The practice
App Development
Android, iOS, and the web apps behind them. Built when an app is genuinely the right answer, and said plainly when it is not.
Most businesses that ask for an app need a faster website. The ones that genuinely need an app need it for something specific — a booking a customer repeats every month, a catalogue a field team carries into a shop, a membership worth a place on the home screen.
We have built on Android, Kotlin and Flutter for years, and we will tell you in the first conversation which of the three your project wants — or that it wants none of them.
What it covers
The scope.
- Android and iOS apps
- Flutter cross-platform builds
- Native Kotlin development
- Progressive web apps
- Booking and appointment apps
- Catalogue and order-taking apps
- Loyalty and membership apps
- API and backend integration
- Play Store and App Store release
How we work on it
Where we differ.
We will talk you out of it
An app earns its keep only if somebody opens it twice. Before any scoping we test the idea against that — how often, by whom, for what. A good share of the app conversations we have end with a better website and a smaller invoice, and we would rather lose the project than build something that sits unopened on a phone.
Honest scoping
Opened-twice test
One codebase where one will do
Flutter covers most of what mid-market clients actually need, at roughly half the cost of two native builds. We go native when the brief genuinely calls for it — deep hardware access, heavy graphics, platform-specific integrations — and not as a default.
Flutter / Kotlin
Cost-matched stack
The store is part of the build
Review rejections, privacy declarations, signing keys and staged rollouts are the part that quietly sinks timelines. They sit inside our scope, and the developer accounts are in your name from the first day.
Play Store / App Store
Client-owned accounts
How it is engaged
Terms, plainly.
Ten to twenty weeks depending on scope, at a fixed fee billed against staged milestones. A short paid discovery comes first on anything substantial, so the estimate rests on a written specification rather than a guess.
After release, apps need a retainer in a way websites do not: operating-system updates, store policy changes and SDK deprecations arrive whether or not there is budget for them. We price that separately and say so before you commit.
Fifteen minutes.
No fee, no deck, no pitch. Tell us what you are trying to build and we will tell you honestly whether an app is the right answer — and whether we are the right studio for it.