Services · Mobile app development · Android app development

Android apps that run well on the phones your customers really carry.

Q: Should we publish on Huawei AppGallery too?

Only if a meaningful share of your audience uses newer Huawei phones. Newer Huawei devices lack Google Mobile Services, so features like push and maps need Huawei equivalents. We look at your analytics or market research first. If Huawei users are a small group, the extra build and store work may not be worth it yet.

Q: Which Android versions will the app support?

We agree a minimum version with you based on your users, not a default. Supporting very old versions adds testing time and limits which modern libraries we can use. We check your existing analytics where they exist and suggest a cut off that covers the people you need without carrying old phones nobody uses.

Q: How long does Google Play review take?

Often a few days, but plan for longer on a first release. New apps and new developer accounts tend to get closer scrutiny, and Google may ask for testing, policy or data safety changes. We set up the account early and build review time into the launch plan, so a Ramadan or product launch date is not put at risk.

Q: Who owns the app and the signing keys?

You do, from the first day. The Play Console, AppGallery account, source repository and app signing setup are created under your company. We work as invited users. If you move to another team later, nothing has to be transferred back from us.

Q: How long does it take to build an Android app?

A focused first release usually takes a few months; complex apps take longer. The timeline depends far more on scope and integrations than on Android itself. A first release with sign in, a core flow, payments and notifications can often be ready in a few months once designs are agreed. Apps that connect to several internal systems, work offline or need Huawei services take longer. We give you a sprint plan after discovery, show progress with a build every sprint, and flag scope changes as soon as they affect the date.

Q: What do you need from us to get started?

A decision maker, access to your systems, and a clear picture of your users. We need one person on your side who can make decisions quickly, plus access to the APIs or systems the app relies on, or the people who own them. Brand assets, Arabic copy approval and test accounts all save time. If you already have a Play Console account, we ask for a developer invitation rather than your password. We also ask early about any legal or compliance review your organisation needs before release, so it can be planned in.

Q: Can you work alongside our in house developers?

Yes. We can lead the build or slot into your existing team. Some clients want us to own the Android app end to end; others have backend or web developers in house and want our Kotlin engineers to work inside their repositories and processes. Either works. We agree branching, code review and release responsibilities up front, document the architecture as we go, and keep the code in your own Git repository so your team can read and extend it without depending on us.

Q: What happens after the app is live?

We monitor, fix and keep it compatible with new Android releases. Launch is the start of the useful work. We watch crash reports, ANRs and reviews, fix issues quickly, and plan small updates based on what users actually do. Each year Google raises the target API level and Android itself changes permissions and background rules, so the app needs regular maintenance to stay in the store. We offer an ongoing support arrangement, or we hand everything over cleanly if your own team will take it on.

Native Android app development in Kotlin for UAE businesses whose customers use everything from flagship Samsungs to budget handsets and Huawei phones without Google services. We build, test on real devices, and take the app through Google Play and, where it makes sense, Huawei AppGallery.

Get in touch All mobile app services

Built for: UAE businesses with Android heavy audiences: delivery, field service, healthcare, retail and real estate apps used across many device types.
Typical timeline: A first internal build in four to six weeks. A focused app usually reaches Google Play in three to five months.
What you own: The Kotlin source code, your Play Console and AppGallery accounts, signing keys and every design file, all in your name.
Rated: 4.7 / 5 from 23 Google reviews

In short

Android in the UAE is not one platform. A delivery rider, a nurse on shift and a property investor may all use Android, on hardware that ranges from the newest foldable to a three year old handset with little memory. We plan for that spread from the first sprint: we agree a minimum Android version with you, test on a shelf of real devices rather than one emulator, and keep the app light enough to start quickly on modest phones.

Huawei deserves its own conversation. Newer Huawei phones ship without Google Mobile Services, so Firebase push, Google Maps and Google sign in do not work as expected. If a meaningful share of your users carry these phones, we add Huawei Mobile Services equivalents for push, maps and location, and publish to AppGallery as well as Google Play. If they do not, we tell you, and you save the effort.

