/ 01 / ProblemA trustworthy mobile bank-adjacent app, shipped solo.
Monetiza came to me with a half-built React Native prototype, two designers, and a runway problem. They wanted a real iOS and Android release in a quarter, a subscription stack that wouldn't leak revenue, and a backend they could actually scale on after I left. The founder's brief was the kind I like: “Don't tell us what you can't do. Tell us what you'd build.”
/ 02 / DecisionFlutter, RevenueCat, Firebase. No clever choices.
I rewrote the app in Flutter in six weeks. “We already have RN, just finish it” is the most expensive trap I've watched founders walk into. A week into the rewrite, the team stopped asking. Subscriptions went through RevenueCat with server-side receipt validation (never client-only). Firebase Auth, Firestore, and Functions covered auth, storage, and the lightweight server logic without a second engineer.
/ 03 / BuildEleven months, three releases that mattered.
- v1: ship the core flows. Onboarding, accounts list, transaction tagging, manual entries.
- v1.4: subscription gating and paywall. The single biggest revenue moment in the app's life.
- v2: AI-powered transaction categorisation. Server-side, prompts versioned in the repo, fallbacks for cold-start users.
