What makes one Android build cost more than another here?

The size of the test matrix, more than the number of screens. Five manufacturer skins is more work than two, and background work that has to survive all of them is more again, because each one has to be proved on a physical handset rather than reasoned about. A listing in two languages, and any application the manifest has to declare before the app can switch to it, both add scope that a feature list does not show. The general drivers of an app budget are set out on the solutions page; these are the ones specific to Android.

Our notifications do not arrive on some staff phones. Why?

Almost always the manufacturer’s power management rather than your code. Several of the skins common here freeze an application that has not been opened for a few days, and a frozen app receives nothing until someone opens it again. The send is accepted, your logs look clean, and the message never lands. The fix is a combination of message priority, the right kind of scheduled work, and an exemption the user grants inside the flow rather than in a settings screen nobody visits.

Which Android devices should we actually test on here?

One handset from each of the five manufacturers that carry this market, plus whatever your own analytics says your users hold. Statcounter put the August 2026 split at Samsung 17.82%, Xiaomi 16.59%, vivo 8.14%, OPPO 7.46% and realme 6.05%, which is a plurality rather than a leader, so a matrix built around a single vendor misses more than it covers. If you already have an app, the answer is in your own install base and we start there instead.

What does Google Play need from a UAE company to publish?

An organisation account with a D-U-N-S number, and a legal name and address that match the Dun and Bradstreet record Google checks against. That record has to agree with your trade licence, which is where UAE companies most often come unstuck: an entity that has moved premises, changed its licensed name, or opened the account under an individual will pass at launch and fail at a later verification. An unresolved mismatch can restrict the account and remove your apps, so it is worth confirming before the listing opens rather than after.

Can an Android app sign users in with UAE PASS?

Yes, and on Android it starts in the manifest. Since Android 11 an application cannot see what else is installed unless it declares what it needs, so switching to the national identity application is a declaration made in the scope rather than an integration discovered in sprint three. The flow itself registers your own URI scheme, runs in a web view and hands over when the identity application’s scheme appears. The approval to use it at all sits outside the build, and the Dubai page sets out what it waits on.

What does adding Arabic to an Android app later actually cost?

More than the translation, and the difference is layout. Android needs the right-to-left flag in the manifest, layouts written with start and end rather than left and right, and a mirrored resource set, so an interface built with hardcoded directions has to be revisited screen by screen. Done from the first sprint it is a flag and a discipline. Done at the end it is a second pass over the whole interface, plus the store listing, plus every screenshot.

We issue our staff their handsets. Does that change the build?

It shrinks the test matrix, which is the largest single cost driver on this page. A fleet standardised on one or two models is a build proved against those, with the manufacturer’s power management known rather than guessed, and the saving is real enough to be worth stating in the scope. It does not change the manifest, the listing or the Arabic decision. Procurement-led buyers concentrate in Abu Dhabi, and the city page covers what else changes there.

Android app development · UAE

Android apps that work on every UAE phone.

Kotlin and Jetpack Compose is the easy half. The skins decide whether a notification arrives and whether overnight work is still running in the morning.

Scope the Android side before you commit

What Android app development is

What Android app development involves here.

Android is roughly 78% of the handsets here. The useful fact is the shape of that share, because it decides the test matrix before it decides the code.

Built in Kotlin.

The stack Google ships its own apps on, with Material 3 and right to left settled at the manifest. Arabic is a build flag and a resource set, decided at the start, not a translation pass at the end.

The phones people here use.

Samsung, then Xiaomi, vivo, OPPO and realme, with no Android vendor above a fifth of the market. The four behind Samsung together carry more than Samsung does, and their skins are the ones that change behaviour.

Your Google Play listing.

An organisation account whose legal name and address Google checks against Dun and Bradstreet, a listing in both languages, and a staged rollout with a rollback. The listing is pinned to the trade licence.

The scope

What a native Android build gives you.

Six outputs from an Android engagement. Two are the app, two are the release, and two exist only because Android is a set of manufacturers rather than a platform.

Built in Kotlin and Compose.

The interface written in Compose and previewed as it is built, on the stack Google ships its own apps on

Output

an app that behaves as Android rather than as a wrapped page

KotlinCompose

Staged releases you can roll back.

A release that reaches 1% before it reaches everyone, with a halt you can pull

Output

