Android... without Google
summary
Claims a single codebase can target Google and non‑Google Android by using product flavors, manifest merging, interfaces and DI, and shows that maps, location and analytics can be swapped (Google Maps → OSMDroid/OpenStreetMap, fused location → raw location, Firebase → Segment) with near‑identical UX. Uses DexCount and Gradle dependencyInsight to find GMS usage, builds a Gradle plugin to call Amazon’s Publishing API and uploads app bundles, runs non‑Google binaries on Firebase Test Lab, and cites Huawei shipping ~250M devices with ~50% non‑OHA units.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:19Why consider non-Google Android
- 9:37Identifying dependencies on GMS
- 15:37Replacing Google Play Services
- 20:29Architecting app without GMS
- 27:51Building for platform differences
- 30:41Deploying to alternative stores
- 33:23Distribution strategies overview
- 35:06Recap and key takeaways
related talks
27mRemoving Google from smartphones
53mHuawei Mobile Services Vs Google Play Services?
16m/e/OS, My Android Smartphone Without Google
41mWrite once, ship multiple times
18mAndroid in Automotive, the Real Fragmentation
32mAndroid Open Source: What more can we do with Android?
28mEffective Gradle Scripts for Android Projects
55mCompilers. Dalvik. ART. And everything in between