Mobile App Development
Cross-platform and native mobile applications, shipped through the stores and maintained after.
What this is
We have built and shipped mobile applications as part of our own commercial products, including rider and driver apps, so we build for what happens after launch: store review cycles, OS version churn, offline conditions and crash triage. Cross-platform by default, native where a platform capability genuinely requires it.
When teams call us about this
If more than one of these is familiar, there is usually a case worth scoping.
- An app shipped once and has not survived OS and store policy changes since.
- Separate iOS and Android codebases double every change.
- The app is unusable where connectivity is poor, which is where it is needed.
- Nobody monitors crash rates, so quality is discovered through store reviews.
What this covers
Each item below is part of this service line. Where an offering needs a specialist partner, it is marked as such rather than implied.
-
Android app development
Native Android where platform depth or performance requires it.
-
iOS app development
Native iOS for capability-specific or performance-critical applications.
-
Flutter app development
One codebase across iOS and Android with a consistent interface.
-
React Native development
Cross-platform delivery sharing skills and code with a React web stack.
-
Cross-platform app development
Platform choice assessed against your capability needs and team, then committed to.
What you receive
Artefacts that end up in your repositories and your cloud account, not locked inside our team.
- Applications published to the App Store and Google Play under your accounts
- Shared cross-platform codebase, or native where capability requires it
- Backend APIs, authentication and push notification infrastructure
- Offline handling and sync where the use case needs it
- Crash reporting, analytics and release monitoring
- Store listing assets, review submission and release management
- Build pipeline producing signed releases reproducibly
Typical engagements
The shapes of work we are asked for most often in this area.
Field and driver applications
Works offline, syncs when connectivity returns, respects battery and data limits.
Customer-facing app
Booking, ordering, tracking and account management on mobile.
Internal workforce app
Replaces paper and phone calls for staff working away from a desk.
Companion to a web product
Extends an existing platform to mobile without forking the backend.
How we run it
Discovery
Platform decision, capability requirements, offline needs and store constraints.
Design
Platform-appropriate interface design covering key flows and states.
Build
Increments with installable test builds distributed to your reviewers.
Testing
Device and OS version coverage, offline cases, automated tests on core logic.
Release
Store submission, review handling and staged rollout.
Support
Crash monitoring, OS version maintenance and release management.
Products we built and sold
Our own commercial platforms, built with this engineering stack. These are products, not client references.
RideOn
A ride-hailing and fleet management platform, now with agentic dispatch, driver support and demand intelligence.
View product Multivendor marketplaceUniBooker
A configurable multivendor service-booking marketplace with agentic onboarding, matching and support.
View product Classifieds marketplaceClassify
A classifieds marketplace with agentic listing creation, moderation and buyer-seller matching.
View productMobile App Development — FAQs
Including the questions where the honest answer is "it depends", and what it depends on.
Cross-platform or native?
Cross-platform unless there is a specific reason not to: it halves the maintenance surface. Native is justified by deep platform integration, demanding graphics or performance constraints. We make the call with you during discovery.
Who owns the store accounts?
You do. Applications are published under your developer accounts so you are never dependent on us for a release.
Do you handle store submission?
Yes, including listing assets, review responses and staged rollout. Review timelines are controlled by Apple and Google, so we plan releases around them.
What about ongoing maintenance?
Mobile needs it: OS releases and store policy changes break things independently of your code. We offer a maintenance retainer, or document the work for your team.
Services that pair with this
Custom Software Development
Applications shaped around how your business actually works, not around a product roadmap.
Read moreAPI Development & System Integration
Documented APIs and integration layers that keep your systems consistent without manual re-entry.
Read moreCloud, DevOps & Infrastructure
Infrastructure as code, CI/CD pipelines, containerisation and monitoring you can operate yourself.
Read more