A note from the back room
From Kyle. The story behind Speakeater.
Every first-person note from the build, in one place. Because the homepage was getting too long, and most of this was buried halfway down a 4,000-line scroll.
Chapter one. The Tuesday that started it.
I built this in my own kitchen.
It was 9pm on a Tuesday. I had ingredients. Real ones, half a chicken, a head of broccoli, garlic, parmesan, lemons. Genuinely cookable.
I pulled up a recipe to figure out what to do with the chicken. The page opened with fourteen paragraphs about Sandra's nonna in a Tuscan hillside village hand-cracking peppercorns harvested by a goat farmer named Giuseppe. I scrolled past the watercolor of an olive grove. I scrolled past the SEO keyword paragraph. I scrolled past three banner ads and a newsletter popup. By the time I finally hit the actual ingredient list, I was on UberEats. The chicken stayed in the fridge. Now it was haunting me, and I had pad thai too.
"Open the fridge. Take some photos. Tell me what to cook."
That's it. That's the whole pitch. No nonna. No olive grove. No newsletter. Snap a few shots of your shelves, and Speakeater tells you what's actually within reach tonight.
I'm one guy doing this. I'm shipping it slow because I'd rather you trust the app than feel hooked by it. The cocktail side is in there because there are recipe books from 1862, 1882, 1908 that nobody has properly digitized, and that bothered me enough to fix it.
If something breaks the first time you cook with this thing, email me. I'll fix it the same day.
- Kyle
Chapter two. Why solo.
One person. One strong opinion.
Speakeater is one person. Me. Native Android in Kotlin, Cloudflare Workers backend, vision for the fridge scan. Bootstrapped, no investors, no team, no growth budget until the product earns it.
Cooking apps are a graveyard of well-funded teams that shipped slop. The ones that actually retain users are mostly solo builds with one strong opinion. Paprika is one guy. Crouton is one guy. Mela is one guy. Speakeater is the cook-from-your-fridge answer to the same question.
Most cooking apps assume you already know what to make. That's the wrong starting point. The real starting point is the moment at 8:43 PM when you open the fridge, sigh, and reach for the takeout app. Fix that, the rest follows.
- Kyle
Chapter three. Why two cocktail eras.
The manuscripts deserve their own room.
Cocktail apps either mush every recipe into a 2024 brunch menu or they cosplay as old-timey without doing the work. The split between Bootlegger and Mixologist exists because the manuscripts deserve their own room.
I am not a professional historian. I will be wrong somewhere. But I've typed fifty pre-Prohibition cocktails out by hand from the original 1862 to 1917 sources, page-keyed each one, and quoted both sources where the printings disagree. The ones that ship in the app will follow the same standard.
If you find an error, hit reply on any of my emails. I read every one.
- Kyle
Chapter four. If something breaks.
Email me. I respond inside the day.
Speakeater is built solo. That means there is no support team, no escalation queue, no chatbot trained on a 600-page knowledge base. There's me, a laptop, and an inbox.
If something breaks the first time you cook with this thing, email me. I'll fix it the same day if I can. If I can't, I'll tell you what's actually going on and what the timeline looks like.
If you have an idea, same address. The features that have shipped fastest are the ones a real user emailed me about.
block to keep parity.
=========================================================================== -->