Nine years of Android in production. Jetpack Compose that doesn't recompose wastefully, Kotlin coroutines that don't leak, architecture that handles the fragmentation most teams ignore. Three billion users deserve an app that works on a $120 phone.
Why Entalogics for Android
God Activities, XML nobody touches, a networking layer that crashes on config change, and zero thought for budget devices. We've inherited all of it. We fix the architecture before the Play Store reviews do.
We profile on mid-range hardware from day one. Recomposition tracing, baseline profiles, R8 shrinking. Smooth on budget devices isn't a bonus — it's where most users live.
Each feature is a Gradle module with its own screen, ViewModel, and tests. Build times drop. Teams don't step on each other.
ViewModels expose StateFlow collected with lifecycle awareness. UI state in a sealed interface — Loading, Success, Error. Impossible states stay unrepresentable.
Sealed classes for state machines. Value classes for domain primitives. Kotlin Serialization at every API boundary. When the backend changes a field, the build fails — not the app.
When native, when not
Kotlin and Compose give you the deepest platform access. They also cost the most. We'll tell you on the first call if native is genuinely justified.
GO NATIVE WHEN
CONSIDER CROSS-PLATFORM WHEN
WE SAY NO WHEN
What we build for Android
The shapes of native Android work we ship most. Each built for the Play Store — not a hackathon demo.
Onboarding, Play Billing, FCM push, App Widgets, Dynamic Feature delivery. Consumer polish that survives real user hands.
Offline-first with Room, barcode scanning, NFC, GPS tracking, MDM compliance. Built for the warehouse and the construction site.
Adaptive layouts with WindowSizeClass, multi-pane UIs, large-screen optimisation. One app for phone, tablet, and foldable.
Tiles, complications, health services. A Wear app that extends your phone app — not a stripped-down afterthought.
Replace the spreadsheet your field team uses. Offline capture, photo evidence, GPS logging, sync when connectivity returns.
ComposeView inside existing Fragments. Screen by screen, no flag-day. The current app stays live while we modernise.
The playbook
Android patterns from production apps — not Codelabs.
P01
New screens in Jetpack Compose. XML only for legacy screens not yet migrated. No mixed-for-no-reason codebases.
P02
ViewModelScope for screen-scoped work. WorkManager for guaranteed background execution. No AsyncTask, no RxJava on new code.
P03
Each feature is its own module. Build cache improves. CI parallelises. Two engineers work without touching the same build file.
P04
Material 3 tokens extended with your brand. Light/dark, dynamic colour, large-screen density from a single token source.
P05
Compose screenshot tests for visual regression. Espresso for critical flows. CI runs on every PR against real emulators.
P06
ComposeView inside existing XML layouts. One screen at a time. The app ships continuously.
Signature case
An enterprise logistics app — 8s cold start on target devices, Activities averaging 4,000 lines, no offline despite warehouse use with spotty connectivity. Rebuilt in Kotlin Compose with Room and WorkManager in 11 weeks. Rating went from 2.8 to 4.5.
Before
Java XML · cold start 8s · avg Activity 4,000 lines · no offline · rating 2.8★
After
Kotlin Compose · cold start 1.8s · avg screen 320 lines · offline-first · rating 4.5★
Engagement shape
A typical Android engagement. We build screen by screen — never a six-month rewrite. The current app stays on the Play Store while we work.
Two senior Android engineers. Baseline profile analysis, recomposition tracing, module audit. A ranked, dollarized RFC.
Compose baseline, Gradle modularisation, Hilt wired in, one production screen end-to-end. Real numbers on a mid-range device.
Feature by feature under feature flags. Internal track releases weekly. Your roadmap keeps moving.
Store listing, compliance, first submission. Runbook handed to your team — or we stay on retainer.
Stack
Picked for production Android — not tutorial starters.
Engagement
No hourly retainer that bills for "thinking time." Pick a lane that matches your stage; everything is fixed-quote or transparently rated.
A defined product, a fixed price, a senior-only team. From RFC to Play Store submission in 8–14 weeks.
$15k–$30k
FIXED SCOPE
Embedded engineers in your Slack, your Linear, your standups. Senior Kotlin engineers. Pause, resize, end with 30 days' notice.
$5k / eng / mo
PER ENGINEER
A long-term partner for product orgs shipping across Google's ecosystem — phone, tablet, foldable, Wear OS.
custom
PROCUREMENT-FRIENDLY
Founder-direct
Thirty minutes with the founder. We'll bring a senior Android engineer, the relevant playbook, and a candid read on whether native Kotlin is the right call — or whether cross-platform gets you there faster.
