iOS new product flow
We had the metric, the customers published their products and wanted to continue editing.
We created a flow that prevented them from doing that. We had the metrics and what the customers needs, but was it really what they needed?
We had metrics that indicated that customers once they published a product, went directly to create a new one or edit it. We had a well-defined behavior, but our flow did not allow that efficiently. On the contrary, it obliged people to have one more step of sharing, when they did not want to do that
The new flow was simple. Once the client finished editing or creating a new product, it went directly to the product’s list and a message appeared with this message: “Congratulations, your product was saved / published successfully” and an action with “more” options. Those options are: edit, duplicate or share.
There was a substantial change between the old flow and the new one. An impressive increase on the edition and duplication. It was successful for the new flow.
- Create the new architecture.
- User cases.
- Wireframe, sketch and create the UI for the feature.
- Testing with users with Maze.
- Testing the interface and understand the metrics
LEARNING AND FAILURES
- I learned to listen to the main needs of clients
- Look at the metrics and cross the information with the needs of the clients.
- Understand simple solutions