You’re cooking. Your partner asks when the garlic goes in.
“That’s in the next step,” you say.
And the app skips to the next step.
That was one of the problems we had to solve on Feasty.
Feasty was founded by Michael, who spotted a gap. TikTok is brilliant at the mouth-watering part of food. It makes you want to cook something, then gives you no help when you try. No ingredients list, no step by step, no instructions.
So Feasty took those videos, synced them to the steps and showed the ingredients. They stopped being a way to discover recipes and became a way to cook them.
The video waits for you
The video stops at the end of each step. Timers start by themselves. You can continue or repeat a step with your voice, because your hands are covered in whatever you’re cooking. It works in portrait and landscape, because you’ll use whatever stand is in your kitchen.
Your phone stops being a phone. It’s a cookbook that knows where you are.
The bits nobody sees
Stopping at the end of a step sounds easy. But the keyframes in a video don’t always line up with the end of a step, and it still has to stop in the right place. Nobody praises a video for stopping on time. Everybody notices when it doesn’t.
Voice was its own problem. Phrases sound alike, and people talk while they cook. So it needed a wake word: Feasty. It also needed context. If a step usually takes ten minutes, “next step” at two minutes probably wasn’t meant for the app.
Then there were the steps that weren’t in the video at all. TikToks skip the boring parts, because they don’t look good on camera. But the recipe still needs them. So we designed screens to fill those gaps.
Apps get designed at a desk. They get used in a kitchen.
None of those problems exist at a desk. They come from messy hands, a partner talking and a phone propped against whatever’s nearby.
So before you decide how your app should work, go and stand where people will use it.