a bad build caught by a hundred users rather than by all of them

StagedRollback

Tested on the phones people carry.

Samsung, Xiaomi, vivo, OPPO and realme, with a share against each and the strictest skin marked

Output

a written test matrix, agreed before sprint one

Five skinsSourced

Screens that work in Arabic.

Components, motion and dynamic colour to Material 3, with layouts written in start and end so a mirrored build is a resource set rather than a rewrite

Output

an interface that holds in both directions

Material 3Mirrored

Watch, TV and car screens.

The app extended to the watch, the screen or the car only where a user genuinely opens it there

Output

a surface roster you approved rather than a feature list

Wear OSAndroid Auto

Notifications that reach every phone.

Scheduled work, sync and notifications measured against Doze and against a strict manufacturer power manager

Output

an overnight job that is still running at 07:00

DozePer skin

What the skins change

The same app on strict Android skins.

The documentation describes stock Android. Most of this market is not running stock Android, and the difference shows up in the two things a business app depends on.

	Stock AndroidWhat the documentation describes	A strict OEM skinWhat a lot of this market runs	What we build againstThe strictest one in the matrix
An overnight sync	Runs in a maintenance window, roughly when the platform says it will.	The app is frozen after a few idle days and the job never fires.	Scheduled work proved on the strictest skin, with the exemption prompt in the flow.
Push with app closed	Delivered, usually within seconds of the send.	Delayed, batched or dropped once the app has been swiped away.	Delivery measured per skin on a real handset, never inferred from an emulator.
Seeing another app	Hidden since Android 11 unless the manifest names what it needs.	The same rule, plus permission screens of the manufacturer’s own.	The queries list written in the scope, so an app-switch works on first install.
Reproducing a report	An emulator reproduces the framework, not the manufacturer.	Reproducible only on that skin, which nobody on the team carries.	The handsets on the matrix are the handsets on the ticket, so it reproduces.

Which approach we recommend.

The size of the build, more than the feature list does. A matrix of five skins is more test time than a matrix of two, and a managed fleet on one handset is less than either, so it is agreed in writing before sprint one rather than discovered in support. The pillar sets out the decisions that sit above this one. If iOS is in scope too, the shared and per-platform split is here.

What we find on Android here

Which Android phones people here use.

Webzenia has worked with Gulf clients since 2018. Four things about an Android build here that the platform documentation will not tell you.

01of 04
The share has a shapeStatcounter, August 2026
No single Android brand holds a fifth of this market.
Samsung is 17.82%, then Xiaomi 16.59%, vivo 8.14%, OPPO 7.46% and realme 6.05%. A JLT commodities trader under DMCC whose warehouse staff carry their own handsets is testing against four skins, not one, and it is the skins that decide whether the dispatch notification arrives.
Our methodThe test matrix built from vendor share, then agreed in writing.
02of 04
The manifest is an allowlistSince Android 11
Your app must name the apps it opens.
Package visibility means the manifest has to declare each application the build needs to reach, so a national identity app-switch is a scoping decision taken before sprint one. Asking to see everything is a separate Play approval rather than a shortcut around it.
Our methodEvery app the build has to reach, enumerated in the scope document.
03of 04
The listing driftsQuietly, and then all at once
Google re-checks your name against your trade licence.
A Play organisation account is verified against a Dun and Bradstreet record. An Al Quoz logistics operator on a mainland DET licence that moves premises, or whose listing was opened under a former developer, finds this at renewal rather than at launch, which is the expensive time to find it.
Our methodThe Play organisation record checked against the trade licence, then re-checked.
04of 04
Arabic is a build flagNot a translation pass
Arabic layouts are set up at the start.
It needs the right-to-left flag, layouts written in start and end rather than left and right, and a mirrored resource qualifier. A Musaffah contractor on an Abu Dhabi mainland licence adding Arabic to a finished workforce app is not translating it, it is revisiting every layout in it.
Our methodThe manifest flag and the mirrored resources set in the first sprint.

What the engagement covers

Inside an Android build.

The engagement in six stages. The matrix and the manifest are settled in the first, because both of them price everything after.

Scope and the phone list.

The feature list, then the handsets and skins the build has to survive. A Sharjah SAIF Zone manufacturer whose distributors carry whatever their own market sells has a wider matrix than a company issuing its own devices.

