Meal planning shouldn't require planning seven perfect dinners.
Start smaller.
Pick a few meals you actually want to make. Reuse ingredients. Leave space for leftovers. Leave space for life.
A useful meal planner should reduce decisions during the week, not create homework on Sunday.
Open source makes software incredibly easy to copy.
Bitcoin proved digital scarcity could exist anyway.
We find that contrast fascinating.
Code can be abundant.
Trust, reputation, attention and relationships remain scarce.
Those are the things you have to earn.
The internet doesn't need another 10,000 chicken recipes.
What we need are better ways to find the right one.
Something that fits your time, ingredients, skill level, nutrition goals and mood.
Discovery gets much more useful when the question changes from:
“What recipes exist?”
to:
“What should I cook?”
A five-star rating tells you whether someone liked a recipe.
A conversation can tell you much more.
What did you substitute?
What would you change?
Did your kids eat it?
Would you make it again?
Food gets better when knowledge travels with the recipe.
Shipping a product changes the questions.
Before launch: Does this work?
After launch: Does this help?
That second question is much more interesting.
As more people use Zap Cooking, that is what we want to learn: where are the moments we can remove one more step, one more decision, or one more frustration?
Recipes are interesting because they are both structured and deeply human.
There are quantities, temperatures, times and steps.
But there is also instinct, culture, memory and taste.
That makes food a fascinating place to build technology.
The computer can help with the structure.
The human still makes dinner.
We don't want you spending more time inside Zap Cooking.
We want you spending less time figuring out what to cook and more time actually cooking it.
That distinction matters.
Good software isn't measured only by engagement.
Sometimes success means helping you put the phone down.
Open source gives us an unusual kind of accountability.
We can tell you how we think the technology should work.
Or you can go look at the code yourself.
We like that.
Transparency is more useful when it can be verified.
There’s a special category of recipe that comes with a person’s name attached.
Those recipes have usually survived years of dinners, substitutions, picky eaters, and requests for seconds.
That’s better testing than most software gets. 👵
Grandma Betty's Chicken Dijon
zap.cooking
Grandma Betty's Chicken Dijon
Sautéed chicken smothered in a dijon cream sauce served over rice, pasta or favorite vegetable(s).
The internet made information nearly free to move.
Bitcoin did something different: it made value internet-native too.
That opens interesting possibilities for creators, communities, and products built online.
We happen to be exploring those possibilities through something everyone understands:
Food.
Don’t be afraid of making mistakes in the kitchen.
Some of the most famous recipes in the world started out that way. 🍪
🚀 Zap Cooking Android 1.4.0 is rolling out.
This is a big update with a lot packed into it:
🔐 NIP-49 encrypted key import + backup
🛡️ Branta payment verification
🔔 Better notifications
⚡ Broadcast notes to your relays from more places
❤️ Cleaner reactions + reposts
🍳 Better recipe and comment context
💬 Improved thread replies
🔑 Google sign-in fixes
📱 Android 16 support
The Zapstore release is live now, and the Google Play update is on the way.
Still building. Still improving. Still focused on making your cooking experience simpler.
🍳⚡ zap.cooking
Software has a cost whether you see it or not.
Servers. Models. Development. Design. Support. Time.
With Cook+, we’re trying to build a straightforward exchange:
We make tools that improve your cooking experience.
If they create enough value for you, you can support the work.
That feels like a healthier relationship
Nutrition labels give you numbers.
What most people actually want is context.
How much protein is in a serving? What is driving the calories? How does changing the portion change the meal?
We built Nourish around making food information easier to understand, not harder.
The best leftover recipe might be breakfast.
Open the fridge. Cheese? Vegetables? Yesterday’s meat? Herbs that need used?
Put them in an omelette.
No complicated planning required. 🍳
The Anything Omelette
zap.cooking
The Anything Omelette
I make a lot of things with eggs at home. Poached eggs, fried eggs, hard-boiled eggs, shakshouka…but my favorite thing to make is an omelette.
Thai Red Curry has one of the highest flavor-to-effort ratios in existence.
Twenty minutes.
One pan.
Your kitchen suddenly smells like you've been cooking all afternoon.
zap.cooking
Thai Red Curry with Chicken
This delicious and healthy Asian dish has chicken and veggies stewed in a creamy coconut red curry sauce.
What's the one recipe you make when you want people to think you worked harder than you did?
Probably not as bad as it sounds, tbh.
View article →The moment you decide to cook something, the recipe should become easier to use.
Ingredients. Steps. Portions. Nutrition. Questions along the way.
That’s how we think about product design at Zap Cooking: turn information into something you can actually use in the kitchen.
We simplify your cooking experience
Recipes are weird.
Think about it...
Someone you've never met can teach you how their grandmother cooked dinner fifty years ago.
That's a pretty incredible form of technology.
We've always thought recipes were worth preserving.
We're just building better tools for sharing them.
🍳⚡
