Fixed shapes at published prices. If your engagement doesn't match one of the six, we'll say so before we quote.
Native Android app built lean. Kotlin, Jetpack Compose, MVVM. Six to fourteen weeks depending on shape. Includes Load, Build, Ship, Hand off. APK size and cold-start tracked from day one.
Four-week sprint on your existing Android codebase. We match your style, merge clean, hand back tests. Common asks: onboarding, subscription, offline mode.
Two-week deep read focused on APK size, cold-start, memory, battery, gradle build time. Written report with prioritised recommendations for the next quarter.
Previous team left. App is unreleased or badly leaking. We stabilise, ship a version to the Play Store, then set the ground for a considered lean rewrite.
You have an APK; we do the rest. Store listing, screenshots, feature video, staged rollout, first-week review-response process, monitoring dashboard.
Monthly capacity across your Android portfolio, used flexibly by your product team. Weekly async check-ins, quarterly efficiency review call. Three-month minimum.
We are Android-native and boringly opinionated. There are boring reasons for that.
100% of our production code. No Java, no cross-platform shims. Loopfrog writes what Android's own team writes.
Compose for all new work. If you're on classic Views we can integrate incrementally without breaking your ship rhythm.
Boring, understood, obvious. Room for persistence. Retrofit for HTTP. Hilt for DI. Coroutines and Flow throughout.
GitHub Actions CI. Fastlane for releases. Play Console via API. Staged rollouts by default. Firebase for crash + analytics.
Every PR reports APK delta and cold-start delta. Budgets set in the Load phase. Regressions fail the build, not the demo.
Your GitHub org. Your Play Console. Your Firebase. From day one. We're renters, not landlords.
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.