Apps people keep on the first screen
An app earns its place by being quicker than the website for the thing people do most. We build customer apps and staff apps that connect to the systems you already run, work on mid-range Android phones and patchy connections, and get through app review without drama.
- iOS and Android
- Works on mid-range phones
- Connected to your systems
- Published and maintained
- React Native
- Flutter
- Swift
- Kotlin
- Offline first
- Push notifications
How we help with mobile app development
Each piece can stand on its own, or run as one engagement with a single point of contact.
Customer apps
Ordering, booking, tracking and accounts, in an app that is quicker than your site for the frequent things.
- Accounts and notifications
- Payments in app
- Tracking and history
Staff and field apps
Apps for people who work away from a desk, built for one-handed use and bad signal.
- Works offline, syncs later
- Photos, signatures and scanning
- Location and routing
Cross-platform builds
One codebase for both stores when the app does not need platform-specific depth.
- React Native or Flutter
- Shared logic, native feel
- Faster to build and to change
Native builds
Swift and Kotlin when performance, hardware or platform features demand it.
- Device hardware access
- Background processing
- Platform design languages
Back ends and APIs
The part behind the app: accounts, data, notifications and the integrations that feed it.
- Secure APIs
- Push notification services
- Integration with your systems
Store publishing and updates
Getting through review, and staying there as the platforms change their rules.
- Store listings and assets
- Review submissions
- Version updates
Tested on the handsets your customers actually own
Apps are usually built on the newest phone in the office and then meet a four-year-old Android on 3G in a basement. We test on the devices and connections your users really have, because that is where an app is abandoned.
- Mid-range and older Android devices, not just flagships
- Designed to survive a dropped connection and resume
- Data use kept low for people on prepaid bundles
- Screens readable in sunlight and usable one-handed
- Battery and background behaviour checked before release
Four steps, and you can see all of them
No long silences. You see progress as it happens and can change direction between stages.
- 1
Define the job
We agree the one thing the app must do better than the website, and build outwards from that.
- 2
Prototype
A clickable prototype you can put in front of staff or customers before anything is built.
- 3
Build and test
Short cycles, with test builds on your own phones throughout.
- 4
Publish and maintain
We handle both stores, then keep the app current as the platforms change.
Both stores reject apps for reasons that have nothing to do with code. We handle submissions, and we build with their rules in mind rather than discovering them at the end.
What we build with
Chosen to suit the job and to be maintainable by whoever comes next.
- React Native
- Flutter
- Expo
- Swift
- Kotlin
- SwiftUI
- Jetpack Compose
- Laravel
- Node.js
- Push notifications
- Analytics
- Crash reporting
Cross-platform for most business apps; native when the app depends on hardware, performance or a platform feature that cannot be bridged.
Where this work usually starts
Retail and delivery
Ordering, tracking and loyalty for customers who buy often.
Field teams
Engineers, surveyors and delivery staff who need the system in their hand.
Services with bookings
Clinics, salons, studios and workshops where the calendar is the business.
Membership organisations
Cards, renewals, events and announcements in one place.
Businesses with a busy website
Customers who return weekly and deserve something quicker than a browser.
Companies with an app that stalled
A half-finished or abandoned app that needs rescuing or replacing.
Mobile App Development, answered
Do I need an app or a better website?
Often a better website. An app is worth it when people come back often, need it offline, or need the phone's hardware. We will say so if a website would serve you better.
Do I need an app or a better website?
Often a better website. An app is worth it when people come back often, need it offline, or need the phone's hardware. We will say so if a website would serve you better.
Tell us what people would use it for
Describe the one job the app has to do and we will tell you whether it is worth building, and what it would take.