Scope
Matrix

Design in Arabic and English.

Screens built to Material 3 with the right-to-left flag set and layouts written in start and end, so the Arabic build is a mirrored resource set rather than a second pass over every screen.

Material 3
Mirrored

Payments and sign-in wired.

Your APIs, the payment sheet, push and the identity app-switch. Each application the build has to reach is named in the manifest before it is reached in code.

Payments
Manifest

Testing on real phones.

The matrix run on physical handsets, with the strictest power manager treated as the reference rather than the exception. An emulator is honest about layout and dishonest about delivery.

Real devices
Strictest skin

Your listing in both languages.

Store copy, screenshots and release notes in English and Arabic, on an organisation account checked against the licence, released to a percentage rather than to everyone.

Two languages
Staged

Handover and documentation.

Code, documentation, the agreed device matrix and the list of every application the manifest declares. The next team inherits both decisions instead of re-deriving them from a bug report.

Documented
Matrix

Our stack

Built with Kotlin and Android Studio.

The language, the manifest, the delivery path, the listing and the crash log. Select one to see what it tells you and what it does not.

Kotlin

Why Kotlin

Kotlin is the language Google builds Android in, so a platform behaviour that changes in a release arrives with Kotlin support rather than behind a binding somebody else has to write.

How we excel

We keep the platform-behaviour code in one place rather than scattered through screens, because background limits and permission prompts are the parts most likely to change under you between releases.

Platform accessMaintained by GoogleLanguage

KotlinFirst class

JavaSupported

A cross-platform frameworkBindings

A web view shellBrowser

How the build runs

From the phone list to Google Play.

Two artefacts come out of week two and price everything after them. The device matrix, and the list of applications the manifest has to declare.

01Weeks 1 to 2Scoped

Agreeing the phone list.

We agree the device matrix in writing, from vendor share and from what your own users carry, and mark which skin is the reference for background work. In the same fortnight we list every application the manifest has to declare, and check the Play organisation record against the trade licence. All three price the build, and none of them is code.

Matrixagreed in writing
Manifestdeclarations listed
Listingchecked against the licence

02Weeks 3 to 10Built

Building it in Kotlin.

The app is built in Kotlin and Jetpack Compose to Material 3, with the right-to-left flag and start and end layouts from the first screen rather than after them. Push and scheduled work are instrumented so arrival is measured on a handset rather than inferred from an accepted send, and the strictest skin in the matrix is the one they are proved against.

Interfacebuilt in both directions
Deliverymeasured, not assumed
Referencethe strictest skin

03Month 3 onwardRunning

Rolling out in stages.

The release goes to a percentage before it goes to everyone, and the crash and delivery numbers are read grouped by manufacturer rather than as one total. A fault that affects a single skin is a rounding error in an average and obvious the moment the average is split, which is the difference between halting a rollout and finding out from a review.

Releasestaged, with a halt
Crashesgrouped by manufacturer
Rollbacka mechanism, not a hotfix

Reported per manufacturer, so a fault on one skin is visible before it is an average.

The matrix, in writing

Device matrixPer skinStaged

Our commitment

Four promises we put in writing.

An Android build goes wrong on a handset nobody on the project owns. These four exist because that is where the damage is done.

We agree the phone list first.
Named handsets and named skins, in writing, with the reference for background work marked. A test plan that says real devices and nothing else is a plan nobody can hold us to.
Notifications proved on the strictest phone.
Arrival is confirmed on a physical handset from each manufacturer in the matrix. An accepted send tells you the message left, which is not the claim anyone is actually making when they say push works.
Your Play account matched to your licence.
The legal name and address on the account are matched to the trade licence before the listing opens, and re-checked when either changes. An unresolved mismatch can take every app you have published down with it.
Every release can be rolled back.
A percentage first, the numbers read per manufacturer, and the halt is yours to pull. Shipping to everyone at once means the only correction available is another release.

Common questions

Android apps, answered.

