Android Applications – Design Patterns

By Author: Alan Smith
Total Articles: 1285
Comment this article

Most people including the clients and mobile application developers like to opt for short cuts because this saves time and money. Every time the shortcuts are not going to live up to your expectations because of limitations at are applicable. This principle is applicable when anyone thinks of using iPhone application design to the Android. If you use coding languages like HTML5 and WebKit, a part of the purpose can be served but not totally. When you develop the application design with the help of HTML5 and WebKit for iPhone, that application design cannot be for Android just because of difference in the user interface (UI) conventions.

The ‘Back’ key is the major difference between the UI conventions of the two. If you want to navigate or go back to the previous pages the ‘Back’ key is very useful. In the Android devices the ‘Back’ key is at the disposal of the user so that user can use whenever he/she wants. This facility does not depend on the application. In the Android 3.0 and later versions the ‘Back’ key is either found fixed digitally to the screen bottom or a physical part of the smart phone device. ...
... When the ‘Back’ key is outside the application, the screen top is left with space for other elements to be accommodated. This space can be constructively for title, menu or logo.

Some other major design patterns introduced in Android 2.0 and later versions are as follows:

• Action Bar:
The Action makes a big difference between the design pattern of the Android and that of other smart phones. The Action Bar is very similar to the banner that is seen in the conventional websites. The left side has the title and or the logo while the right side has the navigational items. Flexibility is another feature of this Action Bar. The menus can be made to hover and the search boxes can be expanded. This feature has now become global for Android phones.

• Quick Actions:
When the user wants the actions in addition to those present especially with reference to the context, the Quick Actions design pattern is of much use. An action bar is triggered when the user taps the photo in the application. This can allow the user to share the photo with others.

• Dashboard:
When the user wants to navigate through a number of different layers in an application, the Dashboard comes into use. When you want to use rich applications like LinkedIn and Facebook, the Dashboard facilitates the user with a launching pad.

• Search Bar:
If you want to conduct a search on the basis of category, the Search Bar makes the search very simple. Suggestions about the search are provided through this design pattern.

• Companion Widget:
If the notifications are to be displayed on the screen of the user by the application then the Companion Widget is of use. The advantage of Companion Widgets is that it remains on the launch screen while in the iOS it is not so.

Copyright © 2011

Spinx Inc. is a Professional Android Application Development company; we are expert in Mobile Applications Development including Android App, iPad App and Blackberry Apps Development services.