Android holds roughly 45–55% of the Kuwait smartphone market (depending on demographic) and dominates among delivery drivers, blue-collar workers, and budget-conscious consumers, exactly the audiences for delivery, fintech, and government apps. We build native Kotlin Android apps (and Flutter cross-platform apps when iOS parity matters) for Kuwait businesses at 10 KWD/hour, shipping production-ready in 6–12 weeks.
What we deliver
- Native Kotlin app with Jetpack Compose UI, Material 3 design, and Coroutines + Flow for clean async code.
- Arabic RTL throughout, proper text alignment, mirrored icons, Hijri/Gregorian date handling, Arabic numeral toggle, Cairo/Tajawal font integration.
- KNET payments in-app, Custom Tabs to MyFatoorah/Tap with proper deep-link return, webhook verification, and a fallback for KNET timeouts.
- Authentication, Firebase Auth with phone OTP (Kuwait +965 numbers), Google sign-in, Apple sign-in (yes, on Android, for App Store reviewers if you also publish iOS).
- Push notifications via Firebase Cloud Messaging with bilingual content, action buttons, and per-user opt-in management.
- Offline-first architecture, Room database, WorkManager for sync, sensible behavior on Kuwait 4G that drops mid-session.
- Google Play submission, content rating questionnaire, data safety form, screenshots in Arabic + English, and the staged rollout process.
- CI/CD, GitHub Actions or Bitrise, Firebase App Distribution for QA builds, Play Console internal/closed/open testing tracks.
Why Android matters for Kuwait apps
While iPhone has strong middle-class share in Kuwait, Android is overwhelmingly the device used by delivery drivers, restaurant staff, taxi drivers, expat workers, and many government employees. If your app serves any of these audiences, a delivery operations app, a restaurant kitchen display, a field-service tool, a labor-camp services app, Android-first or Android-equal is correct. Building iOS-only and assuming everyone has an iPhone is one of the most common (and expensive) mistakes Kuwait startups make.
Android also gives you more flexibility for the things iOS restricts: background services, custom share targets, deep filesystem access, NFC payments, custom keyboards, accessibility services, alternative app distribution (APK download from your site, useful for B2B), and the new Play Billing updates for in-app purchases. We use these capabilities where they make the product better.
Our process
- Week 1, Discovery: user research with real Kuwait users on their actual phones (often older Samsung A-series or Xiaomi devices), competitive analysis of Kuwait Android apps, scoping the MVP.
- Week 1–2, UX and design: Figma flows, Material 3 components, RTL variants, Arabic typography testing on the slowest device the audience uses.
- Week 2–4, Build (alpha): Kotlin + Jetpack Compose, modular architecture, Hilt for DI, Ktor or Retrofit for API. Firebase Auth, FCM, Crashlytics integrated from day one.
- Week 4–6, KNET + business logic: payment flow, order management, push notifications, offline sync, deep links.
- Week 6–8, Beta + Play Console setup: Internal track on Play Console, closed testing with your team and 10–20 real Kuwait users, crash and ANR tuning.
- Week 8–12, QA, staged rollout, launch: production keystore, Play App Signing, content rating, data safety, staged rollout starting at 10% to catch issues before they affect all users.
Technology stack
- Kotlin 2.x + Jetpack Compose, modern Android default. Coroutines + Flow for async, Hilt for DI, Room for local DB, DataStore for prefs.
- Flutter 3.x as an alternative when you need iOS + Android with one codebase. We build native when the app is Android-only or when the performance/UX bar is highest.
- Firebase, Auth, Firestore or Realtime DB (situational), FCM, Crashlytics, Analytics, Remote Config, App Distribution.
- Networking: Retrofit + OkHttp, or Ktor Client. JSON via kotlinx.serialization.
- Backend (if we build it): Node.js / FastAPI / Laravel, deployed to AWS Bahrain, GCP Dammam, or Cloudflare Workers.
- Payments: KNET via MyFatoorah or Tap Payments using Chrome Custom Tabs, Apple Pay via web checkout where applicable, Google Pay for international cards.
- CI/CD: GitHub Actions, Bitrise, or Codemagic. Play App Signing for upload keys.
Pricing breakdown
| Feature / Phase | Hours | Cost (10 KWD/hr) |
|---|---|---|
| Discovery + UX flows + Figma design | 27 | 270 KWD |
| Core Kotlin + Jetpack Compose UI | 80 | 800 KWD |
| Arabic RTL + bilingual content management | 20 | 200 KWD |
| Auth (phone OTP, Google, Apple) | 17 | 170 KWD |
| KNET payments + order flow | 20 | 200 KWD |
| Push notifications (FCM) + deep links | 10 | 100 KWD |
| Offline-first + sync | 17 | 170 KWD |
| Backend API + admin (if needed) | 40 | 400 KWD |
| Play Console setup + screenshots + submission | 10 | 100 KWD |
| QA + staged rollout + 30-day support | 20 | 200 KWD |
| Typical MVP total | 261 | 2,610 KWD |
KuwaitDev vs typical Kuwait Android shop
| What you need | KuwaitDev | Typical shop |
|---|---|---|
| Modern Kotlin + Compose (not legacy XML) | Yes | Java + XML still common |
| Arabic RTL tested on real devices | Day 1 | Bolted on at the end |
| KNET payments inside the app | Custom Tabs, deep-link return | Redirect with broken return |
| Crashlytics + analytics from day 1 | Yes | Added when something breaks |
| Staged Play Console rollout | Yes, 10/25/50/100% | Push to 100% directly |
| Post-launch support | 30 days included | Hourly |