Allison's Kitchen

This did not start as a product. It started because the recipes my family actually cooks were scattered across screenshots, a browser bookmark folder, a paused video, and someone's memory — and the week's plan lived nowhere at all.

That is the credibility, not something to apologize for. Software built for a real household under real conditions gets corrected every single evening. The dinner does not care whether the feature demos well.

The category is full of tools for saving recipes and nearly empty of tools for the twenty minutes when someone is standing in a kitchen with a hot pan. Capture is easy and well served. Planning the week and then executing it is neither.

So the product treats capture as a means, not the point: get the recipe in from wherever it lives, then get out of the way.

Capture ingests a link, a photo of a printed page, or a video you paused, and normalizes it into structured ingredients and steps. Planning assembles the week in one sitting and rolls the result into a consolidated shopping list.

The cooking view is deliberately austere: one screen, current step, no upsell, no ads, nothing that requires clean hands to dismiss.

Web is in invite — real households, gated, added deliberately rather than in a launch. The iOS build is in user acceptance testing.

Adding families slowly is a choice, not a constraint. Each new household surfaces assumptions that were invisible while the only user was the person who wrote the code.