Friday, June 5, 2015

The hidden agenda of Android M – Hypertext

As a user, I consider customization layers have been one of the biggest problems experienced by the Android platform. Although it can be argued that some like Sense long were nicer than the design that Google brought to AOSP (blessed Matias Duarte), which also had very interesting unique features such as multi-window (TouchWiz) , the fact is that for users, has been an issue that has brought many more headaches than benefits. In fact, that many users want to experience both the Nexus (also from Motorola) is no coincidence. They are advanced users, yes, but know their benefits.

Android M includes a feature that, in my view, is created to help OEMs, but also to end the visual fragmentation and layers, but nevertheless allowing differentiation

If the new system is adopted well, will not see such drastic changes from AOSP as left

XDA Developers have descuebierto that Android M supports natively RRO , a framework that was created by Sony and then ceded by the company to the Android Open Source Project. Interface allows you to modify applications without having to create new applications, or modify its code. It does not change its operation or its estabiliad, and that’s what we’ve always wanted users on the platform. That is, we understand that in such a saturated market, differentiation is vital to compete against other manufacturers, but this need never have to be tied to a poor performance.

RRO is the most ambitious plan to unify the Android experience while maintaining the different layers of customization

Although it is a function that might Cyanogen be implemented and other ROMs as the current system of themes, it really is designed to change by OEMs managers to customize Android to its terminals. On the one hand I think it is making life easier for development teams deadlines update , and second, to ensure the system performance because, like it or not, that is a point that until now could tarnish the image of Android.

As shown in the above screenshot, Alan Vivarette, Senior Software Engineer at Google, explained that the new implemented so manufacturers can serve to modify aspects such as colors or icons, but does not mention anything about playing the system, because it’s not about that. He adds that the new dark mode Android M also can be used by all apps, as it is offered as part of Material Design.

Obviously, this new Android M or can not be used by manufacturers , but if you really want to provide a quality experience, I think is a great idea to implement the resources that Google is making available and that Nexus experience that can get changed, but not destroyed to all Androids market. Out of this consideration it is, of course, the companies want to add additional functions. That goes for elsewhere and if you need to change the system. But it’s a start.

LikeTweet

No comments:

Post a Comment