Blog
2 min read

Shipping consumer apps solo: what Axiome taught me

Five consumer apps designed, built and submitted without a team. The release chain, the AI in production, and why product taste now matters as much as the code.

AxiomeExpoMobileIndie

I run Axiome App Studio alone. In 2025 I designed, built and shipped five consumer apps — Belle, Koji, Tanzy, KnuckleMax, Teacherz — on Expo, strict TypeScript, Supabase and Superwall. This is not a manifesto about “indie hacking”. It is what actually changed once there was no one else to catch a bad release.

The constraint is the product

With a team, a slow App Review round is annoying. Solo, it is the whole week. So the release chain had to become a procedure: multi-file version bump, local .ipa / .aab builds, App Privacy, canned answers for App Review. Each submission is now a script I run, not a ritual I reinvent.

The same applies to errors and money. Every app has Sentry. Every app has a Superwall paywall. PostHog sits on the whole portfolio — onboarding funnels, activation, retention — because I cannot sit behind every new user.

AI in the product, not as a demo

Belle uses vision models to look at a face and advise. Other apps generate onboarding, copy, and localisation that detects FR / EN / ES / IT. That only works if the model is a step in a shippable flow, not a chat window bolted on at the end.

I still care about the code. Since models arrived, code is no longer the centre of every conversation — product is. I write with Cursor. Some days I ship in a straight line. Some days I slow down and get the details right. The studio only exists if both modes are available.

What I would not drop

Expo and TypeScript strict. A single backend shape (Supabase) I already know. Analytics before polish. And a public page for the studio, because a stack of App Store listings does not explain who built them.

If you want the inventory: Axiome App Studio. The landings for Belle, KnuckleMax and Koji are linked from there.