Google android human interface guidelines

Google-android-human-interface-guidelines-featured.jpg

They previously gave for you the fundamental links you’ll find on the internet about them. I’d then add personal advices If only I add before creating my first android application :

Purchase a real phone As soon as possible. You will find lots of stuff you cannot determine if you take your application only around the emulator.

Don’t consider delivering your application without getting utilizing it not less than 2 week yourself on the telephone. The recommendation of eating your personal pet food is much more true here because we haven’t enough knowledge about such products to depend on intuition. Pc experience doesn’t suit.

Design for large fingers. You do not have a stylus, and individuals have completely different size fingers. Design for that greatest so that they will not get mad, while regular individuals will just feel much more comfortable.

Design for vertical and horizontal screen. Around the HTC dream, the laptop keyboard pressure you to definitely alter the layout very frequently.

Avoid creating 1000 activities. It appears a programming rule but it is not. Whenever you open a task, it’s another application open on top on others. Consequently, closing the application 1 by 1 can eventually piss from the user, or at best confuse him. Espacially if you will find complex restore states.

Design for interruption. It is a phone : it will get off and on, calls earnings, music is performed, etc. Your application is going to be open and shut a thousand occasions so cut loading, save the best states and be sure congruency.

It is a little screen, avoid putting to many details onto it. Meaning only exactly what the user may use ninety percent of times. The relaxation from the data or actions should be contextual : lengthy clic, menu, gestures, timers, etc. Yes, your user won’t find all of the feature immidiatly. He’ll most likely even uncover a number of them monthes after making use of your application the very first time. However it labored for Apple :-)

Scrolling is boring : come up with your computer data fit on screen. If you cannot, use another home windows or tab to show information. Scrolling is perfect for data that’s lengthy to see and mayInchcapital t be damaged in a number of pieces.

Don’t overload your menu. The contextual menu can be used very frequently, it needs to be utilized very rapidly. For those who have a lot of things, create one entry for any submenu named “more” like Google does.

You will find some expected actions you need to follow since the relaxation from the phone works by doing this :

Striking the rear button don’t cancel the present action but save and quit. It isn’t that which you expect if you’ve been focusing on other platforms, but that is how contact, configurations or SMS work. So that’s how you want to do it.

Because of this cancel must discover the typical way : an entry within the contextual menu.

A clic works the experience. No confirmation, no “save”. You clic on the setting, the setting changes. You choose a filter inside a drop lower list, it filters. This is the user expectation.

Whenever you open an application, it returns towards the last condition it’s been : last selected item, last opened up home windows, etc. Make use of the onResume / onCreate / onPause techniques to make sure consistency.

Writting inside a text box begins the written text by having an uppercase letter. This isn’t automatic using the textbox widget, you’ve clearly request for this with “capitalize” within the XML layout file. But thats what happen everywhere on the telephone…

Tell the consumer when you’re consuming his data plan. This really is so apparent, but I’ve come across application so confusing about this you don’t dare runnning it.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>