In this chapter we will look at the different UI Patterns which are available by android to design apps that behave in a consistent and foreseeable way.
A good android application should follow following UI patterns −
Now we will discuss the above mentioned UI Patterns in detail.
The action bar is a dedicated bar at the top of each screen that is generally persistent throughout the app. It provides you several key function which are as following −
Action Bar has four major components which can be seen in the following image.
These components name and functionality is discussed below −
|Sr.No||Action Bar Components|
The app icon establishes your app's identity. It can be replaced with a different logo or branding if you wish.
If your app displays data in different views, this segment of the action bar allows users to switch views.
Show the most important actions of your app in the actions section.
Move less often used actions to the action overflow.
When a user invokes a action on your app's UI, it is a good practice to confirm or acknowledge that action through a toast or a dialog box.
There is a difference between Confirming and Acknowledging.
When we ask the user to verify that they truly want to proceed with a action that they just invoked, it is called confirming. As you can see in the following image −
When we display a toast to let the user know that the action they just invoked has been completed, this is called acknowledging, As you can see in the following image −
The place in your app where users can indicate their preferences for how your app should behave is called as Settings. The use of settings can benefit your app's users in the following ways −
Settings help user to predetermine that what will happen in certain situations
Use of settings in your app help users to feel in control
It is preferred by the android developers to always make "settings" option part of action overflow which is mentioned above. As users did not frequently use this option so the common practice is to place it below all other items except "Help". As you can see in the following picture −
Some of your app users may run into some difficulty while using your app and they will be looking for some answers, and they want them within the app. So always make "help" part of your app.
Like "Settings" the standard design of placing "Help" option is in action overflow. Always make it very last item in the menu and always label it "Help". Even if your app screen has no other action overflow items, "Help" should appear there. As you can see this in the following picture −
Android 3.0 version changed the long press gesture to the global gesture to select data. The long press gesture is now used to select data, combining contextual actions and selection management functions for selected data into a new element called the contextual action bar (CAB).
The selection CAB is a temporary action bar that overlays your app's current action bar while data is selected. It appears after the user long presses on a selectable data item. As you can see in the following picture −
From the CAB bar user can perform following actions −