I have spent just over a year building a gardening intelligence and plant identification app, and it turned into a test of a hypothesis I'd been forming across years of running production AI systems.
The default now seems to be to reach for one large model, run it in the cloud, and treat it as a general solution. I've come to think that's the wrong default for anything working under real constraints. The bigger the model, the more it abstracts away from the specific job. The more cloud-dependent it is, the more it inherits the cloud's downsides: latency, cost, privacy exposure, vendor risk.
So I built the opposite. The whole identification model ships inside the app and runs on-device. There are no server calls ever. Under the hood that's not one big model but smaller, specialised ones composed into a system, the kind of architecture software has used for fifty years and the current AI moment has partly forgotten.
The economics are something I think people maybe don't think about enough. Cloud inference costs per request, so for a subscription app the cost scales with engagement and your best users become your most expensive. On-device inverts that. Once the model ships, inference is effectively free, and heavy users become your cheapest instead of your priciest.
Hey Product Hunt. I'm Matt, the maker. Here's the moment that started this.
A while back I photographed a seedling in my garden. An app told me, with complete confidence, it was basil. I left it to grow. It turned out to be annual mercury, which is mildly toxic. Basil isn't. The app never hedged and never offered an alternative. It just said basil.
That stuck with me, and it's why I spent the last year building Raychis.
I've spent fifteen years in engineering, the last five leading SRE teams for production AI systems. I'm not a botanist, just someone who gardens and got tired of tools that were confidently wrong.
Raychis is a gardening companion that identifies what you grow and learns your garden over time, tailoring care to your plants, your region, and the season. Two things make it different:
It's honest. When it isn't sure, it tells you, instead of guessing.
It runs entirely on your phone. The whole model ships in the app. No account, no cloud, no server calls, no subscription wall to open it. It works offline in the garden or on a walk, and nothing leaves your device.
It learns your garden over time the more you use it. It is able to tell you what is going on, what to look out for, what tasks you should be doing, and what would be good to grow. It is more than a plant ID app. It is a gardening intelligence app that will act as a true garden companion.
Fitting real identification into a phone's memory budget was the hard part, and the interesting one. It meant composing smaller specialised models rather than leaning on one big model in the cloud.
I'd love your thoughts, especially on the honest-uncertainty question: would you rather an app admit when it isn't sure, or just hand you a confident answer? I'm here all day to answer anything.