01 · The reel
Shoku reads the reel for you: eleven steps, twenty three ingredients, the amounts beside the thing they belong to. Then it answers at the stove, edits when you ask, and counts what your fridge is missing.
24 MB APK · Android · source on GitHub
02 · Import a reel
Send a reel from Instagram or YouTube, or take one from the Wall. The model reads the video and the caption, then writes the method out in order, linking each step to the ingredients it uses.
It also says what it cannot know. Amounts read off a video are estimates, and the page carries that line at the top instead of hiding it.
21 reels on the Wall · 11 steps for palak paneer · 23 ingredients
Three reels from the feed, and the pages that came back. Nothing is retyped, and the thumbnail stays with the recipe.
in your cookbook, with its cover
03 · The assistant
One thread per dish, and a kitchen thread with no dish at all. The scope sits above the input, so you always know what it is looking at. Everything below is a real answer from the build, recorded on 2 November.
One question, one answer, metered against the twenty talks a day.
Nothing is written until you press it, and v1 stays in the history.
The matcher computes these against your shelf. The model only chooses among what it was given.
Paneer has no amount because the sentence had none. It never invents one.
An edit comes back as a list of operations with the words it will change, and a version id it was computed against. Press apply and one version is written. Ask for something destructive and it opens the real flow instead of doing it.
Two versions can be compared, and the older one is never overwritten. That is the whole reason the journal exists.
edit · apply · undo is another ask
04 · The fridge
Every ingredient in the recipe is checked against your shelf. The count is arithmetic, not a guess: units convert inside a family, grams to kilos, and a line whose units do not convert is left alone. Tap a row below and watch it move.
Eight of the twenty three are shown here. One more is already on the shopping list, which is why five have and seventeen to buy add up.
And it fills from a receipt
Real output from one photo. The photo goes to a vision model once, comes back as lines you confirm, and is not kept.
05 · The cook
Three steps from this cook, the ones photographed on 2 November, each paired with the frame that matches it. On the left, the app exactly as it stood at that step. On the right, what the step looked like in the kitchen. Step through them with the numbers, the arrows, or the keyboard.
Wash the palak thoroughly under running water and drain.
06 · Questions
No. The amounts are read from the video, and the page says they may be off in a line you cannot miss. Every amount can be edited, and the edit becomes a version.
A structured output model reads the reel into steps and ingredients, and Meta’s vision model reads a receipt photo. The matching against your shelf is plain arithmetic, not a model, which is why it never invents a dish.
It proposes edits as a diff, and one version is written only when you press apply. It never deletes a version, and a destructive request opens the real flow instead of running.
The candidates are computed from the Wall against what you have in the fridge. The model is only allowed to choose among those, and to name what is missing from them.
The image is sent once, read once, and not stored. You see the lines before anything reaches your fridge, and the app tells you before the first upload.
The assistant needs the API, and it says so rather than pretending. The journal, the fridge and the shelf keep working, and anything you change syncs when you are back.
Twenty a day, shared between asking, editing, suggesting and capturing. The shelf, the matching and the journal do not count against it.
Not yet. The builds are Android APKs, and every release also publishes a debug build for testing.
Shoku is free, and every build is published in the open.
Take the arm64 build for most phones. The debug build sits beside it on the same release.