Apps that feel like they came with the phone.

We design and build iOS, Android and web apps with the platform's own manners, then do the unglamorous work of getting them found and kept.

Built native

Everything we do, on one page

Building the app and getting it used, planned together. What the store listing promises is something the build has to keep.

iOS apps: Swift and SwiftUI, with the system gestures, widgets and settings people already know.
Android apps: Kotlin and Jetpack Compose, respecting back navigation, themes and the many screen sizes out there.
Web apps: Fast, accessible interfaces that work with a keyboard, a screen reader and a weak connection.
Backend and APIs: The services, data models and admin tools an app quietly depends on.
Product and UX design: Flows, prototypes and interface details, drawn to each platform's conventions.

Store listings: Titles, screenshots and descriptions written in the words people actually type into the search bar.
User acquisition: Paid campaigns planned around what a new user is actually worth to you.
Creators and social: Short-form content and creator partnerships that show the app doing its job.
Lifecycle and retention: Onboarding, notifications and messages that bring people back without nagging.
Analytics and A/B tests: Event tracking agreed before launch, and experiments that each start with a question.

Native: Using the controls, gestures and conventions each platform already taught its users. Nobody should need a tutorial for scrolling.
Fast: Measured on a modest phone on a bad train connection, not on our own desks.
Accessible: Readable with large text, usable with VoiceOver and TalkBack, and fine in dark mode. It is tested in the same pass as everything else.
Finished: Crashes watched, edge cases handled, release notes written. The dull parts are most of the job.

Plain names for the platforms and kinds of work involved, in case a proposal ever gets too clever.

iOS: iPhone and iPad, plus the places around the app: widgets, the share sheet, Shortcuts and notifications.
Android: Phones, tablets and foldables from many manufacturers, each with its own idea of the back button.
Web: Browsers on every kind of screen, including the marketing pages that send people to the stores.
Backend: The part nobody sees: accounts, sync and the jobs that run overnight.

Conversation

You tell us what the app is for and who it is for. We ask awkward questions early, while they are still cheap.
Shape

Flows, a clickable prototype and a plan for the first release, agreed while changes are still a matter of moving boxes.
Build and release

Short cycles with working builds you can install, followed by store submission and a launch plan.
Grow Then repeat

Store listing work, campaigns and retention experiments, guided by what real users do with the app.

Do you take on a project from scratch, or an app that already exists?

Both. With an existing app we start by reading the code and the reviews, then suggest what to fix first.

Who owns the code and the designs?

You do, by default. We set up repositories, design files and store accounts in your name where we can, and hand over the rest.

Can you only do the marketing side, or only the build?

Yes, either one. We think they work better together, and will mention it once.

How long does a first release take?

It depends on the scope, so we give an estimate after the shaping stage rather than guessing in a first email.

Do you work with teams outside the United Kingdom?

Yes. The company is registered in England, and the work happens remotely, so where you are makes little difference.