+ Follow

Design for Every Screen

by shoobe01

1,735 views

Even for the simplest, most-focused product, your users will engage in multiple ways, and in multiple channels. Learn about a user centric approach to developing a target experience to guide better, more efficient design, planning and implementation of your product.

Steven Hoober has been practicing UX and IxD for 15 years, and has been designing mobile products since 1999. His mobile work has included design of browsers, e-readers, search, NFC, mobile banking, data communications, location, and OS overlays. Steven spent eight years at U.S. mobile operator Sprint, and has also worked with AT&T, Qualcomm, Samsung, Skyfire, Bitstream, VivoTech, The Weather Channel, Lowe's, and Hallmark Cards. He has a just-released book of patterns, Designing Mobile Interfaces from O'Reilly.

Accessibility

View text version

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

File a copyright complaint

3 Embeds 23

http://paper.li	19
http://a0.twimg.com	3
http://www.linkedin.com	1

Statistics

Likes: 5
Downloads: 64
Comments: 2
Embed Views: 23
Views on SlideShare: 1,712
Total Views: 1,735

Design for Every Screen Presentation Transcript

Design forEvery ScreenDesigning Mobile Interfaces:Patterns for Interaction Design 1

What is Mobile? 2

Design for Clients“What we need is… “• Trends• Fashion• Competition• Please the boss 3

Design for What You Know 4

You Are the Mobile Team 5

Design for Every Screen 6

Design for Everything• Desktop consumer web • SMS• Mobile web • MMS• Mobile app • IVR• Store terminals • TV• Call center terminals • Projection• Call center logging • Touch• Call center scripts • Gesture• Kiosks • Shared interfaces• Printed bills • Pen input• Bill inserts • Biometrics• Envelope printing • Location• Emails • Environments 7

Design for Experiences 8

Design for Connections 9

Design for Connections 10

Design Principles• Gather information• Design for users, tasks, and goals• Do not design for technology, interfaces or platforms• Create a blueprint of the whole service• Design to target experiencesUse that to create IAs (and then interaction flows, wires, etc.) for each channel. 11

Design for UsersUser-Centered Design informs your decisions.Before you can design, you have to define:• Audience• Purpose• Context 12

Design for ServicesService Design principles may inform the process even more.Key elements that have to be defined, using formal processes, are:• Actors• Scenarios• Components 13

How About an Example? 14

Every Platform We Can Think Of 15

One IA for All 16

Blueprint for Systems 17

One IA for eReaders 18

Another IA for Web 19

Blueprint the IxD & Interface 20

Branch for Platforms 21

A Checklist for Design• Blueprint: • Gather – Collect info • Define – Personas, objectives • List – All possible features • Filter – Keep only what you need • Group – Cluster and establish dependencies • Prioritize – Earlier and higher, in system or backlog • Arrange – Notional interfaces• IA, IxD (per channel) • Re-Filter – What cannot, should not be here • Branch – Executable IA • Optimize – Interaction, and interfaces 22

Implement for Every Screen 23

Communicate Objectives 24

Own Your Design 25

Gain Buy-In 26

Steven Hoobersteven@4ourth.com+1 816 210 0455@shoobe01shoobe01 on:www.4ourth.com 27

shoobe01 I think it's actually in the notes. I recall saying that repeatedly when I've presented it. But I almost don't even explicitly design for accessibility, because so many of the core principles of use for every user (or for web, semantic markup) automatically make the products pretty to very good for low-vision users or screen readers. 1 year ago

Are you sure you want to

Technocation, Inc at Technocation, Inc Surprised that this presentation doesn't seem to talk about accessibility issues. You need to design for every screen, including readers for the blind. 1 year ago