Who this is for
Businesses whose customers live on their phones.
- Companies with a repeat-use service — bookings, orders, loyalty or account access that customers reach for weekly, where a website tab is one step too many.
- Teams in the field — staff who need your system in their pocket, working even where the signal doesn't.
- Founders with an app idea — you want an MVP in front of real users in weeks, not a year, without paying for two separate native builds.
- Businesses extending an existing system — the web app or CRM exists; now it needs a mobile front door with push notifications.
What you get
Design to store submission, one pair of hands.
- One Flutter codebase for iOS and Android — one build to pay for, one to maintain, native feel on both stores.
- UI design through to store submission — the whole journey handled, including the listing assets and review process.
- Offline-first architecture — the app stays useful when the connection isn't; South African networks are part of the design brief.
- Push notifications — the channel that brings customers back, set up with restraint so people don't switch it off.
- API backend and integrations — the app connected to your site, store or business systems rather than floating alone.
- Store listings and release management — versioning, updates and rollouts handled after launch, not abandoned at it.
With or without AI
Everything works without AI. Where it earns its keep, the same app can add voice, vision and an assistant in your customer's pocket — pilot small, prove the value, then scale.
How it runs
From idea to both stores.
- Step 01Free consultation
Thirty minutes on the problem the app solves and whether an app is even the right answer — straight advice, even if you don't hire me.
- Step 02Fixed proposal
Scope, timeline and a fixed quote, usually within a few days. MVPs are typically four to ten weeks.
- Step 03Build in the open
Test builds on your own phone as the app grows — you steer it from the first week, not the last.
- Step 04Ship and improve
Store submission, release management and Kaizen Care — updates and improvements for as long as the app lives.
Starts at from R35 000
Mobile builds start on the Grow plan. Every project gets a fixed quote after a free consult, scoped to a clear MVP.
Get a fixed quote →Proof
Capability proven in The Lab.
The honest version: my shipped client work is web and systems — the app-grade engineering is proven in The Lab. Aurora, my EOS business platform, is an offline-first PWA with real-time sync — and the same discipline — offline architecture, API backends, release rigour — is what a Flutter build gets. Judge the engineering yourself before you hire it.
Before you ask
Quick answers.
An MVP is typically four to ten weeks, scoped in the proposal with a clear timeline you can hold me to. Store review adds a little at the end — it's planned for, not a surprise.
Apps start from R35 000 on the Grow plan. Every project is scoped individually after a free consultation, and you get a fixed quote before any work starts.
You do. Code, store accounts and backend are registered to you, with full access and handover documentation. No lock-in, ever.
No. Everything I build works beautifully without it. Where AI would genuinely earn its keep, I'll show you the case first — pilot small, prove the value, then scale.
Begin
Let's put your business in their pocket.
Tell me what the app must do and who it's for. You'll get a straight answer — including whether you actually need an app — usually within a day.