Build
iOS & Android App Development
Both app stores, one budget. Flutter where a single codebase does the job, native Swift or Kotlin where the app lives on the device. The right answer depends on what the app has to do, not on what I prefer building.
iOS & Android App Development
Need an app on both stores without paying for two separate builds?
Problem
Need an app on both stores without paying for two separate builds?
Solution
Flutter for one codebase across iOS and Android, native Swift or Kotlin when the app depends on the device itself. I'll tell you honestly which one your app needs, and whether a mobile web app would get you there sooner and cheaper.
What you actually get
One codebase, both stores
Flutter compiles to genuinely native iOS and Android apps. For standard apps, lists, forms, maps, chat, media, it performs like native and costs roughly a third less than building twice.
Native where it earns it
Swift with SwiftUI, or Kotlin with Jetpack Compose, when the app is built around the camera, AR, health data, background location, or a watch. I will say when that is the case rather than stretching a framework past what it does well.
Works without signal
If the job happens on site, in a basement or on the Underground, the app reads and writes to a local SQLite database and syncs when a connection returns. Planned in from the start, because retrofitting it means reworking every screen.
Through review and onto the stores
App Store Connect and Play Console, signing, privacy declarations, TestFlight builds for your testers, and the submission itself. Handled, not handed back to you as a to-do list.
How it works
Same principles, whatever the job.
- 01
Decide what it should be first
Sometimes the honest answer is that a mobile web app gets you to real users faster with no store review, and native comes after the demand is proven. That conversation happens before anyone quotes you.
- 02
Build in sprints you can see
Working builds on your phone through TestFlight and Play internal testing every week, not a reveal at the end.
- 03
Launch and stay on
Store submission, crash reporting, analytics on what people actually use, and support packages if you want me on hand for the releases after launch.
Questions
Flutter when you need both stores on a limited budget and the app is made of standard screens. Native Swift or Kotlin when it depends on the device: serious camera work, AR, HealthKit, precise background location, watch apps, or platform features released this month. If you only need one platform, cross-platform buys you nothing.
It depends on how many screens there are, whether it needs accounts and payments, and whether it has to work offline. Cross-platform costs less than building twice, though not half, because store submission and platform-specific work still apply to both. Message me on WhatsApp with what the app needs to do and I will scope it properly and price the whole job, fixed, before anything starts.
Flutter if the app is UI-heavy and you want the same behaviour on both platforms with fewer surprises. React Native if you already have a React and TypeScript web app to share logic with. Both are production-grade; team skills usually decide it.
You need an app when you need push notifications, offline use, device hardware in the background, or a place on the home screen. If none of those apply, a fast mobile web app ships sooner, costs less and skips store review entirely. Plenty of businesses pay for an app when what they needed was a better mobile site.
Yes. It starts with a technical review: what is there, what is safe, what is worth keeping. Half-finished apps from agencies and AI builders are a large part of what I pick up.
A focused first version is typically 10 to 16 weeks including store submission, depending on how much backend it needs behind it. Apps with offline sync or payments sit at the longer end.
If it needs to. Data lives in a local SQLite database on the device, with a sync layer that reconciles with the server when a connection returns and a conflict rule agreed up front. Field service, delivery, inspections and warehouse apps all need this.
Yes, including signing, privacy and data declarations, screenshots, TestFlight distribution and dealing with review rejections when they happen. It is part of the build, not an extra.
Goes well with
Book a call
Loading calendar…
No time that suits? Message Joe on WhatsApp or email hello@calljoe.co.