Services · Mobile apps
One codebase, every platform your customers are on.
Cross-platform iOS, Android and desktop apps built with Flutter: offline-capable and store-ready.
Best for: Products that genuinely need to be on a phone (offline use, camera, notifications) rather than a website in an app wrapper.
The short version
The honest first question is whether you need an app at all. A great many things that get built as apps should have been websites: cheaper to make, no store review, and nobody has to install anything. I will tell you if that is your situation.
When an app is genuinely the right answer, when you need to work offline, use the camera, send push notifications, or live on someone's home screen, I build with Flutter, which produces iOS, Android, Windows and macOS from one codebase. I am currently 200,000+ lines into building exactly that, solo, so the estimates I give you come from doing it rather than reading about it.
What you get
- One codebase targeting iOS and Android, and desktop if useful
- Offline-first data with sync, so the app works on the MRT
- Native sign-in flows rather than a browser bouncing users around
- Push notifications and crash reporting wired up from day one
- App Store and Play Store submission, including the parts that get rejected
- Source code and store accounts in your name
How it runs
Sanity check
A frank conversation about whether an app is the right vehicle. Sometimes the answer is a mobile website and a much smaller invoice.
Scope and prototype
The core flow first, running on a real device, so you can hold it before the expensive parts get built.
Build
Regular builds you can install and use. Offline behaviour and sync get tested deliberately, because that is where cross-platform apps usually break.
Ship and hand over
Store submission, review responses, and transfer of developer accounts and signing credentials to you.
Common questions
Should I build an app or a mobile website?
A website, unless you need something a browser cannot do: reliable offline use, background sync, push notifications, deep camera or sensor access, or a home-screen presence that drives repeat use. Apps cost more to build, require store approval, and need users to install them. If your use case does not need those things, I will point you at the cheaper option.
Do I need separate iOS and Android builds?
No. Flutter compiles one codebase to both, plus Windows and macOS. That is roughly half the build cost of native development and, more importantly, half the ongoing maintenance: a fix goes in once rather than twice.
How long does an app take?
A focused first version is usually two to four months, depending on how much has to work offline and whether there is a backend to build alongside it. Store review adds days to weeks and is outside anyone's control. I plan for it rather than being surprised by it.
What about the App Store approval process?
I handle submission and the back-and-forth with reviewers. Rejections are normal, usually about metadata, privacy declarations or account deletion requirements rather than the app itself. Knowing the common ones in advance is most of the battle.
Ready when you are.
Describe the problem in a few sentences. You will get a real reply within one business day, and a straight answer about fit.