The size of the test matrix, more than the number of screens. Five manufacturer skins is more work than two, and background work that has to survive all of them is more again, because each one has to be proved on a physical handset rather than reasoned about. A listing in two languages, and any application the manifest has to declare before the app can switch to it, both add scope that a feature list does not show. The general drivers of an app budget are set out on the solutions page; these are the ones specific to Android.
FAQ · 01
Almost always the manufacturer’s power management rather than your code. Several of the skins common here freeze an application that has not been opened for a few days, and a frozen app receives nothing until someone opens it again. The send is accepted, your logs look clean, and the message never lands. The fix is a combination of message priority, the right kind of scheduled work, and an exemption the user grants inside the flow rather than in a settings screen nobody visits.
FAQ · 02
One handset from each of the five manufacturers that carry this market, plus whatever your own analytics says your users hold. Statcounter put the August 2026 split at Samsung 17.82%, Xiaomi 16.59%, vivo 8.14%, OPPO 7.46% and realme 6.05%, which is a plurality rather than a leader, so a matrix built around a single vendor misses more than it covers. If you already have an app, the answer is in your own install base and we start there instead.
FAQ · 03
An organisation account with a D-U-N-S number, and a legal name and address that match the Dun and Bradstreet record Google checks against. That record has to agree with your trade licence, which is where UAE companies most often come unstuck: an entity that has moved premises, changed its licensed name, or opened the account under an individual will pass at launch and fail at a later verification. An unresolved mismatch can restrict the account and remove your apps, so it is worth confirming before the listing opens rather than after.
FAQ · 04
Yes, and on Android it starts in the manifest. Since Android 11 an application cannot see what else is installed unless it declares what it needs, so switching to the national identity application is a declaration made in the scope rather than an integration discovered in sprint three. The flow itself registers your own URI scheme, runs in a web view and hands over when the identity application’s scheme appears. The approval to use it at all sits outside the build, and the Dubai page sets out what it waits on.
FAQ · 05
More than the translation, and the difference is layout. Android needs the right-to-left flag in the manifest, layouts written with start and end rather than left and right, and a mirrored resource set, so an interface built with hardcoded directions has to be revisited screen by screen. Done from the first sprint it is a flag and a discipline. Done at the end it is a second pass over the whole interface, plus the store listing, plus every screenshot.
FAQ · 06
It shrinks the test matrix, which is the largest single cost driver on this page. A fleet standardised on one or two models is a build proved against those, with the manufacturer’s power management known rather than guessed, and the saving is real enough to be worth stating in the scope. It does not change the manifest, the listing or the Arabic decision. Procurement-led buyers concentrate in Abu Dhabi, and the city page covers what else changes there.
FAQ · 07

Keep exploring

Explore Mobile App Development

Part ofMobile App Development

iOS App Development

Native Swift, and the entity Apple publishes as seller.

Cross-Platform Apps

One codebase, and the parts written per platform.

Flutter Development

One widget tree, and an Arabic screen that mirrors itself.

React Native Development

For teams that already write React and have to hold it.

eCommerce App Development

A shopping app costed against the repeat order.

On-Demand App Development

Two-sided products where the fleet is the harder half.

Enterprise App Development

Internal apps for staff who are not at a desk.

SaaS App Development

Subscription products whose customer is a licensed company.

App UI/UX Design

A component system engineering builds from, in both directions.

Next step

Get your Android app scoped.

Send what the app has to do and which handsets your users carry. We will come back with the build shape and the test matrix it runs against.

Tell us what you need.

What Android app development involves here.

Built in Kotlin.

The phones people here use.

Your Google Play listing.

What a native Android build gives you.

Built in Kotlin and Compose.

Staged releases you can roll back.

Tested on the phones people carry.

Screens that work in Arabic.

Watch, TV and car screens.

Notifications that reach every phone.

The same app on strict Android skins.

Which Android phones people here use.

No single Android brand holds a fifth of this market.

Your app must name the apps it opens.

Google re-checks your name against your trade licence.

Arabic layouts are set up at the start.

Inside an Android build.

Scope and the phone list.

Design in Arabic and English.

Payments and sign-in wired.

Testing on real phones.

Your listing in both languages.

Handover and documentation.

Built with Kotlin and Android Studio.

From the phone list to Google Play.

Agreeing the phone list.

Building it in Kotlin.

Rolling out in stages.

Four promises we put in writing.

Android apps, answered.

Explore Mobile App Development

iOS App Development

Cross-Platform Apps

Flutter Development

React Native Development

eCommerce App Development

On-Demand App Development

Enterprise App Development

SaaS App Development

App UI/UX Design

Get your Android app scoped.