We're a few weeks out from launching our first app, Leafwise, and we wanted to start a small series here on the blog before it lands: one post for each Superapp, about the need that pushed us to build it and the hurdles we hit along the way. Not feature lists. The why. We're starting with the first one, Leafwise, because it's the app that taught us how the studio wants to work.
The need: we kept killing plants we loved
This is not a hypothetical origin story. Between the three of us, we have a genuinely tragic history with houseplants. Not from neglect, exactly, but from confident, well-intentioned wrong moves. Watering on a Sunday because it was Sunday. Moving a plant to a "nicer" spot with no idea it had just lost half its light. Reacting to a yellow leaf by adding water when the soil was already drowning.
The frustrating part was that the information we needed always existed. We'd check the weather before deciding whether to water the balcony plants, but no app cared that it had rained all weekend. We'd notice a plant drying out faster after moving it into the sun, but the app kept ticking on its fixed timer. Care is contextual, and every tool we tried had thrown the context away.
Why a plant app, of all things
People ask why the studio's first release wasn't something flashier. The honest answer is that plant care was the perfect first problem: small enough to hold in one head, deep enough to reward doing it properly, and personal enough that we'd know immediately if we got it wrong. It fit exactly what we mean by a Superapp, a single-purpose tool that goes deep on one job instead of wide on ten.
And the failure mode of existing apps was so clear. A watering schedule is a fundamentally flawed model for a living thing whose needs change with the season, the weather, the pot, and the room. We didn't need to invent a new category. We needed to build the app we already wished existed.
The hurdles
Building it was harder than the tidy version of this story would suggest. A few of the walls we hit:
- Weather is messy. Turning "it rained near you recently" into an actual watering decision meant reconciling location, rainfall, temperature, and humidity into advice a person could trust, without drowning them in data or being confidently wrong.
- Context has to be effortless. The whole idea falls apart if logging your care feels like a chore. We rebuilt the flow for adding a plant and recording a watering more times than we'd like to admit, chasing something that felt like a quick note, not a form.
- Restraint is a feature. The temptation to add a social feed, a marketplace, streaks, and badges never fully goes away. Every time we said no to one, the app got quieter and better. Saying no turned out to be most of the work.
- Personality without noise. We wanted Leafy, the companion, to reflect your progress back at you without becoming a mascot that won't stop talking. Finding that line took a lot of deleting.
What it set in motion
Leafwise gave the studio its template. Start with a real need you keep tripping over. Go deep on the context that everyone else ignores. Cut anything that doesn't serve the one job. Add a little warmth, but never at the tool's expense.
That template is exactly why there's more than one Superapp on the way. Over the next couple of posts we'll talk about the other needs we couldn't shake, the ones that became the second and third apps. Different problems, same starting point: something in our own lives that no existing tool handled the way it deserved. And Leafwise itself is almost here, we'll have a lot more to say when it launches.