Do You Actually Need a Huawei AppGallery App?

Huawei devices don't ship with Google Mobile Services, so there is no Google Play Store on them and no standard Android app distribution. The logical conclusion is that reaching Huawei users means building and maintaining a separate app in Huawei's own AppGallery. We used to think so too. Our own usage data across client apps says otherwise: fewer than 5% of users ever download the Huawei-specific version.

That number is the whole argument, and it is worth being clear about what kind of recommendation follows from it. Bridzia can build a Huawei version, and still does when there is a reason to. This is not a capability we lack. It is a build we have watched go unused often enough to stop recommending it by default.

Why the demand isn't there

The gap between "Huawei needs its own app" and "almost nobody downloads it" comes down to something most planning conversations miss. A meaningful share of Huawei device owners already have a way to access the standard Google Play Store version, through workarounds that have been common knowledge in Huawei-using communities since the original Google services ban. Users who have already gone through that setup simply install the regular Android app like everyone else.

The remaining Huawei-specific audience, people who haven't done that and are relying purely on AppGallery, turns out to be a small fraction of the device's actual user base. Device market share counts handsets. It does not count the people who would reach for a second app that most of them have no need of.

The cost side isn't small either

A Huawei build isn't a recompile of the Android app. Huawei Mobile Services and Google Mobile Services diverge on several things a typical retail app actually depends on, push notifications, maps, and certain payment or in-app purchase integrations among them. A genuine Huawei build means swapping those dependencies for Huawei's equivalents, testing them separately, and maintaining a second release pipeline going forward.

That is real, ongoing engineering time rather than a one-off cost, because every future update needs to go out on two separate app stores with two sets of platform-specific quirks.

Putting the two together

Under 5% adoption, weighed against a genuinely separate codebase and release process to maintain indefinitely, is a hard number to justify for most retail apps.

We still build Huawei versions when there is a specific reason to: a client whose customer base is disproportionately on Huawei devices for a known reason, a market where that is genuinely different, or a specific business requirement. As a default recommendation for most clients, we now advise against it.

The honest version of "should I build a Huawei app" is usually this: check your actual expected adoption against the ongoing cost of a second codebase, and in most cases the answer comes back no.

What we actually recommend

If you're planning a mobile app and want an honest read on which platforms are actually worth building for, not just which ones are technically possible, talk to us about Mobile Application Development.