Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (6)
En vedette
En vedette (13)
Similaire à Stand Out Apps
Similaire à Stand Out Apps (20)
Dernier
Dernier (20)
Stand Out Apps
- 2. Stand-Out Apps: The User Experience Is Key Jeremy Lyon, Manager, Interaction Design Adil Dhanani, Manager, UI Production April 24, 2010
- 3. What We’ll Cover What is design? 10 minutes What’s special about mobile design? 5 minutes How to employ design techniques 15 minutes Examples 15 minutes Q&A 15 minutes
- 9. Usefulnes s image courtesy SNAKPhotography http://www.flickr.com/photos/snakphotography/
- 10. Usability image courtesy Terry Wha http://www.flickr.com/photos/terry_wha/
- 11. image courtesy Sean McGrath http://www.flickr.com/photos/mcgraths/
- 15. image courtesy Rob Shenk http://www.flickr.com/photos/rcsj/
- 16. image courtesy Sean McGrath http://www.flickr.com/photos/mcgraths/
- 19. Tradeoffs image courtesy Henna by Karen Horton http://www.flickr.com/photos/karenhorton/
- 20. What’s Different About Mobile
- 23. image courtesy Paul Lowry http://www.flickr.com/photos/paul_lowry/
- 24. Opportunities
- 28. image courtesy Horia Varlan http://www.flickr.com/photos/horiavarlan/
- 29. image courtesy Norman B. Leventhal Map Center http://www.flickr.com/photos/normanbleventhalmapcenter/
- 30. image courtesy The Shane H http://www.flickr.com/photos/shane-h/
- 31. Balance
- 32. Consisten cy
- 33. Dominanc e
- 34. Unity
- 35. image courtesy D’Arcy Norman http://www.flickr.com/photos/dnorman/
- 36. Evaluate
- 37. Test
- 38. Iterate
- 40. Examples
- 41. Resources
- 42. Books About Design • The Design of Everyday Things and Emotional Design by Donald A. Norman • Don’t Make Me Think by Steve Krug • The Inmates are Running The Asylum by Alan Cooper • Shaping Things and Tomorrow Now by Bruce Sterling
- 43. webOS Design Resources • Palm Human Interface Guidelines • Top Tips For Developing Great webOS Application Interfaces • Style Matters • All are available at developer.palm.com. Search for User Interface Guidelines
- 44. Q &A
Notes de l'éditeur
- •Who we are Jeremy -- Run interaction design at Palm -- Have been in this role since before webOS got its start Adil -- Manage production team at Palm -- Also been in this role from the beginning of webOS -- Background in Computer Engineering -- Started as an EPM, switched to design team as a UI developer
- • What do you think?
- • Some people think it’s about making things look better
- • Some think it’s about putting people through a battery of tests in a laboratory
- • Some think it’s about drawing a bunch of flowcharts • It’s all those things, and it’s about cultivating a state of mind • If you want to write applications that users are delighted by, you need to think like a designer
- • Does your application do something people want to do, in a way that’s better than they can do otherwise? • This is table stakes • But from a designer’s perspective, this is about satisfying a user need • We looked at how people pursue their activities and realized that true multi-tasking, that is managing multiple tasks with permanence and in a physical natural way, didn’t exist in the mobile space
- • Usability’s a big topic. I’ll call out a few components. • But there’s a framework to think about usability.
- • Usability is a cognitive throughput problem • Like traffic on a freeway -- the more elements on a screen your brain has to process, the less it can • Key is to make the right trade offs between the functions you put in your application, and how you portray them. Here are some things to think about.
- • Discoverability • How easy is it for people to pick up your application and know how to use it?
- • Command buttons are easily discoverable • Back is easily discoverable on the iPhone, but it also makes for a more complex screen, and it adds that complexity to every single screen of an application that’s more than one level deep. • Back gesture is not easily discoverable on the Pre, but it’s very learnable.
- • Learnability • How well does your design help users remember what to do? • Once you discover it, back gesture is easy to remember. It goes from right to left, which is associated with “back” in left to right reading languages. It’s physical, so portions of your brain that don’t require conscious thought are engaged. (When you walk, you don’t think about pick up foot, move it forward, put it down).
- • Predictability • Will users get the same results when they perform the same actions? • Example: option lists. Every time you see a downward facing arrow, you can predict that there are a set of options that will appear on top of the screen and let you pick one • In general, you can count on the framework to provide predictability (and aid in discoverability)
- • Simplicity • The less you have to think about, the easier it is to understand • Example: apply the 80/20 rule
- • All adds up to reducing friction
- • So, create a useful application that’s simple • A discoverable application that doesn’t put much on the screen • These ideas are often at odds with each other • Key is to make tradeoffs between one and the other • We’ll come back to this when we talk about techniques
- • Mobile design is design, only more so. • Constraints are greater. • Trade offs are more important • Several characteristics unique to mobile design
- • Smaller screen • There’s an upper limit on screen size before a device is no longer mobile • Smaller screens = less room = more complexity if you’re not careful • But also helps us to focus on what’s really important. 80/20 rule
- • Smaller and less convenient input methods • Less opportunity to solicit user feedback
- • More casual interaction, shorter bursts •People plan to sit down at their computers •People have their mobile device all the time, so they use it at odd moments •More interruptions
- • Mobile design also offers opportunities over fixed devices • Always with you -- so you can build apps that enable frequent, rapid interactions • Contains your life, so operating systems that let you access that data open up all kinds of smart behaviors
- •By no means is this comprehensive •At the end I'll present a list of resources I've found useful for more detail •Going to go in roughly chronological order, though much of this is back and forth
- • Generate an idea • Be self-reflective about what you do • What do you wish you could do that you can't? •When do you find yourself cursing at a computer, and what about? •When do you find yourself asking, "wouldn't it be cool if?" •In other words, what itch do you want to invent a tool to scratch? • What about the people around you? Who would you like to help with a tool? • Write down your idea. • What problem are you trying to solve? • Who will use your application? • How will they measure success?
- • Apply the reality filter •Its the intersection of reality and fantasy that's the fertile ground for software •Given what you know about software and hardware, what is possible?
- • Research • What research won't do •Won't give you an idea •Won't tell you if your idea is a good one • What research will do •Set the context for your design •It’s like backstory for a writer •Help you discover the details that make a difference •Help you generate new ideas • Techniques •Talk to people •Place people in scenarios similar to what you're thinking about, and observe them •Show people your ideas, and ask them how they'd use it
- • Map It • Draw a map of your application •What are the primary scenes users will interact with? •What do I mean by scene? Think of it as a scene in a play -- where the action takes place. A screen is a scene, so is a dashboard. •What can they do in them? •How will the scenes connect to each other? •Here's where a flow chart is helpful
- • Sketch It • Start sketching the primary scenes • We’ll cover some primary visual design principles
- • Less friction to balanced elements
- • Repetitions of basic forms helps predictability
- • Important objects should stand out
- • Group related concepts •Enclosure •Placement •Color •Weight •Spacing
- •Think about motion •Motion should reinforce the flow of your design • What happens when a user changes state? •webOS has built in transitions. Go in a level, we zoom in. Go out a level, we zoom out. •they’re only about 1/3 of a second each, but they really help users understand where they are in the hierarchy • But be appropriate. Too much eye candy in transitions can be distracting and reduce usability.
- • Stand back and give it a dispassionate evaluation •Look at what you wrote down about your application. •Does it meet the needs you identified? •Does it satisfy your goals? • If not, why not? •Analyze what seems to work and what doesn't
- • Cut out your sketches into the component screens •Or do it in Photoshop and use Ares to put it together • Find people to try it out on •Set the context -- what are they trying to do •Show them your sketches, ask what they would do? •Have them talk about what they're thinking •Don't help them when they get stuck •Write down your impressions immediately afterwards • Take your learnings and apply them back to the design
- • Rinse and repeat until you’re satisfied
- •Know when to stop • It's all about tradeoffs •Use your goals, audience and differentiation to decide what to trade off •Understand costs of discoverability versus usability, etc.
- These resources are focused on the things that I found useful -- there’s a million more out there, just google it.