ux concerns across mobile platforms

© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.

UX Concerns across Mobile Platforms Joseph Labrecque

FITC Unconference @


FITC @ Introduction

2

Joseph Labrecque, MA University of Denver - CTL Senior Interactive Software Engineer Adjunct Faculty

Fractured Vision Media, LLC Proprietor

Adobe Community Professional

Adobe Education Leader

What’s New in Flash Player 11

What’s New in Adobe AIR 3


FITC @ What We’ll Talk About

Desktop User Expectations

Desktop Experiences

How Mobile UX is Different

Concerns Across Platforms

Apple iOS!

Google Android!

Blackberry Tablet OS!

Why Adhere to Existing Paradigms?

When to Deviate from Existing Paradigms?

3


FITC @ Who This Talk is For

Q: Are you a seasoned mobile designer or developer?

A: Yeah? You should probably just leave now… unless you just want to hear me blabber.

Q: Interested in my perspective on mobile UX across platforms?

A: Mmm… perfect.

Q: Are you simply mobile-curious?

A: Yes? Cool- stick around.

4

?


FITC @ Desktop User Expectations

My normal setup: dual 1680 x 1050 displays

Lots of applications opened simultaneously

Uber-Multitasking!

5


FITC @ Windows vs. Mac vs. Linux

Example: Adobe AIR

AIR allows developers to build desktop applications which can run on Windows, OSX, and Linux.

This fact caused a stir among platform-specific UI purists as application interface controls could take on a variety of forms due to the open nature of Flash UI design.

Any experience, if done well, does not necessarily need to conform strictly to any specific guidelines.

6


FITC @ Mobile UX is Different

Users generally have very small screens and therefore not a lot of room to work with.

Applications take up the entire screen.

The user’s full attention is directed toward the running application.

You are guaranteed a captive audience, barring any disturbances.

7


FITC @ Screen Paradigm

The fact that an application will fill the entire screen during the entire duration of an interaction is the single most important consideration for mobile UX.

Depending upon the platform, this may mean that while an application is active, additional applications have been dismissed to the background or closed entirely.

The user is always focused upon one screen at a time, and methods for navigating these screens are often dependent upon whichever operating system is in play.

8


FITC @ Platform-Specific Hardware

Dedicated Buttons

iOS: one button.

Android: four buttons along the bottom or side, which include a home key, dedicated back button, dedicated options menu button, and search.

Tablet OS: a unique bezel through which a variety of gestures can be used, moving beyond simple button presses.

9


FITC @ Touch and Gestures

Touch interfaces completely derail the concept of a single, clicking arrow, substituting fingertips, gestures, and sensors for the simple mouse pointer.

This fact alone reshapes the entire interactive landscape when considering UX with these devices.

Touch and gestures are ancient and powerful! Nothing new at all- the mouse has been an imperfect deviation.

10


FITC @ Cross-Platform Concerns

Menu Systems

Android: a dedicated menu button built into the device that can be programmed to reveal application options, normally via a menu at the bottom of the screen.

iOS: a button within the application that allows the user to access application-specific menus.

Tablet OS: a swipe from the top bezel will pull down or dismiss a set of menu options defined for any given application.

11


FITC @ Existing Paradigms

When users have become familiar with a specific platform, they will expect certain behaviors when interacting with that device.

Deviating from an established expectation can cause confusion for the user and lead to a frustrating experience, or even to total abandonment of the application.

12

[image courtesy of GestureWorks]


FITC @ The Urge to Deviate

Adhering to known user conventions is the safest way to approach UX, but it may not always be the best.

At times, it may be worth the risk of deviating from the norm, either due to the uniqueness of some application process, or because it better establishes a connection with your user in a tighter way than the standard paradigm allows.

Example: http://www.swype.com

13

http://www.swype.com/


FITC @ Last Thoughts

Learn what makes the device platform different from others and to take advantage of that.

Only deviate from established norms when it benefits the user in some way by making interactions better than they would be otherwise.

Skinning your controls for each device, while not always necessary, will add a touch of polish and may go that extra little bit to win a user’s appreciation.

14

[image courtesy of GestureWorks]


FITC @ Questions?

Ask ‘em.

15

?


FITC @ Get in Touch!

16

Joseph Labrecque, MA University of Denver - CTL Senior Interactive Software Engineer Adjunct Faculty

Fractured Vision Media, LLC Proprietor

EMAIL [email protected]

WEB http://josephlabrecque.com/

TWITTER @JosephLabrecque What’s New in Flash Player 11

What’s New in Adobe AIR 3

ux concerns across mobile platforms

Technology