Mobile app development
Mobile App Development
Build secure iOS and Android applications connected to reliable backend systems, payments, notifications and operational workflows.
Plan the right mobile experience
We first compare a responsive web experience with an app-store product against the tasks, devices and distribution needs of your users. The delivery plan includes the backend and support needed alongside the app.
- What to bring
- Bring the user tasks, target devices and any offline or distribution requirements.
- What we agree first
- A platform recommendation and screen flow, with a plan to test the riskiest requirements.
Illustrative example · fictional data
Field app concept and platform choice
Your visits
09:00 · Equipment check
11:30 · Follow-up visit
2 records waiting to sync
Open visit (concept)Record the work
Checklist: 4 of 5 complete
Photo: attached
Offline · saved on this device
Submit when connected (concept)- Reach users
- Open a link; installation may be available
- Install through an agreed distribution channel
- Offline and device features
- Support varies; test target browsers and devices
- Platform APIs and permissions still need testing
- Updates
- Web deployment, with cache/version handling
- Store rollout and older installed versions
- Choose when
- Link-based access suits the task
- Distribution or deeper platform integration matters
| Requirement | Web app | App-store product |
|---|---|---|
| Reach users | Open a link; installation may be available | Install through an agreed distribution channel |
| Offline and device features | Support varies; test target browsers and devices | Platform APIs and permissions still need testing |
| Updates | Web deployment, with cache/version handling | Store rollout and older installed versions |
| Choose when | Link-based access suits the task | Distribution or deeper platform integration matters |
Where this fits
- Customers or field staff need a mobile experience suited to their devices and daily tasks.
- An existing app is unreliable, outdated or expensive to maintain.
- Work happens offline or in the field, away from a reliable connection.
- Mobile access needs to stay connected to the same data as the web platform.
Benefits to work towards
- A mobile experience tested against agreed user tasks
- A shared release plan for iOS and Android
- An application connected to the required business records
Compare a web app with an app-store product
Offline work, notifications, camera access and location are not exclusive to native applications. Progressive web apps can offer many of these capabilities, but support, permissions and restrictions vary by browser, operating system and device. Test the requirements on the devices your users actually have.
A web app is easy to reach through a link and can suit occasional tasks. An app-store product may suit deeper platform integration, distribution requirements or a frequent dedicated workflow. The choice depends on the whole journey, including updates and support.
Shared code still needs platform testing
Flutter can share substantial code across iOS and Android. Device integrations, permissions, payments and store release requirements still need platform-specific work and testing. We assess those dependencies before estimating a build.
Plan beyond the first release
Include authentication, backend compatibility, crash reporting, rollout and maintenance in the scope. Users may run different app versions, so the server and data format need a compatibility plan.
See MDN’s overview of progressive web apps for the web-platform capabilities behind this comparison.
Mobile features and delivery
Platforms and release
- Cross-platform mobile development
- Flutter capabilities
- Native-platform integrations
- App Store and Google Play delivery
User experience
- Authentication
- Push notifications
- Subscriptions and payments
- Offline and synchronised data
- Geolocation
Connected operations
- Administration platforms
- Mobile API development
Typical use cases
A service business wants a booking app for customers.
A field team needs an app with offline data capture.
A subscription product needs in-app payments and renewals.
Technical confidence
A mobile application normally also needs a backend API, authentication, a database, an administration interface and monitoring. We design the whole system, not just the screens.