Solo Flutter dev/consumer mobile apps/one release every 4 weeks
«Solo Flutter dev, building consumer apps publicly. One app every four weeks. No team, no investors, no growth hacks. Just shipping and metrics in the open.»
I make portfolio consumer apps in Flutter 3.x: design, code, ship to App Store and Google Play, then unpack the metrics and write about the process in the devlog. The stack is deliberately small — Material 3, Riverpod, go_router, RevenueCat, Firebase, Sentry, Mixpanel. A shared scaffold (auth, paywall, analytics, theming) lives in my own shyber-starter kit — every new project forks from it, which is why the 4-week cadence holds: week one is design + skeleton, two is features, three is polish, four is launch and assets.
Each app solves one concrete pain — no feature bloat, no ads, no third-party trackers. If an app doesn't find an audience within four weeks of launch, it gets archived and I move on. This isn't a venture sprint or a growth-hack — it's slow iterative practice in the open. This site is the working log of that process.
Each slot is one standalone app. Once a release lands, the ghost card flips into a product card with screenshots, MRR, and App Store / Play badges.
First app of the series. Launch — end of phase 0. Subscribe to the devlog — I'll send a TestFlight invite and the changelog the day before the App Store release.
Weekly devlog. Unsubscribe in one click.
One post per week on what got shipped, what broke, what I learned. No buzzwords, no content-marketing fluff. Hosted on Beehiiv.
SwiftUI, React Native, KMP, native Kotlin — I went through every candidate. Cross-platform wins on a single metric: time from idea to a build on two platforms. The pros, and the sharp edges.
readThe full inventory: what I pay for RevenueCat, Firebase, Beehiiv, domains, mail. How a week looks in "one person = the whole company" mode, and which tasks are not delegable (none).
readThe concrete schedule: what has to be done by Monday of week 2, what by Thursday of week 3, and the shape the app is in when it goes to TestFlight on day 5 of week 4. With the slips from my first iteration.
read