Kotlin 2.x + Compose product work
New features and full apps on Kotlin 2.x with K2 compiler, Jetpack Compose with strong-skipping mode, Material 3 with dynamic color, Hilt DI, Room/DataStore persistence, Coroutines + StateFlow.
Services
Native Android engineering on Kotlin 2.x and Jetpack Compose for consumer and B2B products targeting phones, tablets, foldables, Wear OS, and Android Auto. We ship Google Play-ready bundles that pass Data Safety review on the first submission, handle the annual targetSdk bump, and support EU User Choice Billing where eligible. Dedicated Android teams from 12,000 EUR/month, fixed-scope project sprints from 25,000 EUR. CET workday with 9 AM–1 PM ET overlap, GDPR-aligned by default.
GDPR-aligned · ISO 27001 ready · SOC 2 Type II in progress · HIPAA-capable · CCPA-acknowledged · CET workday with 9 AM–1 PM ET overlap
Android is where global volume lives and where Google Play policy gets stricter every year. The Data Safety form must match the actual SDK behaviour or the listing gets pulled. Account Deletion is mandatory in-app and from the web. targetSdk has to track the latest release within one year or new installs stop. Foreground service types on Android 14+ broke a generation of apps that worked fine on Android 13. EU DMA opened User Choice Billing and alternative distribution for the categories Google was forced to open. We build Android apps that survive all of this — Kotlin 2.x with the K2 compiler, Compose-first UI, Baseline Profiles for cold start, and a Data Safety form that is actually accurate. See it in practice in our Refactoring xRouten case study.
New features and full apps on Kotlin 2.x with K2 compiler, Jetpack Compose with strong-skipping mode, Material 3 with dynamic color, Hilt DI, Room/DataStore persistence, Coroutines + StateFlow.
Data Safety form audited against actual SDKs, in-app + web account deletion, foreground service types declared correctly, restricted permissions justified, Pre-Launch Report crashes fixed before release.
Play Billing Library 7.x with base-plan/offer subscriptions, price-change consent flows, EU User Choice Billing pilot where eligible, alternative distribution APKs for DMA-relevant categories.
Java to Kotlin, XML Views to Compose, RxJava to Coroutines, AsyncTask/Loader to ViewModel + StateFlow, SupportLibrary to AndroidX, Gradle Groovy to Kotlin DSL with version catalogs.
Macrobenchmark and Microbenchmark, Baseline Profiles generated per release, cold start under 500 ms on Pixel 6a-class devices, Perfetto traces for jank, R8 full mode with proper keep rules.
Wear OS 4/5 with Compose for Wear, Tiles and Complications, Android Auto + Automotive OS apps, foldable continuity with WindowSizeClass, large-screen quality tier for Play Store.
Week 1: audit existing module graph (or define scope), pick targetSdk/minSdk, run a Google Play policy gap analysis (Data Safety, Account Deletion, permissions), write the baseline.
Weeks 2–3: module graph, Gradle KTS + version catalog, Hilt + DI graph, CI on GitHub Actions with Fastlane supply, internal Play track, Crashlytics + Performance Monitoring wired.
Two-week sprints, internal Play track build every Friday, weekly demo, Crashlytics + Pre-Launch Report review every Monday, Data Safety form re-checked against the SDK list every sprint.
Staged rollout on Play Console (1 percent → 5 → 20 → 100), Android Vitals monitored for ANR rate and crash rate, hotfix path tested, retrospective, then back into cadence.
Senior Android engineer + tech lead + QA + PM allocation, your repo, your sprint board, daily standup. From 12,000 EUR/month, three-month minimum, then month-to-month with 30 days notice.
Fixed scope, fixed price, 6–12 weeks. Compose migration of a feature module, Play Billing 7 upgrade, targetSdk bump with foreground-service refactor, Wear OS companion. From 25,000 EUR.
One or two senior Android engineers embedded in your team. Your standups, your code review, your release process. From 9,500 EUR per engineer per month, monthly rolling.
All engagements include NDA, DPA, and full IP assignment signed before kickoff. CET workday with 9 AM–1 PM ET overlap for US founders.
Most agencies keep the number for a sales call. Here are our published US & EU planning ranges so you can budget before discovery. Every app is scoped individually, but these three bands cover the common path from an embedded engineer to a full dedicated Android team.
From 9,500 EUR / engineer / month. One or two senior Android engineers embedded in your team — your standups, your code review, your release process. Monthly rolling.
From 25,000 EUR · 6–12 weeks. Fixed scope, fixed price: Compose migration of a feature module, Play Billing 7 upgrade, or a targetSdk bump with foreground-service refactor.
From 12,000 EUR / month. Senior Android engineer + tech lead + QA + PM allocation; a standard two-engineer product team runs 28,000–34,000 EUR/month. Three-month minimum, then month-to-month.
What moves the number: how many form factors you ship (phone-only vs phone + tablet + Wear OS + Android Auto + foldables — each surface adds design and QA); the depth of legacy migration (Java→Kotlin, XML Views→Compose, RxJava→Coroutines); how many restricted permissions and third-party SDKs the Data Safety form has to justify; billing complexity (Play Billing subscriptions, EU User Choice Billing, DMA alternative distribution); and compliance scope (GDPR-aligned, HIPAA-capable, or PSD2 raises the bar). A single-surface Compose app on clean data sits at the bottom of the sprint band; a multi-surface product under a DPA writing to production systems sits at the top. Google Play and third-party API fees are billed on your own accounts, so you keep the cost lever.
Android + iOS refactor and rebuild for a German last-mile logistics operator — multi-point route planning, real-time driver tracking and in-app invoicing live in the EU.
Unified iOS & Android app for remote alarm, embedded video and smart-home control across the US & EU — zonal entitlement, role-based access.
Native iOS & Android fitness-marathon and challenge app — programs, stats, and leaderboards on a Laravel backend, for the US & EU.
An Android app is only as safe as its fit with your regulatory and operational reality. We pair native Kotlin engineering with industry-specific compliance across US & EU markets, and share a codebase and release process with our iOS and cross-platform mobile teams when a product ships on both stores.
Secure Android banking and payment apps with hardware-backed Keystore, BiometricPrompt, PSD2 SCA flows and PII kept out of Crashlytics — Play Data Safety filled from the real SDK list.
FinTech apps →HIPAA-capable, GDPR-aligned Android apps for intake, records and fitness — EU-region backends, documented data flows and account-deletion in-app and from the web, as on our MFIT fitness build.
HealthTech apps →Driver and last-mile Android apps with multi-point route planning, real-time tracking and in-app invoicing over changing state — live in the EU on our xRouten build for a German operator.
Logistics apps →Native Android storefronts and loyalty apps grounded in your catalogue, with Play Billing subscriptions, deep links, offline-first Room caching and staged Play Console rollouts.
Retail apps →GDPR-aligned · ISO 27001 ready · SOC 2 Type II in progress · HIPAA-capable · CCPA-acknowledged
Every engineer on the roster has shipped at least three production Android apps and worked through the Java→Kotlin and View→Compose migrations. No juniors billed at senior rates.
Data Safety form audited every sprint, Account Deletion shipped before launch, targetSdk roadmap planned, restricted-permission justifications written and submitted before the deadline.
GDPR with IAB TCF v2.2 via Google UMP, CCPA Do Not Sell, EU User Choice Billing where eligible, DPAs with every third-party SDK, PII scrubbing in Crashlytics and analytics.
For regulated products we run a HIPAA or PSD2 gap assessment in week 1 and design the data flows accordingly — secrets stay in EncryptedSharedPreferences or hardware-backed Keystore, biometric prompts use BiometricPrompt with CryptoObject.
The legacy Android app had years of accumulated debt and no iOS counterpart. YuSMP refactored the existing code, shipped the iOS version, and added live driver tracking and in-app invoicing — all without stopping daily operations for our drivers.
Our iOS and Android apps had diverged over years of separate development. YuSMP rebuilt a single unified solution with live camera feeds, smart-home device control, and role-based multi-user access. Zero critical defects in the first six months post-launch.
New projects start on Kotlin 2.x with the K2 compiler, target SDK 35 (Android 15), and set minSdk to 26 (Android 8.0) which covers roughly 95 percent of active US/EU devices. Google Play's policy requires targetSdk to be within one year of the latest major release, so we plan SDK upgrade sprints into the annual roadmap. For B2B fleet apps on rugged devices we drop minSdk to 24 (Android 7.0) with isolated AndroidX backports. Jetpack Compose is the default UI layer; View/XML interop is kept for legacy modules and CameraX/PdfRenderer paths where Compose is still catching up.
We run a pre-flight against the most common rejection categories: Data Safety form mismatched against actual SDK behaviour, missing Account Deletion (required since May 2024 in-app and from the web), foreground service types not declared correctly on Android 14+, restricted permissions without a Permissions Declaration Form (SMS, Call Log, AccessibilityService, MANAGE_EXTERNAL_STORAGE), and Families policy violations. We also fix the Pre-Launch Report crashes Google runs on Firebase Test Lab devices before our internal release, which catches 80 percent of post-publish 1-star reviews.
Google Play Billing Library 7.x is the default for digital goods (Play policy still requires it inside the Play distribution channel for most categories). For EU users we implement the User Choice Billing pilot where eligible — users see Play Billing alongside the developer's own processor, with the corresponding service-fee reduction (3 percent). For DMA-relevant categories we support alternative distribution via direct APK install flows with the proper Install Unknown Apps user prompts, and we keep a separate Play track for the same app. Subscriptions use the new base-plan/offer model with proper price-change consent flows.
Compose-first since 2023 for all new code: Compose 1.7+ with the strong-skipping mode, Compose Navigation with type-safe routes, Compose Material 3 with dynamic color, and Compose for Wear OS where the product extends to watches. ViewModels use Kotlin Coroutines and StateFlow, dependency injection via Hilt, data layer with Room and DataStore. We still embed AndroidView/ComposeView interop for CameraX preview, AdMob native ads, ExoPlayer (Media3), and PdfRenderer until Compose-native equivalents are production-ready. Baseline Profiles are generated for every release to keep cold start under 500 ms on mid-range devices.
GDPR-aligned by design: lawful basis documented per data category, Google's User Messaging Platform (UMP) SDK for IAB TCF v2.2 consent in the EU, granular data export and account deletion (also a Play policy requirement), and DPAs with every third-party SDK. The Data Safety form is filled from a single source of truth that we audit against the actual SDKs in the bundle — mismatch is the #1 cause of policy enforcement actions. For EU customers we host backend infra in eu-central-1 or europe-west3, enable Android Privacy Sandbox where the product uses ad attribution, and keep PII out of Crashlytics/Sentry with breadcrumb scrubbing.
Pricing starts at 12,000 EUR/month per dedicated team (one senior Android engineer + part-time tech lead, QA, and PM allocation). Standard product team is two senior Android engineers + tech lead + QA + designer + PM at 28,000–34,000 EUR/month. Project sprints (e.g. Compose migration of one feature module, Play Billing 7 upgrade, targetSdk bump with foreground-service refactor) start at 25,000 EUR for a 6-week fixed-scope engagement. CET workday with 9 AM–1 PM ET overlap. Three-month minimum on dedicated teams, then month-to-month with 30 days notice.
Practical guides on Android development, costs, and cross-platform choices.




Share a few details and a senior consultant will reply within one business day.