Android UI Anti-Patterns

The great majority of students and programmers that I happen to know and who have an ambition to develop High Level Applications (Mobile, Desktop) don’t have the necessary skills in designing and User Experience, and, sadly, I am one of them.

The above can be justified by the fact that this area does not figure in the curricula of computer studies.
Nevertheless, it is important, essential or even determinant, if we do not want to frustrate the users to the point of uninstalling the application (if they even attempt to install such unattractive app in the first place).

With this in mind, I want to write 3 simples tips on Android Anti-Patterns,together with their respective recommendations:

SignUp / SignIn:
Problem: Multiple register forms, log in’s, age verifications, terms and conditions, etc. detract from the key mobile use case: quick,simple information access on the go.
Solution: The app should request (email,mobile number,etc.) only when it is strictly necessary to proceed.
Example: SitOrSquat

Useless Controls:
Problem: Letting the user filter zero-results from a previous search.
Solution: Remove the filters
Example: TripAdvisor

Crippled Refinement:
Problem: Loss of the previously added filters for subsequent
searches while adding parameters to the search box.
Solution:Keep the search history in a separate and specially dedicated fragment/activity.
Example: Amazon

SitOrSquat  -  TripAdvisor  -  Amazon
SitOrSquat – TripAdvisor – Amazon

NOTE: These examples were taken from the book Android Design Patterns, Willey, 2013 from Greg Nudelman and are merely illustrative. It’s important to mention that TripAdvisor and Amazon Anti-Patterns were corrected at the time of writing.

[twitter-follow screen_name=’fmendes6′]

As an Android Developer, I believe that every application should be as simple and as easy to use as possible. Currently a GDG Lisbon organizer.

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