Arabic is built in, not bolted on. We write layouts that mirror properly for right to left, use Arabic numerals and fonts where your audience expects them, and check every screen in both languages before release. Logins usually run on UAE mobile numbers with one time codes, and support or sales hand off to WhatsApp, so we design those flows carefully. Personal data is handled with the UAE PDPL in mind, and for health or finance apps we suggest confirming storage and hosting rules with your regulator early.

Google Play has its own rhythm. Apps must keep up with Play's target API level requirements each year, declare their data safety details accurately, and pass review before each release. We set up your Play Console under your company, use staged rollouts so a bad build reaches a small share of users first, and watch crash and ANR reports after every launch, with extra care around Ramadan and sale periods when usage peaks.

Before the first sprint, it helps to prepare a few things. Bring a short list of the tasks your users must complete, the systems the app will talk to, such as your CRM, booking engine or ERP, and any brand guidelines you already have in English and Arabic. Analytics from your website or an existing app tell us which devices and Android versions your customers really use, which is far more reliable than guessing. If you have a Google Play developer account already, we confirm who holds the owner role, because recovering a lost account later is slow and frustrating.

A mistake we often see is treating the Android app as a smaller copy of the iPhone app, designed on an iPhone and then squeezed onto Android. Android users expect the system back button, Material patterns for sheets and menus, and notifications that respect channels they can switch off individually. Another is building the app before the backend is ready, so the team ends up mocking data for weeks. We plan the API and the app together, so both arrive at the same time and the first real test happens early rather than in the final fortnight.

Our Kotlin engineers sit in our Dubai Silicon Oasis office alongside the wider team of 80+ across Dubai, Riyadh and Karachi. You can review builds with us in person, test on our devices, or keep it all on WhatsApp and video calls.

200+ companies servedFrom a first store to an ADX listed developer

What you get

Native Android, built for the device mix in the UAE.

We build in Kotlin with Jetpack Compose, test on real hardware across price points, and handle Play Store and AppGallery publishing so the app reaches every Android user you care about.

Explain your project

Kotlin and Jetpack Compose
Modern native Android code with Compose interfaces, coroutines for background work and a clean architecture your next developer can follow.
A codebase that is easy to extend, not a rewrite in two years.
Real device testing
Testing across flagship, mid range and budget phones, different screen sizes and older Android versions you agree to support.
Fewer surprises from users on phones nobody tested.
Huawei and AppGallery
Huawei Mobile Services for push, maps and location where Google services are missing, plus AppGallery publishing when your audience justifies it.
Huawei users get an app that actually works for them.
Arabic and right to left
Mirrored layouts, Arabic typography and bilingual content checked screen by screen in both languages.
Arabic speakers get an app that feels native, not translated.
Payments and wallets
Card payments through your UAE gateway, Google Pay and saved cards, with secure handling of tokens and receipts.
Checkout that works on the phones your buyers use.
Offline and low signal
Local caching and sync for field teams, basements, car parks and sites where the connection drops.
The app keeps working when the signal does not.
Play Store release
Play Console setup, data safety declarations, closed testing tracks, staged rollouts and release notes in English and Arabic.
Releases that go out in stages, with a way to stop a bad build.
Monitoring after launch
Crash, ANR and performance reporting reviewed after each release, with fixes prioritised by how many users they affect.
Problems found by us before your customers report them.

Who this is for

Three Android situations we are asked to help with.

Most Android work that reaches us starts from one of three places: a new app, an app that struggles on cheaper phones, or an audience that includes many Huawei users.

You need a new Android app for a UAE audience

We start with who your users are and which phones they carry, then agree the minimum Android version, languages and integrations before design begins. The first internal build arrives early so you can hold it, not just look at slides. We agree the scope of a first release that is small enough to ship and useful enough to learn from.

