Will Verduzco · Jun 29, 2014 at 01:35 pm

Google to Take Back Platform Control with Android Wear, Auto, and TV–That’s a Good Thing, But Questions Remain

Android OEM customizations like Samsung TouchWiz and HTC Sense are undoubtedly a love-it-or-hate-it affair. There are certainly users out there who care for the added features that these skins introduce. But on the other side of the coin, there are more than a fair share of users who despise the aesthetic nightmares found in some skins. What’s more, this extensive customization often (but not always) results in Android firmware update delays—and that’s if the bloated firmware doesn’t prevent updates in the first place. Oh, and let’s not forget about how these customizations result in a greater number of security vulnerabilities.

Android’s Early Beginnings

OEM customizations certainly had their place in the early beginnings of Android, when its stock UI was clunky and supremely unpolished, and when these custom interfaces added legitimately useful features. However, Android has evolved quite a bit, and ever since Ice Cream Sandwich (or arguably even Honeycomb), has also offered a fantastic and intuitive UI that certainly had its own flair. But as we all know, this flair was for all intents and purposes lost in the excessive OEM and carrier customizations. After all, does a Samsung Galaxy S 5 phone look and feel more similar to another phone running KitKat like the HTC One M8, or does its UI remind you more of an ancient TouchWiz-laden device like the original Galaxy S?

Increased Platform Unity

As we noted in our I/O 2014 coverage, Google has been trying to bring some unity into Android ever since Sundar Pichai took over the platform. And now with Android Wear, Android TV, and Android Auto, they’re taking the first big step by requiring manufacturers to deliver a relatively untarnished user experience.

In an interview with Ars Technica, Google engineering director David Burke confirmed that all of Android’s new initiatives will feature user interfaces and underlying software that is controlled by Google, and not by the OEMs. This is because on these products, “the UI is more part of the product in this case.” And as one would expect given Pichai’s new role, the end goal is to make Android updates “more like Chrome on the desktop.” There will be a few differences in OEM implementations with regards to built-in features and pre-installed apps, as described by Google, but for the most part, these implementations will be nearly identical to the end user, and reinforce Android’s new image.

Questions Remain

There are now undoubtedly several questions from both a developer and end user perspective. First off, how exactly does Google plan on enforcing this? Would this be accomplished by limiting Google Play access to certified implementations? This is already done in limited capacity with new Android devices to ensure that they pass the Android Compatibility Test Suite. But still, what’s to prevent an OEM from building an Android Wear device, which doesn’t require direct access to the Play Store in the first place, and making it hook into the appropriate APIs? This then brings us back to a question we posed several months back when Android Wear was first unveiled: Just how open will Android Wear actually be?

The unfortunate truth is that we don’t know yet if Android Wear itself (or how much of it) will be open source, or how this unified UI will be enforced. Perhaps only the shared AOSP codebase will be open, with the rest being proprietary and used as a means of enforcing platform unity. This is both a good and bad thing–for both developers and end users. However, it’s easy to imagine how this move, alongside the emergence of all of the recent closed-source Google apps, can hurt Android’s openness.

What are your thoughts on all of this? Are you a fan of Google trying to preserve Android’s identity at seemingly all costs, or would you rather have a more open ecosystem, where developers and manufacturers are free to use (and abuse) Android’s openness to differentiate their products? Be sure to sound off in the comments below!

[Source: GoogleArs]


_________
Want something on the XDA Portal? Send us a tip!

Will Verduzco

willverduzco is an editor on XDA-Developers, the largest community for Android users. Will Verduzco is the Portal Administrator for the XDA-Developers Portal. He has been addicted to mobile technology since the HTC Wizard. But starting with the Nexus One, his gadget love affair shifted to Google's little green robot. He is also a Johns Hopkins University graduate in neuroscience and is now currently studying to become a physician. View willverduzco's posts and articles here.
Jimmy McGee · Mar 31, 2015 at 07:00 am · 2 comments

Fix Lollipop Memory Leak – XDA Xposed Tuesday

Unfortunately there was a memory leak in Android 5.0.x Lollipop. Thankfully it was fixed in Android 5.1. However, at the time of this video Xposed Framework doesn’t have Android 5.1 support. So you are faced with a choice of fixing the memory leak or running your Xposed Modules. Or are you? In this episode of XDA Xposed Tuesday, XDA TV Producer TK reviews an Xposed Module that adds the Android 5.1 memory fix to pre 5.1 Lollipop devices. The module...

XDA NEWS
Mario Tomás Serrafero · Mar 30, 2015 at 11:00 pm · 2 comments

Would The LG G4 Fare Well With The Snapdragon 808?

The LG G4 has a lot to prove, given that last year’s LG G3 was among the best smartphones of 2014. The Global Mobile Awards given out during the time of MWC 2015 named it the Smartphone of The Year (SOTY?) alongside the iPhone 6, and at the time of its release it packed the very best in Android specifications, from the powerful Snapdragon 801 to the class-leading 1440p display. The camera, battery life and feature set were also deemed...

XDA NEWS
GermainZ · Mar 30, 2015 at 02:41 pm · 3 comments

DexPatcher: Patch Android APKs Using Java

You've probably seen or installed modified applications, be it a patched dialer for your resolution or a custom WhatsApp version with added features. How do developers do that, though? A lot of the time, the applications' source code isn't even available, so how does it all work? We'll see that first, then take a look at a new tool that aims to make the process much easier, and finally compare it to the popular Xposed framework to see how they...

XDA NEWS
Share This