The latest Google Mobile Services agreement states that OEMs' custom gesture navigation controls for Android must be enabled only via settings moving forward
October 2019 Dan Grabham / Pocket-lint : Google is discouraging other Android phone makers from using their own navigation systems Tyler Lee / Phandroid : Android 10 might require custom third-party navigation gestures to be hidden Phillip Prado / Android Authority : Google hides OEM navigation systems on Android, can't include in setup Cory Gunther / Gotta Be Mobile : October Pixel Android 10 Update: What to Know João Carrasqueira / Neowin : Google will apparently force OEMs to hide custom Android navigation gestures Justin Diaz / Android Headlines : Google Working On Certification Program For Gaming Devices Jon Fingas / Engadget : Android 10 phones may have to hide third-party navigation gestures David Oh / Android Police : Google to make mobile gaming more predictable and performant with Gaming Device Certification Abdullah / Gizchina : Google works on a certification program for Android gaming smartphones Ron Amadeo / Ars Technica : OnePlus 7T Review: Not very new, but still one of the best phones you can buy Michael Allison / MSPoweruser : Google will make it harder for Android 10 OEMs to showcase custom gestures Joe Maring / Android Central : Android 10 will make it harder to use third-party gesture navigation Tweets: Tochi / @enyibinakata : @Techmeme @NexusBen With over 80% of market share in the bag, Google begins to take more and more control of Android. Open source my foot Mishaal Rahman / @mishaalrahman : Part 1 of ? There's a lot more to share! https://twitter.com/...
Context & Ripple Effects
This lands in the same fall 2019 window as Google's Pixel 4 launch, when Google was shipping its own gesture navigation as the flagship Android interaction model. The new Google Mobile Services term doesn't ban OEM gesture systems outright — it moves them out of the setup flow and into settings, meaning every newly activated Android phone boots into Google's navigation by default. Separately, the same reporting cycle surfaced a [[/entity/google-working-on-certification-program-for-gaming-devices-jon-fingas-/-engadget|Gaming Device Certification program]] under development, showing the licensing apparatus expanding into new device categories.
First-order effects
- OEMs that built custom gesture navigation — a visible software differentiator — must now bury it behind a settings toggle, ceding the out-of-box first-run experience to Google's own navigation system.
Second-order effects
- With the setup screen no longer available as a differentiation surface, phone makers are pushed to compete on hardware and preloaded services instead, while Google demonstrates that GMS certification terms can be used to steer core UX decisions across the entire Android ecosystem.
Third-order effects
- If the pattern holds, the GMS agreement functions less as a compatibility checklist and more as a design-governance instrument — standardizing Android's interaction layer around Google's choices and narrowing the software customization space that historically distinguished Android vendors, a dynamic likely to draw antitrust scrutiny of licensing terms.
The trend: Google is using its Mobile Services licensing terms to consolidate Android's core user experience around its own design, trading OEM customization for platform consistency.