A recipe is written to be read at a table. Cooking happens standing up, with a hot pan, a timer you set on the microwave, and hands you cannot put on a screen. That gap is where dinner goes wrong: you scroll past a story to find step four, the phone locks, you lose the thread, and the chicken decides the timing for you.

None of that is a cooking problem. It is a tool problem. So we started from what a kitchen actually demands and built backwards.

What we decided

One step at a time. The screen shows the instruction you are on, in type you can read from across the counter, and nothing else competing for your attention.

The app keeps time, not you. A timed step brings its own timer. It runs on the clock, so it stays honest whether the screen is on, the app is closed, or the phone restarted.

It never loses your place. Every move is written down as it happens. Take a call, drop the phone, come back two minutes later: you are still on step three, with the right amount of time left. This is the hardest part to build and the first part we got right.

Safety where the risk is. The temperature that keeps you safe belongs on the step where you check it, not in a note at the bottom of the page.

What we will not do

We will not describe a feature we have not built. The features page lists what the app does, the roadmap lists what it does not do yet, and those two lists stay apart even when it would be easier to blur them.

We will not call the app hands-free until you can cook a whole dish without touching it. We will not promise a launch date we cannot keep. And we will not sell your email address.

Where it is now

Golden Cheff is not in the app stores yet. It is being built and tested in real kitchens, on cheap phones and new ones, on tablets propped against a canister. When the invites go out, the people on the early list get them first.