Android UX 
 Anti-Patterns Filipe Mendes - ForkIT 1 

Introduction • Majority of programmers have poor graphic and UI skills; 2 

Introduction • Majority of programmers have poor graphic and UI skills; • Very few understand why UX is so important. 3 

Bachelor’s final project design 

Introduction • Majority of programmers have poor graphic and UI skills; • Very few understand why UX is so important. • Sign Up/Sign in - Welcome Experience Keep in mind the following examples may not be accurate today ! 5 

Introduction • Majority of programmers have poor graphic and UI skills; • Very few understand why UX is so important. • Sign Up/Sign in - Welcome Experience • Crippled Refinement - Sorting & Filtering Keep in mind the following examples may not be accurate today ! 6 

Introduction • Majority of programmers have poor graphic and UI skills; • Very few understand why UX is so important. • Sign Up/Sign in - Welcome Experience • Crippled Refinement - Sorting & Filtering • Useless Controls - Avoid missing & undesirable results Keep in mind the following examples may not be accurate today ! 7 

Sign Up/Sign In Problem: Long sign up forms are against any mobile e x p e r i e n c e . A c c e s s t o information in simple and fast way. Example: SitOrSquat 

Sign Up/Sign In Problem: Long sign up forms are against any mobile e x p e r i e n c e . A c c e s s t o information in simple and fast way. Example: SitOrSquat Solution: Only request what is strictly necessary when strictly necessary to proceed. 

Crippled Refinement Problem: Loss of applied filters when we want to refine the current search. Example: Amazon 

Crippled Refinement Problem: Loss of applied filters when we want to refine the current search. Example: Amazon Solution: Keep the applied search in a separate activity or dedicated fragment. Related patterns: Refinement page, Filter Strip 

Useless Controls Problem: Applying filters to 0 results. Example: TripAdvisor 

Useless Controls Problem: Applying filters to 0 results. Example: TripAdvisor Solution: Removal. Related patterns: Did you mean? 

Good practices • Simulate the app navigation with a small notepad; 14 

Good practices • Simulate the app navigation with a small notepad; • The less actions, the better; 15 

Good practices • Simulate the app navigation with a small notepad; • The less actions, the better; • Avoid using too many dialogs; 16 

Good practices • Simulate the app navigation with a small notepad; • The less actions, the better; • Avoid using too many dialogs; • Keep a stack of activities; 17 

Good practices • Simulate the app navigation with a small notepad; • The less actions, the better; • Avoid using too many dialogs; • Keep a stack of activities; • Don’t underestimate a user’s confusion; 18 

Good practices • Simulate the app navigation with a small notepad; • The less actions, the better; • Avoid using too many dialogs; • Keep a stack of activities; • Don’t underestimate a user’s confusion; • Always design specifically to each platform (“pure android”) 19 

Conclusion • Always request what necessary when strictly necessary to proceed; 20 

Conclusion • Always request what necessary when strictly necessary to proceed; • Keep the active filters in each consecutive search; 21 

Conclusion • Always request what necessary when strictly necessary to proceed; • Keep the active filters in each consecutive search; • Stop showing unnecessary controls. 22 

Biography • http://gennovacap.blogspot.pt/2013/02/quality-ui-design-in- mobile-devices-why.html, on 6/05/2013 • http://developer.android.com/design/index.html, on 6/05/2013 • Greg Nudelman, Android Design Patterns, Willey, 2013 23