min 24
Max reach.
97.3% coverage. Missing notification channels, adaptive icons, Material You. Compatibility work cost is real.
§
§ · android app development
Android development, minimum SDK 26.
Kotlin + Jetpack Compose-first Android apps covering 94 percent of active devices at min SDK 26. Material 3 dynamic color, Baseline Profiles, and Play Store 2026 policy compliance included.
On this page
§ 01 · the fragmentation question
Android does not ship to one device. It ships to thousands.
The first decision in every Android build is minimum SDK.
Too low and you write compatibility code for APIs nobody uses. Too high and you cut yourself off from the users you wanted to reach. Our default is min SDK 26 (Android 8.0): it covers 94.1 percent of active devices and unlocks every modern API most apps actually need.
Higher minimums only make sense for specific Material You requirements. Lower minimums only for apps genuinely targeting legacy devices.
in short
- Jetpack Compose + Kotlin as the default, XML/View system only for legacy migration.
- Min SDK 26 (Android 8.0) covers 94.1% of active devices. Targeting newer Android versions trades reach for API access.
- Material You via Material 3 design system + dynamic color tokens; Compose previews + Play Store policy compliance baked in.
- Performance: Baseline Profiles, R8 minification, < 2s cold start, > 99.5% crash-free verified on real mid-tier devices (Pixel 6a, Galaxy A35).
- Four engagement shapes: 2-week audit (refundable), greenfield Compose build, View→Compose migration, retainer. Client owns Play Console + keystore.
min 26 · our default
Sensible floor.
94.1% coverage. Notification channels, adaptive icons, autofill, background limits. The meaningful install base without legacy debt.
min 29
Scoped storage era.
84.2% coverage. Gesture nav system, dark theme API, scoped storage. Right for modern storage-heavy apps.
min 31
Material You.
72.8% coverage. Dynamic color, new splash API, stricter background. Right for brands leaning into Material You.
min 33+
Latest-only.
54.1% coverage. Predictive Back, per-app language, Photo Picker. Only when newest APIs are a hard requirement.
target SDK
2026 Play Store.
target SDK 34 or 35 required for new submissions and updates. Separate from min SDK. Non-negotiable.
§ 02 · kotlin + jetpack compose
Compose is the stated future. We ship it.
Jetpack Compose in 2026 is production-mature and Google's stated future for Android UI.
It's declarative, Kotlin-native, and tightly integrated with Material 3 and the modern Android toolchain. We ship Compose-first on every new build.
XML layouts stay for maintaining existing codebases and specific edge cases. The default is Compose.
compose wins
- ✓Declarative state model with clear recomposition boundaries
- ✓Material 3 + dynamic color first-class
- ✓Animation API ergonomic for complex motion
- ✓Compose for Wear OS, Compose Multiplatform for sharing with iOS/desktop
- ✓Preview tooling in Android Studio excellent
where xml still fits
- ✓Maintaining existing XML-based codebases where conversion cost exceeds value
- ✓Complex custom ViewGroup needs not yet well-served in Compose
- ✓Third-party libraries still View-based with no Compose wrapper
- ✓AndroidView interop when a specific widget has no Compose equivalent
§ 03 · the fragmentation grid, in motion
Thirty-six devices. One minimum SDK.
We test against a 36-device matrix that represents minimum coverage for every Android engagement.
The matrix includes Pixel 5/6a/8, Galaxy A35/S22, Xiaomi Redmi, OnePlus Nord, tablets, and foldables. Real-device runs catch OEM skin issues that emulators miss every time.
§ 04 · play store 2026 policy
Play Store policy in 2026 is stricter. Be ready before submission.
Google Play has tightened requirements consistently since 2022. For 2026 submissions, we run a pre-check before Publish.
When the pre-check passes, first-rejection rate is under 5 percent.
the 2026 pre-submission pass
- target SDK within 1 year of latest (target SDK 34 or 35 in 2026)
- Data Safety form completed with accurate data-type disclosures
- Privacy policy URL publicly accessible and app-specific
- Account deletion flow present for any app with sign-up
- Play Integrity API for apps handling payments or sensitive actions
- Per-app language settings supported (system-level locale override respected)
- Predictive Back gesture properly handled (animation, not just callback)
- Minimum 16KB page size support (required for apps targeting Android 15+)
- Accessibility minimums: content descriptions on interactive elements, 4.5:1 contrast
- App Bundle (AAB) delivery, not APK; signed via Play App Signing
§ 05 · material 3 + dynamic color
Material You is the Android design language in 2026.
Material 3 with dynamic color adapts your app's palette to the user's wallpaper.
For min SDK 31+ apps, dynamic color is close to a default expectation for premium Android feel. We build a Material 3 theme scaffold with brand tokens that fall back to a fixed color scheme below API 31.
The result feels like a first-class Android citizen on Pixel, Samsung One UI, and most OEM skins. We track Play Console policy updates as they change.
tier 01
Material tokens.
Brand color roles (primary, secondary, tertiary, surface) expressed as Material tokens. Typography scale, shape scale, elevation tokens.
tier 02
Dynamic color.
API 31+: dynamic color derives from wallpaper. Your brand color becomes the fallback. Users can opt back to brand-only in settings.
tier 03
Motion + haptics.
Material motion (easing, duration tokens). Haptic feedback on interactive events via HapticFeedbackConstants. Makes the app feel premium.
§ 06 · performance SLA
Baseline Profiles and sub-2-second cold start.
We target cold start under 2.0s on mid-tier Android, 60 FPS frame budget, over 99.5% crash-free over 30 days, and APK under 50 MB per device.
Targets are verified via Macrobenchmark and Baseline Profiles, never on the engineer's flagship.
| metric | target | note |
|---|---|---|
| cold start | < 1.8s | mid-tier Android, Baseline Profile |
| warm start | < 500ms | process resume |
| frame rate | 60 fps | sustained scroll + animations |
| APK split (per-device) | < 15 MB | ABI split + resource qualifiers |
| ANR rate | < 0.20% | Play Console vitals |
Two archetypes. One consumer, one B2B.
These are industry archetypes drawn from patterns across consumer DTC and B2B field-tools engagements.
One ships Material You dynamic color and WorkManager-heavy background sync. The other ships enterprise-MDM-aware Compose with tablet-first layouts. These patterns describe the work we typically ship.
archetype 01 · media + news
Compose-first news app, 300K DAU.
Subscription news app. Jetpack Compose, Material 3 dynamic color, Play Billing subscriptions, offline reading queue via WorkManager, dark theme. Baseline Profile shaved cold start from 2.6s to 1.5s.
DAU
300K
12mo post
cold start
1.5s
Pixel 6 p75
ANR
0.09%
30d
archetype 02 · field service
Rugged-tablet enterprise app.
Enterprise field service app for rugged tablets (Zebra, Panasonic). Min SDK 26 (older device support required). Offline-first with WorkManager sync, barcode scanner integration, signature capture. 18 weeks.
devices
2,400
deployed
offline hrs
12
before sync
crash-free
99.78%
Play Vitals
§ 08 · engagement + fit
Four shapes. Audit names the right one.
We offer four engagement shapes: 2-week readiness audit, greenfield Compose build, View to Compose migration on legacy apps, or retainer with named senior engineers.
We scope the right shape before any contract.
shape 01
Readiness audit.
2 weeks. Min SDK decision, policy review, Compose readiness. Refundable.
shape 02
Android MVP.
10-16 weeks. Kotlin + Compose + Play Store submit.
shape 03
Full build.
14-22 weeks. Play Billing, WorkManager, Baseline Profiles, ABI split.
shape 04
Phone + Wear OS.
16-26 weeks. Phone + tablet + Wear OS one codebase.
right fit
- ●Android is primary or Android-first for your market
- ●Material You + dynamic color matters for premium feel
- ●You need Jetpack Compose and Kotlin-native maturity, not a wrapper
- ●Play Store policy compliance requires specialist attention
wrong fit
- ×Need iOS + Android with shared codebase; see React Native or Flutter
- ×Marketing wrapper for a web site; a PWA is cheaper
- ×Consider iOS-first; see iOS development
Eight answers.
These are the questions Android teams ask most before booking a readiness audit.
What minimum SDK should we target in 2026?
Min SDK 26 (Android 8.0) is our default for 2026. It covers 94.1 percent of active devices and unlocks the APIs most modern apps need: notification channels, adaptive icons, background limits, autofill, and a clean Kotlin runtime.
Going lower to 24 adds only 3 percentage points of coverage at the cost of legacy compatibility work. Going higher to 31 gains Material You dynamic color but loses 22 percent of users.
For brands with specific Material You visual identity needs, min SDK 31 is worth the trade-off. For everyone else, 26 is the sensible floor.
How much does a native Android app cost in 2026?
Senior rates: US and UK $145-$200/hr, India $90-$135/hr.
Kotlin + Jetpack Compose MVP (15-25 screens, auth, push, Play Store): 10-16 weeks. Full production build (Material 3 dynamic color, Play Billing, WorkManager, Baseline Profiles, ABI split): 14-22 weeks. Kotlin Multiplatform (phone + tablet + foldable + Wear OS): 16-26 weeks.
2-week audit is refundable. Scoped quote in 48 hours.
Jetpack Compose or XML layouts in 2026?
Jetpack Compose for new builds, always. It's production-mature in 2026 and the stated future of Android UI.
The declarative model, Kotlin-native code, preview tooling, and tight Material 3 integration outweigh the small migration cost. XML layouts stay only for maintaining existing XML-based codebases or specific edge cases (complex custom ViewGroups, some third-party libraries).
For a new Android app in 2026, start with Compose.
What are the Play Store 2026 policy requirements?
Key 2026 requirements: target API within 1 year of latest (target SDK 34 or 35), Data Safety form completed, privacy policy URL, account deletion flow if sign-up exists, Play Integrity API for sensitive actions, per-app language settings, Predictive Back gesture respected.
Medical, financial, and children's apps have additional policies we pre-check. We run a full policy pre-check before every submission.
How do you handle Google Play Billing and in-app purchases?
Play Billing Library version 7+ on all new builds. We implement subscriptions, non-consumable and consumable purchases, introductory pricing, promo codes, and family-shared entitlements.
Backend verification uses Real-Time Developer Notifications (RTDN) via Google Cloud Pub/Sub for subscription lifecycle events. For brands shipping Apple, Google Play, and web, we abstract the purchase layer so subscription logic stays platform-agnostic.
Refund and grace period logic follow Play policy requirements.
Do you support Wear OS, tablets, and foldables?
Yes. For tablets and foldables, we use WindowSizeClass to drive adaptive layouts (compact, medium, expanded) from the same Compose code. Foldable-specific features like hinge-aware layouts are supported via Jetpack WindowManager.
For Wear OS, we build companion apps with Compose for Wear OS, Tiles, Complications, and Watch Face Studio integrations where relevant. We scope Wear OS as an add-on to a phone build when your use case benefits from wrist-first interactions.
How do you optimize app launch time and performance?
Baseline Profiles are the biggest win. They precompile hot paths ahead of first launch, reducing cold-start time by 20-40 percent on mid-tier Android. We generate them from Macrobenchmark tests, ship them with the release, and verify impact in Play Console vitals.
Beyond that: R8 full mode for minification, APK split by ABI to reduce per-device download size, App Bundle delivery for large assets, and WorkManager for background work that respects Doze and App Standby.
Who owns the Google Play account, signing, and codebase?
You do. Google Play Developer Console ($25 one-time) under your legal entity. App signing key enrolled in Play App Signing (Google manages upload key, backup in your keystore). GitHub repository under your organization from day one.
Play Console access is under your control with DH engineers as named collaborators, removable anytime. On exit: credentials rotated, repository transferred, CI configuration documented, 30-day support tail.
No lock-in through signing, tooling, or vendor choice.
Start with a readiness audit.
Two weeks to map min SDK, review Play Store policy, assess Compose readiness, and plan Baseline Profiles. Refundable.
Scoped quote in 48 hours.
related services
More from Ryan.
Senior UX Designer · APAC · Sydney · 3 posts on the site
Published · Last updated .
