Does SousSmart make you tap through one step at a time?

No — that was the bug. A long unattended step like a roast used to block the steps after it. Now the cooking screen keeps every running step in a live strip and hands you the next step you can actually start, so you prep ahead while the oven works.

How does a cooking app handle a step that takes hours?

By separating 'running' from 'next.' A three-hour roast sits in a running-now strip with its own countdown while the screen moves you on to the steps you can start in the meantime — instead of forcing you to mark the roast done just to see what's next.

The roast that trapped me in my own app

The bug I cooked in

I started the turkey and the app went dark on me

I was cooking a real Thanksgiving run through SousSmart to shake out the rough edges. I hit Start on the turkey — a three-hour roast — and then went to get a head start on the potatoes and the stuffing. Except the app wouldn't let me. The only button in front of me was Done, and the only way to see the next steps was to press it. On the turkey. That had three hours left.

Why it happened

“One step at a time” is a trap for long cooks

The original cooking screen showed a single active step, big and focused. That's a good instinct for a recipe you move through in order — chop, sear, flip, plate — where the next thing really is the only thing. But a holiday meal isn't linear. The whole point of the app is that a turkey roasts for three hours while you do everything else. A screen that only knows about one step treats that dead time as a wall instead of the opportunity it is.

And the workaround the design forced — press Done to move on — was worse than annoying. Marking the turkey done three hours early tells the app the bird is out of the oven. Dinner would have lurched to a completely wrong time. A UI shortcut was quietly lying to the plan.

The fix

Split the screen into “running now” and “what's next”

The redesign separates two things that were fighting over one screen:

A running-now strip. Every step you've started stays visible with its own live countdown. The turkey's timer sits right there while you work — you never lose sight of it, and you never have to fake-finish it to get it out of the way.
A focus card for the next move. It shows the next step you can actually start — never one that's still waiting on something in the oven. Start it, and the card quietly advances to the one after. No Done required to make progress.

So the three-hour roast now does exactly what it should: it hums along in the strip, counting down, while the focus card walks me through prepping every side that can happen in the meantime.

The lesson

Cook the recipe, not the demo

This bug never showed up in a quick test recipe. It only appeared when I cooked something with a genuinely long, unattended stretch — the exact case SousSmart exists to handle. That's the whole reason I'm building this in public and cooking real meals through every build: the assumptions that feel clean on paper are the ones a live kitchen breaks first. A cooking app has to be honest about how cooking actually feels — long waits, overlapping dishes, hands too busy to babysit a screen.