Solution
01
Build recipe-based UX
![](https://uploads-ssl.webflow.com/5b0af4d950206151bd13c09b/5cb7a2067564c72465509c69_Showcase%20UX_Scenario.png)
![](https://uploads-ssl.webflow.com/5b0af4d950206151bd13c09b/5cb89b44bfadbeafda515318_Showcase%20UX_Recipe%20A.png)
01/ Highlight recipe
Make recipe an independent category.
The change was made due to the scenario test:
01/
It causes overwhelming user flows if a recipe needs both food processing and cook.
02/
Almost all the cook recipes include food processing steps.
03/
Users may confuse about where to find the recipe they want. Un-friendly user experience for making user think before use.
04/
User doesn’t care about if it is a non-cook or cook needed recipe.
02/ Short cut between recipe page and setting page
Make short cut between recipe page and setting/ working pages.
As showed in scenario test:
It takes at least 6 steps from recipe page to a setting page. Users may check the recipe again during the operation. Repeated steps will become a huge pain point.
![](https://uploads-ssl.webflow.com/5b0af4d950206151bd13c09b/5cbbf2a300c3d3c0885c38e5_Showcase%20UX_Recipe%20B.jpg)