Device mix agreed before design.

Your app is slow or crashes on budget phones

We profile startup time, memory and battery on low end devices, fix the worst screens first, and clear the crash and ANR backlog in order of how many people it hurts. We profile startup time, memory and network calls on modest devices, then fix the causes rather than the symptoms.

Fix the phones your users actually own.

A large share of your users carry Huawei phones

Push notifications, maps and sign in quietly fail without Google services. We add Huawei equivalents behind a common layer so one codebase serves both, and publish to AppGallery. We check your analytics first, so the extra AppGallery work is justified by your actual audience.

One codebase, two stores.

Four stages, with a build in your hand early.

01DiscoverUsers, devices, languages, integrations and the minimum Android version, agreed in writing. We also confirm which devices and Android versions your real users carry, using your analytics where you have them.
02DesignScreens in English and Arabic, tested as a clickable prototype with real users where possible. Designs follow Material conventions where they help and are reviewed in Arabic as well as English before build starts.
03BuildTwo week sprints in Kotlin, each ending with a build you can install and try. Every sprint ends with an installable build you can try on your own phone and share with colleagues.
04ReleasePlay Console and AppGallery submission, staged rollout and monitoring after launch. After launch we stay close to the crash and ANR reports through the first few weeks of real traffic.

How we work together

Three ways to work with our Android team.

Android projects usually run as a fixed scope build for a defined first release, then move to a monthly retainer for updates and new features. Teams with their own product manager often add one or more of our Kotlin developers to their squad instead.

Fixed scope

A defined build with a deadline

We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.

Written scope and acceptance criteria
Fixed price and delivery date
Weekly build on a URL you can open
30 days of fixes after launch

Get in touch

Dedicated team

A product that keeps evolving

Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.

Senior engineers, not a rotating bench
Your tools, your repo, your process
Monthly, cancel with 30 days notice
A lead who answers for the team

Get in touch

Retainer

Something live that needs looking after

A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.

Agreed response times
Monitoring and dependency updates
A monthly report of what changed and why
Priority access to the same team that built it

Get in touch

Technology

What we build this with.

Native Kotlin for the app itself, with a backend and cloud chosen to fit your team.

01Android

Kotlin

02Backend and data

Node.js
PostgreSQL
MongoDB

03Cloud

AWS
Azure

Questions people ask before building an Android app.

Do we need native Android, or can one cross platform app cover both stores?

It depends on how much the app leans on the device itself.

If your app relies heavily on Bluetooth, background location, camera processing or deep Android integrations, native Kotlin is usually the safer choice. For many content, booking and commerce apps, Flutter or React Native serves both platforms well. We will tell you which we would choose for your case and why.

Should we publish on Huawei AppGallery too?

Which Android versions will the app support?

How long does Google Play review take?

Who owns the app and the signing keys?

How long does it take to build an Android app?

What do you need from us to get started?

Can you work alongside our in house developers?

What happens after the app is live?

Services that usually go with this one.

Mobile app developmentEvery mobile service we offer, native and cross platform.iOS app developmentThe Swift side of the same product, built to match.App store optimisation (ASO)Store listings in Arabic and English that people find.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews

Android apps that run well on the phones your customers really carry.

Native Android, built for the device mix in the UAE.

Kotlin and Jetpack Compose

Real device testing

Huawei and AppGallery

Arabic and right to left

Payments and wallets→

Offline and low signal

Play Store release

Monitoring after launch

Three Android situations we are asked to help with.

You need a new Android app for a UAE audience

Your app is slow or crashes on budget phones

A large share of your users carry Huawei phones

Four stages, with a build in your hand early.

Three ways to work with our Android team.

Fixed scope

Dedicated team

Retainer

What we build this with.

Questions people ask before building an Android app.

Services that usually go with this one.

Tell us what the business needs. We will tell you what to build first.

Payments and wallets