Want to become an outstanding development engineer of Android, do not understand the Android design rules how can, Android4.0 after the advent of Google for Android programmers to standardize a series of design principles, do not blindly imitate the design of iOS, because Android Is Android, not the same fireworks.
Most developers want to publish their applications on multiple platforms. But keep in mind that different platforms adhere to different rules and conventions. Jobs has only one, and Android isn't the one. The perfect design decision will enable users to feel the extraordinary sensory sensations on the Android platform, differentiating them from other platforms. The "design once, take it all" approach may save you time, but it is likely to produce an inconsistent application experience that makes our programs incompatible with other Android apps, leaving the user experience alienated. Ask each programmer to consider the following guidelines to avoid the most common pitfalls and errors.
(1) Do not emulate UI elements from other platforms
Each platform offers a set of well-designed UI elements, a unique fashion theme. For example, the main fillet button of the iOS platform, and some use gradients in the title bar. In some cases, elements may have the same purpose, but the design work is completely different. When we build Android apps, don't carry theme UI elements from other platforms, don't imitate their specific behavior. Review the building blocks guide to learn more about the most important UI elements of Android and the default themes for the system, and to check how the Android platform application gets the context elements of the app. If we want to customize the theme of UI elements, customize it carefully according to your specific brand--not according to the conventions of different platforms.
Don't just imitate the rounded corners of iOS in a flat design, because Android is not Steve Jobs!!
(2) Do not bring the icons of other platforms
The Android platform has provided developers with an icon set of commonly used functions, such as sharing, creating or deleting icons. When we migrate our app to Android, please match the design of its icon with the official icon! We can find various icons for the application download page. Http://developer.android.com/design/downloads/index.html
(3) Do not use the bottom tab
The bottom tab is used very frequently in iOS programs, but I see a point in the Android design specification that our program should not use the bottom tab, and I don't quite understand why! But since this is written, we must respect its design concept, after all, each platform has its own design concept.
The android tab view control should be displayed at the top of the screen. In addition, Android apps may use the bottom bar to split actions on the action bar. We should follow this guideline to avoid creating an inconsistent experience with other applications on the platform to avoid confusing operations and view switching.
Today's introduction to write this, I hope you can write to me to criticize and add, then I will continue to update this article, I hope to be able to make progress with friends of Bo!