Recipe sites are broken. Most of you reading this already know.
You search "chocolate chip cookies." The first three results are blog posts. You click one. You scroll past a photo of the writer's kitchen, a story about their grandmother in Connecticut, a second photo of a different kitchen, an ad for car insurance, a popup asking you to subscribe, another popup offering a free e-book if you give them your email, a section titled "Why these are the BEST chocolate chip cookies", a list of frequently asked questions about chocolate chip cookies, a third popup reminding you about the free e-book, an embedded video that autoplays, a section titled "Tips for chocolate chip cookie success", an affiliate link to a brand of vanilla extract, a fourth popup, and finally — eleven scrolls down — a recipe card.
The recipe card is fine. The recipe card was always fine.
We built Mise because the recipe card should have been the first thing. We built it because cooking software, in 2026, can be better than scrolling.
Mise is a recipe app. It does the things recipe apps do — capture, save, cook, share. The difference is that every recipe in Mise is structured. We resolve the ingredients to canonical entries. We name the techniques per step. We infer the cuisine. We profile the flavor on seventeen axes (you only see seven; the rest do work behind the scenes). We track every edit you make and every cook you log. The data flows underneath the surface like wiring you don't have to think about.
Why does that matter?
Because once a recipe is structured, every other thing you might want to do with it becomes possible. Find every recipe in your library that uses black garlic. Show me what I can cook tonight from what's in my fridge. Cook a Sichuan dish using a tadka technique. Print compliance-grade allergen sheets for the catering job on Saturday. Scale a sheet-pan recipe to four pans for the eighteen people coming for dinner. Substitute the butter — but only with subs that work for what the butter is doing in this step. Cook the recipe hands-free, on a phone you can't touch, with a voice assistant that doesn't hallucinate.
None of this works if the recipe is a blob of text. All of it works if the recipe is a typed object.
A few principles we won't bend on.
Recipe-first, everywhere. Every public Mise page leads with the recipe. No life story. No preamble. No five photos of a different kitchen. The story, if there is one, is below the fold.
No dark patterns. No cookie banner. No newsletter modal. No "log in to read more." No "limited time" countdown. No fake scarcity. No interstitial upsells in cook mode — when you're cooking, we get out of the way.
Honest AI. We use machine learning extensively. We never invent recipes that don't exist. We never tell you a confident answer when we're not confident. Photo-adjust shows its uncertainty. The doneness check refuses to call your steak from a photo and points you at the thermometer. We'd rather be correctly humble than wrongly confident.
Credit upstream. Every recipe captured from another site links back to its source. We never republish someone else's writing as our own. The structure is in our index; the prose stays where it belongs.
Cooks are the customer. Not advertisers. Not data brokers. Not the engagement-metrics dashboard. The cook with wet hands and a beeping timer is the only person we design for.
Mise is iOS-only at V1. Android comes later. The website you're reading is hand-built. The recipes you'll cook will be too.
— The Mise team