Six services. One catalogue.

Fixed shapes at published prices. If your engagement doesn't match one of the six, we'll say so.

◆ 01 · Full build

Concept to Play Store.

Native Android app built from the kernel out. Kotlin, Jetpack Compose, MVVM, Room, Retrofit. Six to sixteen weeks depending on shape. Includes Load, Build, Ship, Hand off.

From £42k · 6–16 wk
◆ 02 · Feature sprint

A single feature, done right.

Four-week sprint on your existing Android codebase. We match your style, merge clean, hand back tests. Common asks: onboarding, subscription, offline mode.

£18k · 4 wk fixed
◆ 03 · Platform audit

A written map of what's true.

Two-week deep read of your Android codebase. Written report covers architecture, crash rate, build times, release pipeline, prioritised recommendations for the next quarter.

£6.5k · 2 wk
◆ 04 · Rescue & rewrite

Get the app back on the rails.

The previous team left. The app is unreleased or badly leaking. We stabilise, ship a version to the Play Store, then set the ground for a considered rewrite.

From £24k · Scoped case-by-case
◆ 05 · Play Store launch

Submission and staged rollout.

You have an APK; we do the rest. Store listing, screenshots, feature video, staged rollout, first-week review response process, monitoring dashboard.

£4.5k · 2 wk
◆ 06 · Retainer

A long-term engineering shape.

Monthly capacity across your Android portfolio, used flexibly by your product team. Weekly async check-ins, quarterly strategy call. Three-month minimum.

From £8k / month · 3-month min
Stack

The tools we use.

We are Android-native and boringly opinionated. There are boring reasons for that.

◆ Language

Kotlin.

100% of our production code. No Java, no cross-platform shims. Kernel writes what Android's own team writes.

◆ UI

Jetpack Compose.

Compose for all new work. If you're on classic Views we can integrate incrementally without breaking your ship rhythm.

◆ Architecture

MVVM · Clean-ish.

Boring, understood, obvious. Room for persistence. Retrofit for HTTP. Hilt for DI. Coroutines and Flow throughout.

◆ Pipeline

Actions + Fastlane.

GitHub Actions CI. Fastlane for releases. Play Console via API. Staged rollouts by default. Firebase for crash + analytics.

◆ Testing

JUnit, Turbine, Espresso.

Unit-first, instrumented where it counts. We ship with meaningful coverage and screenshots.

◆ Ownership

Your GitHub.

Your GitHub org. Your Play Console. Your Firebase. From day one. We're renters, not landlords.

Which shape fits?

Tell us the outcome you want and we'll point you at one of the six. If none fit, we'll tell you that too.