Analysis updated 2026-07-08 · repo last pushed 2022-08-20
Build a single Android app that ships to both Google Play and Huawei App Gallery without maintaining two codebases.
Generate separate staging and production builds for each platform to test before public release.
Use as a template to scaffold a new Android project that targets Google and Huawei ecosystems from day one.
| shanraisshan/google-huawei-flavor-buildtypes | azcomp2000/battery-sentinel | diredocks/cleanarchitecturenoteapp | |
|---|---|---|---|
| Stars | 1 | 0 | 0 |
| Language | Kotlin | Kotlin | Kotlin |
| Last pushed | 2022-08-20 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Android Studio with Kotlin support and familiarity with Gradle flavor and build type configuration.
This template project helps Android developers manage the headache of building one app for both Google Play and the Huawei App Gallery. Instead of maintaining two separate codebases, you write your app once and this setup lets you generate versions specific to each platform automatically. At a high level, it uses two built-in Android Studio features: "flavors" and "build types." Flavors split the code so you can include Google-specific services (like Google Maps or push notifications) in one version and Huawei-specific equivalents in another. Build types handle the environment, switching between a Staging version for testing and a Production version for your public release. The project combines these to produce four distinct app variations: Google Staging, Google Production, Huawei Staging, and Huawei Production. This is useful for developers building Android apps who want to reach both audiences, especially given Huawei's recent push for its own ecosystem separate from Google's. A startup shipping a retail app, for instance, could use this to serve users on standard Android phones and Huawei devices without duplicating their entire codebase. The template essentially provides the scaffolding so you can drop your app's code in and immediately start generating the correct builds. The README itself is fairly sparse on step-by-step detail, but it links to a full Medium article explaining the approach. It includes screenshots of both the Google and Huawei versions running, showing that the setup visually and functionally separates the two platforms. The main tradeoff here is a common one in Android development: you keep everything in one project for convenience, but the configuration can get complex as you add more platform-specific differences.
An Android Studio template that lets you build one app for both Google Play and Huawei App Gallery using flavors and build types, generating four app variations without maintaining separate codebases.
Mainly Kotlin. The stack also includes Kotlin, Android Studio, Gradle.
Dormant — no commits in 2+ years (last push 2022-08-20).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.