Leaf.Wise shipped July 20. Un.hidden shipped August 3. Two launches in six weeks, after months of building in relative quiet — and the weeks since have taught us more than the planning phase ever did. This is the honest debrief, written down partly so we remember it ourselves.
Lesson one: restraint is visible
We bet the studio on the idea that small, focused apps beat sprawling ones. The nervous question was whether anyone would notice the focus, or just the smallness. They noticed. The feedback that keeps recurring, for both apps, is some version of "it does the thing, and then it gets out of the way." Nobody has asked for a social feed. Several people have specifically thanked us for not having one. Restraint, it turns out, isn't just a design principle — it's a feature users can feel.
Lesson two: context is the actual product
On paper, a plant app and a message decoder share nothing. In practice they're the same machine: gather the context everyone else ignores, and turn it into a better decision. Leaf.Wise reads weather, placement, and history around a plant. Un.hidden reads baseline, pattern, and dynamics around a message. Watching both in the wild confirmed it — the moments users tell us about are context moments. The app that knew it rained. The app that knew "fine" wasn't fine from this person. That's the studio's real product, and it sharpened how we evaluate everything we build next.
Lesson three: trust has to be designed, not promised
Un.hidden taught us this one. People bring genuinely tender material to a message decoder, and no privacy-policy paragraph makes that feel safe. What makes it feel safe is design: conversations that aren't stored, readings that never judge, reply suggestions based on what you want rather than on "winning." We wrote before launch that it was the most careful thing we'd tried to build. Post-launch, we'd put it stronger: for an app like this, the care is the product, and users can tell within minutes whether it's there.
Lesson four: people will use a focused tool in ways you didn't plan
Leaf.Wise users log plants we never anticipated (a bonsai collection; one magnificent, doomed office avocado). Un.hidden users decode work emails as much as romantic texts. We built narrow tools and users immediately found adjacent rooms. The lesson isn't to chase every use — it's that focus creates trust, and trust gets your tool invited into places you didn't design for. The feature requests that matter are the ones pointing where the focus already was.
What this means for the third one
Stock.ed — the kitchen Superapp — is still in development, and these lessons are being applied to it in real time. Context first: what you have, what's expiring, what that means for dinner tonight. Restraint: no recipe social network, no meal-plan guilt engine. And the effortless-entry problem we wrote about in July is exactly a trust problem: an inventory you can't trust is an app you stop opening. It's taking the time it needs to be right. Two launches in, we're more convinced than ever that right beats soon.
More on Stock.ed closer to launch. In the meantime: Leaf.Wise and Un.hidden are both live, both free.