Almost two years ago Google published the famous Android design guide so that developers implement correctly the interface Holo in their applications, and thus rather improve the user experience, but these recommendations were not trying the animations and transitions, something that looks set to change.
In a report called “How Google Taught Itself Good Design” published a couple of days in Fast Company talk about how Android and Google products have improved its interface in recent years thanks to its designers as Matias Duarte (Android), Jon Wiley (Google Search), Jason Cornwell (Gmail), Jonah Jones (Google Maps), or Isabelle Olsson (Google Glass), making a review of this change and collecting several statements from the Google team.
This article includes some statements by Sundar Pichai, the current head of development of Android and Chrome OS, in which he talks about the future of the interface both Android and Chrome OS, in its aim for third-party applications have a consistent design.
The long-term goal of Google to improve Android and Chrome runs on the same line. After improving its own applications, Pichai said they will now focus on platforms that he calls “opinions of design” so that third-party applications achieve consistency in your design via Android and Chrome. “When you click on something in an application and screen transitions,” Pichai asks, “is there a coherent way so they happen? There is the right amount of “Physics” in an animation so that it makes sense for users on an intuitive level? If the platform provides this transition and becomes natural for applications that adopt it, all Android applications will be more rewarding. In this way we can achieve the beauty, and users will not even notice that it’s happening.” In all these efforts, the aesthetic goal of Google is clear: go away. The most beautiful experience of Google is that it never shows.
As we see in the Google statements you want to all Android applications to use the same type of animations and transitions to create a more rewarding user experience, Since having all applications the same transitions will pass unnoticed for the user to do what the user expected to see. If an application makes a new or strange transition as it is striking and breaking the hegemony with other applications.
Apparently the idea of Google will be using your design and your video tutorials DevBytes Guide to tell developers how to implement correctly the animations and transitions, so applications do not have their own transitions and animations between the different components and views.
By default Android 1.0 SDK applications implement transitions the system defaults, but the API allows developers to customize these animations but now it seems that Google wants to normalize esto with examples and recommendations so that all applications, as well as having interface Holo, also have the same animations and transitions.