07
Mobile App Development
One codebase, both platforms, and someone who has actually been through App Store review. Most of the cost in a mobile project isn’t the screens — it’s everything around them.
When this is the right fit
- You need iOS and Android, and paying for two native teams isn’t realistic.
- You have a web product and mobile is the next obvious step.
- An agency quoted a number that felt disconnected from the actual scope.
- You have designs, or a clear idea, and need someone to build it.
- A previous attempt stalled somewhere between TestFlight and the store.
How I build it
- 01
Agree what version one actually is
Almost every first spec contains features that can wait. I’ll push to identify the smallest version that’s genuinely useful, because getting it in front of real people teaches you more than another month of building.
- 02
Flutter, one codebase
iOS and Android from the same source, with platform-specific behaviour where it genuinely matters — permissions, notifications, deep links, payments — rather than a lowest-common-denominator app that feels wrong on both.
- 03
The backend too
Most mobile apps are a thin client over an API. I build that as well, so there’s no gap between the two and no second contractor to coordinate with.
- 04
Through review, onto the stores
Signing, provisioning, privacy declarations, screenshots, the rejection that always happens the first time. This is the part that surprises people, and it’s included.
How long it takes
A focused first version is usually three to five weeks, but it depends heavily on the requirements — how much backend sits behind it, and whether payments or offline support are involved. Store review adds a few days each way. Tell me what it needs to do and I’ll give you a real number.
Questions about this
Can you build something from scratch?
Yes — mobile, web and AI-powered products. It's a different engagement from a rescue: we start with what the thing actually needs to do, and I'll usually push to get a small version in front of real users before building the rest. If your idea is better served by something simpler than what you're picturing, I'll say so.
Can you work with Flutter?
Yes — Flutter is one of the stacks I’ve worked in longest, across both apps and the backends behind them. That includes state management, platform channels, builds and store releases.
Can you help with deployment?
Yes, and it’s one of the most common reasons people get in touch. "It works locally" is almost always an environment, configuration or build problem rather than a code problem, and those are findable.
Your AI-built app doesn’t need another prompt.
Sometimes it needs an engineer.
Send the messy version. That’s usually the useful version.