Both language sides asked for the same missing thing this year
Both language sides asked for the same missing thing this year: a recipe delivered as a hands-free, timed, step-by-step run rather than a block of text. In English a subreddit built it themselves (Parsnip, 139 points in r/cookingforbeginners) and another thread asks for recipes formatted like IKEA manuals; in Chinese the request appears under a developer's open 'you ask, I build' thread, and the developer's reply is that he has no product to point at.
What is the idea?
Nothing complete yet. What is wanted: take one recipe and run it — each step spoken aloud, its timer started for you, the next step on your voice, and the vague parts (heat, doneness, quantity) turned into something checkable.
Who would use it, and what do they get?
Non-developer user: someone at the stove with their hands full. Finished thing: dinner that came out the way the recipe said it would.
Why would anyone bother?
The failure is specific and repeated in both languages: hands are dirty, the screen locks, the timing lives in prose, and the cook improvises and ruins it.
What is missing today?
It hits a real pain but every product solves the storage half. Recipe apps compete on how many recipes they hold; the cook's problem is the twenty minutes at the stove. The Chinese request names the missing piece exactly — a timer per step and something that stops you improvising — and the developer taking requests had no product to point at.
What makes this one different?
Do not own a recipe library — that is the part that is already owned and already crowded. Take the recipe the person already found (a screenshot, a Xiaohongshu note, a link, a photo of a cookbook page) and convert that one into a hands-free run: steps read aloud, timers started automatically, advance by voice, and the vague instructions expanded into a checkable cue. The wedge is 'works with whatever recipe you already trust', which is exactly what a platform with its own library will not build. Cold start (Chinese): the comment tree of 「想要什么软件？你说，我做！」 (283 comments) and the 下厨房 App Store review section; Cold start (English): r/cookingforbeginners, the 'recipes as IKEA manuals' thread and its 32 comments.
What is the sharpest thing about it?
Recipes are written as reference documents and used as live instructions. Nobody has fixed the mismatch; they have only added photos.
What could kill it?
Parsnip already shipped this shape in English with 450 levels and community goodwill behind it, so the English side is not open. In Chinese, 下厨房 owns recipe distribution and can add a step mode in one release. And cooking-app retention is brutal for a reason nobody talks around: most households cook the same eight dishes, so a tool that teaches you to follow a recipe is used hardest by the people who will stop needing it.
Who pays, and for what?
Someone learning to cook, or cooking for a child with a specific diet — a one-off purchase or a small subscription, priced against one ruined dinner.
What is the main risk?
The people who need it most graduate out of needing it; retention is the whole business and this shape has no answer to it yet.
What did real people actually say?
Verbatim from the public sources linked above, not paraphrased: “我想要一个菜谱app，上面有每道菜每一个步骤的计时器，全程跟做，提醒火候和量。时刻监督我不要灵机一动和差不多的了。” — xiaohongshu “I've always struggled with how recipes are always dense blocks of text, and I wished there was an app that converted them into a visual format.” — reddit “哈哈哈，很实用的功能，我研究一下” — xiaohongshu
How much work is it?
about two weeks of work
Where does the evidence come from?
https://www.xiaohongshu.com/explore/67ab4967000000002802a6eb https://old.reddit.com/r/cookingforbeginners/
← The highest-scoring post in r/ADHD on this subject (2,411 points · Two generations of WeChat chat-history exporters have ~55k combined… →