Mobile app development
Apps that ship and keep shipping — with the backend, the admin portal, the analytics and the store release process treated as part of the job, not an afterthought.
We build iOS and Android apps natively in Swift and Kotlin, and cross-platform in React Native and Flutter where a shared codebase is the better trade-off. Every engagement includes the API and backend, an admin portal for your team, analytics and crash reporting, and the App Store and Google Play submission process.
A production-quality app with a backend and admin portal typically starts around £40,000 and takes 3 to 5 months. A narrow proof of concept can be delivered for less. We advise on native versus cross-platform during discovery rather than defaulting to one.
What this covers
- Native iOS development (Swift, SwiftUI)
- Native Android development (Kotlin)
- React Native cross-platform apps
- Flutter cross-platform apps
- Backend APIs and admin portals
- App Store and Google Play release management
What we deliver
Native iOS & Android
Swift and SwiftUI, Kotlin and Jetpack Compose. The right choice when you need platform features, best-in-class performance, or an experience that has to feel genuinely native.
Cross-platform builds
React Native and Flutter for one codebase across both platforms. Usually 30-40% cheaper than two native apps and appropriate for the majority of business applications.
Backend & APIs
The part clients forget to budget for. Authentication, push notifications, offline sync, file handling, payment processing, and an API designed for mobile network conditions.
Admin portals
A web application for your team to manage content, users, orders and configuration — so changing something in the app does not require a developer and a store release.
Analytics & crash reporting
Firebase, App Center or Sentry wired in from day one, with the events that matter to your business defined during design rather than retrofitted.
Store submission & compliance
App Store Review Guidelines and Play policy are a genuine project risk. We handle submission, privacy manifests, data-safety declarations, and rejection remediation.
Often combined with
Web Application Development
Not brochure websites. Software that runs a process: customer portals, quoting and booking engines, internal operation…
ExploreCloud & DevOps
Infrastructure you can reason about, deployments that are boring, and a monthly cloud bill that reflects what you actu…
ExploreData, Analytics & BI
One version of the numbers, refreshed automatically, that nobody has to rebuild in Excel on the last Friday of the mon…
ExploreFrequently asked questions
Should we build native or cross-platform?
If the app is a core product with heavy device-feature use, complex animation or performance-critical paths, build native. If it is a business application — accounts, bookings, forms, content, notifications — cross-platform with React Native or Flutter is usually the better commercial decision. We work through it properly in discovery; there is a full framework in our guide to native versus cross-platform development.
How much does a mobile app cost?
Broad UK ranges: a functional MVP on one platform £25,000-£40,000; a production app on both platforms with a backend and admin portal £40,000-£90,000; an enterprise app with integrations, offline capability and compliance requirements £90,000 upwards. Our cost breakdown explains what moves the number.
Do you publish to the App Store and Google Play for us?
Yes. We can publish under your developer accounts — which we recommend, so you own the listings — or set them up for you. Submission, review responses and phased rollout are part of delivery, not extra.
What happens when Apple or Google changes something?
Both platforms force annual SDK and API level upgrades, and privacy requirements change regularly. An app left alone for two years usually will not build, let alone pass review. This is the main reason we recommend a support agreement for anything in the stores.
Can the app work offline?
Yes, and for field-based use it is usually essential. We implement local persistence with a defined sync and conflict-resolution strategy. It adds meaningfully to scope, so it is a decision to make in discovery rather than halfway through the build.
Will you build a Progressive Web App instead if that is cheaper?
If a PWA genuinely meets your requirements we will tell you, and it is often a smart first step. The honest limits are push notification behaviour on iOS, background processing, some hardware access, and the fact that you get no store presence. If discoverability in the stores is part of your strategy, a PWA does not deliver it.
Talk to an engineer, not an account manager
Send us the problem and we will tell you honestly whether we are the right team, what a sensible first step is, and roughly what it costs.