Retail, food & drink
Order again
- The job
- Reorder a favourite without searching for it.
- Tap target
- 3 taps
- Connected to
- Store + stock
- Payments
- Loyalty
Mobile app development
Apps people keep.
iOS and Android apps built around the one job your customers open them for, then connected to the bookings, orders, payments and data you already run.
- iOS
- Android
- Cross-platform
- App backends
- Store release
(02)One job
Built around one job.
People keep the apps that do one thing better than your website can. So we find that job first, then design every screen to get there in as few taps as possible.
Clinics, studios, salons
Book a slot
- The job
- Find a free time and book it on the spot.
- Tap target
- 3 taps
- Connected to
- Calendar
- Payments
- Reminders
Field teams & deliveries
Close a job
- The job
- Finish a job on site: checklist, photos, signature.
- Tap target
- 4 taps
- Connected to
- Job system
- Maps
- Customer record
Members & loyalty
Show a pass
- The job
- Open the membership card at the door, no login.
- Tap target
- 1 tap
- Connected to
- CRM
- Wallet pass
- Offers
(03)The right build
Which build fits the job?
There is no best way to build an app, only the right one for the job, the budget and the roadmap. Answer three questions to see where we would start.
Three questions
-
01Does it need the phone's hardware: camera, Bluetooth, background location or offline use?
-
02Should customers find it in the App Store and Google Play?
-
03Would one codebase for iOS and Android suit your budget and release plan?
Answer the questions to see where we would start.
-
Native
iOS + Android, built separately
Best when the app lives on the device: camera, sensors, offline work, heavy animation.
Two codebases to build and keep up to date.
-
Cross-platform
One codebase, both stores
Best for most business apps: bookings, ordering, accounts, field teams.
The deepest device features may need native modules.
-
Web app
Installable from the browser
Best for internal tools and quick pilots where store presence doesn't matter.
Limited hardware access, and no store listing.
A starting point, not a verdict. We confirm it in the first workshop.
(04)Sketch to store
From sketch to store.
Six stages, with something you can hold at the end of each. You try the app on your own phone from the first weeks, not on launch day.
-
01
Map the job
Who opens the app, when, and what they came to do. We map the journeys and cut everything that doesn't serve them.
You getJourney map + scope
-
02
Prototype
Clickable screens on your own phone within weeks, so the idea is tested with real people before anyone writes code.
You getClickable prototype
-
03
Design
A design system for iOS and Android: type, colour, components and every state, including empty, loading and offline.
You getUI kit + final screens
-
04
Build
The app and its backend, built in short sprints: accounts, APIs, payments and push. A new test build lands on your phone every sprint.
You getTest builds every sprint
-
05
Test
Old and new devices, slow networks, large text and screen readers. Crashes and accessibility issues are fixed before anyone outside sees them.
You getDevice + accessibility checks
-
06
Release
Store listings, screenshots, privacy details and review submission, then a staged rollout so nothing goes out to everyone at once.
You getLive in both stores
(05)Under the screen
The app is the front door.
An app is only as good as what sits behind it. We build the backend with it, or connect to the one you already have, so the app, the website and the team work from the same data.
- 01 Accounts Sign in once, on any device, with passwordless and social login.
- 02 Payments Cards, wallets and subscriptions, handled by your payment provider.
- 03 CRM Every booking, order and message lands on the customer record.
- 04 Push Reminders and updates triggered by real events, not blasts.
- 05 Analytics What people use, where they drop off, what to build next.
- 06 CMS Change content, prices and offers without a new app release.
- 07 Your systems Stock, schedules, jobs and accounts, through secure APIs.
(06)After launch
Launch is version one.
Phones update every year, and so do your customers' expectations. We stay on for the releases after the first, planned from what people actually use.
-
v1.0
Launch
- Book and cancel classes
- Check in at the door
- Reminders the day before
-
v1.1
Six weeks later
- Waitlist with automatic offers
- Membership pass in the phone wallet
-
v1.2
Next quarter
- Faster booking from the home screen
- Dark mode
- Larger text support everywhere
What we look after
- OS updatesTested and updated for each new iOS and Android release.
- StabilityCrash and performance monitoring, with fixes shipped fast.
- Store reviewsReviews read, answered and fed into the roadmap.
- Release planA monthly release rhythm, from what the analytics show.
(07)Selected work
Apps in use.
An app is one part of a connected build: the store, the booking system and the automation behind it.
All work
Sample project
A booking app for a group of wellness studios
One iOS and Android app for class booking, memberships and reminders, connected to the studios' existing schedule and payments.
- Mobile Apps
- Design
- Automation
Sample project
A specialty coffee store built for subscriptions
An editorial storefront with subscriptions, brew guides and product storytelling, designed and built as one.
- Websites
- Design
- Marketing
(08)Start an app
What should it do?
Tell us the one job your customers or team need done on their phone. We'll tell you how we would build it, and what it connects to.