Android Wear, Android TV and Android Auto will not include custom manufacturer UIs

Custom manufacturer overlays are a major part of Android, with nearly every device maker offering their own unique take on Google’s mobile operating system. Consumers that want a “pure” Android experience typically have to buy a Nexus or Google Play edition device straight from Google, which isn’t exactly ideal for folks that want to try something before they buy it. Thankfully for them, it sounds like “pure” Android Wear, Android TV and Android Auto devices will be easier to come by.

Speaking to Ars Technica, Google’s David Burke confirmed that the user interfaces and software featured in Android Wear, Android TV and Android Auto will all be controlled by Google itself. Burke, who works as Google’s engineering director, explained that “the UI is more part of the product” when it comes to Wear, TV and Auto, and that Google wants “a very consistent user experience.”

Burke also said that while the device makers can brand their hardware and include unique services, the main UI should be the same across hardware.

Finally, Burke revealed that Google will manage the updates for Android Wear, TV and Auto itself. Doing so will allow it to make those products “more like Chrome on the desktop” in that the update process will be automatic and smooth.

Lovers of pure Android are likely overjoyed by this news, as it means that they can choose just about any Android Wear, TV or Auto device without worrying about getting bogged down by a manufacturer’s custom UI. On the flip side, this news is a bit of a bummer because we’ve certainly seen some manufacturers add genuinely handy features with their custom Android smartphone UIs, and today’s announcement means that we may never see some of those goodies in Android Wear, TV and Auto.

What do you think of today’s news? Are you excited at the prospect of a bunch of pure Android Wear, TV and Auto hardware or would you like to see device makers be able to add some deep custom tweaks to the software?

Via Ars Technica

Disqus Comments