Full native Android
Kotlin-first with Jetpack Compose, MVVM/MVI structure, Retrofit and Room — complete apps with no Flutter, when native is the right call.
Service — Android App DevelopmentCairo, Egypt — open to remote
Android app development, Kotlin to Google Play
Android is where your users are — and where the fragmentation lives: dozens of manufacturers, screen sizes, battery killers and OEM quirks. I build Android apps that behave across that mess and ship through Google Play with release discipline most side projects never get.
Native when the job needs it — Kotlin and Jetpack Compose end to end. Flutter when one codebase for Android and iOS serves you better. The choice is made for your app, not out of habit.
3+ yrsprofessional experience
10+production apps today
EG · LB · AEclients served
What gets built:
Flutter, when shared
One codebase for Android and iOS with native modules where Android-specific work earns its keep — background services, hardware, widgets.
Hardware & device work
RFID/NFC readers, scanners, printers and MDM fleets through platform channels — Android as the tool, not just the toy.
Tested on real devices
Unit and instrumented tests, plus checks on the mid-range phones your users actually own — not just the flagship on my desk.
Play Store release
Signing, listings, internal/closed/open tracks, staged rollouts and post-launch vitals — release becomes routine, not a ritual.
- Product teams
You need Android delivered properly inside your roadmap — with architecture the next developer can read.
- Businesses going Android-first
Your audience is overwhelmingly Android (as it is in Egypt) — build where your customers are, with iOS as a planned second step or a shared codebase.
- Hardware-backed products
Access control, inventory, IoT companions — apps whose job is talking to devices reliably.
How it ships:
01Platform decision
A short, honest comparison for your case: native, Flutter, or hybrid — with the trade-offs written down.
02Architecture
Clean architecture and state management chosen per problem — the skeleton you'll keep for years.
03Build
Weekly APK/AAB builds you can install; real-device testing through the whole cycle.
04Release
Play Console end to end — tracks, staged rollout, crash and vitals monitoring after users arrive.
- Language & UI
Kotlin and Java both in service; Jetpack Compose for modern UI with classic Views where legacy demands it.
- Architecture
MVVM/MVI on the Jetpack stack, repositories, use cases — boring in the good way.
- Data & networking
Retrofit, Room, WorkManager for sync that survives process death and Doze mode.
- Fleets & MDM
Managed distribution and over-the-air updates for device fleets — proven on government work (DCT Abu Dhabi).
Shipped on Android: RFID access & inventory systems for Alexandria Sporting Club, universities and banks; MDM-managed government distribution; Unilever's offline-first field apps.
See the selected work on the main page →
Android-first? Good. Build there.
Describe the app and its audience — you'll get a straight platform recommendation with reasons, not a pitch for whatever I feel like building.