Building Great User Experiences

Presented at Jiveworld12 at The Cosmopolitan in Las Vegas, NV.

Transcript

1. Chris Rivard, Senior Product Designer Building Great User Experiences
2. Style
3. Your App Jive Apps: 5.0 to 6.0 User Experience
4. Fundamentals of a great UX?
5. anti-patterns dark patterns “user hostile”
8. Dark Patterns Road Block Sneak into Basket *Roach Motel*
10. So what does good design look like?
11. - View my streams - Quantitative indication of activity - Icon to edit/configure a stream - Control and label to add a new stream - Number of Inbox items - Percentage of on-boarding tasks completed - Call to action to invite your colleagues
14. Affordance An affordance is a quality of an object, or an environment, which allows an individual to perform an action. For example, a knob affords twisting, and perhaps pushing, while a cord affords pulling. http://en.wikipedia.org/wiki/Affordance
15. Mental Model A mental model is an explanation of someone's thought process about how something works in the real world... Mental models can help shape behavior and set an approach to solving problems (akin to a personal algorithm) and doing tasks. http://en.wikipedia.org/wiki/Mental_model
16. “Knowing how people will use something is essential.”
18. Let’s talk about Apps.
19. Jive 5 (Steelhead) Apps gateway Apps Market Dev Center Dev Community Core API Jive 6 (Bridgeport) Jive for Teams (cloud) 2010 App Dashboards (home) App Canvas Billing Infrastructure 2012 App chrome App settings Jive Connects App Actions !app experiences Apps in the stream App Quick Launcher Embedded experiences Jive API v3 (REST & JS) Platform
22. Jive Apps 2010: Designing on principle
23. Simple, powerful business apps.
27. Lessons learned :-\ (this isn’t going to be easy) •Apps are constrained to the dashboard. •The “home” view is a design challenge. •Navigating to a dashboard introduces significant friction.
28. Jive Apps 2012: Recalibrating principles (OODA)
29. 1. Bring apps to the user.
31. Apps Quick Launcher
36. 2. Make it easy to invoke and dismiss apps.
37. !App Experiences
38. What is the most important activity in Jive? hint: you need a keyboard.
39. Can we call apps from the RTE?
43. !
44. Multiple actions !app to call menu.
45. 3. Surface activity from apps in the stream.
48. 6.0 Lessons learned :-) Apps need to be first-class citizens in Jive Speed is a feature (invoking and dismissing apps) App activity needs to be in the stream
49. Great User Experiences begin with users. “Knowing how people will use something is essential.” -Donald Norman
50. Good design is simple is timeless solves the right problem is suggestive is often slightly funny is hard looks easy http://www.paulgraham.com/taste.html uses symmetry resembles nature is redesign can copy is often strange happens in chunks is often daring Principles of good design.
51. Process for designing your app (or any software product)
52. 1. What business problem are you trying to solve?
53. 2. Go talk to your users. 2. Talk to your audience (your users)
54. 3. Simplest set of features to solve the problem.
55. 4. Document the information flow (whiteboard, paper)
56. 5. Design the app on paper.
57. 6. Aesthetics (looks good, works well)
58. 7. Prototype & test
59. 8. Deploy & measure
60. 9. Iterate (OODA)
61. 10. Have fun!
62. 6.0 App Views
63. Canvas view Immersive app experience CRUD / management operations of the app Richer interaction (as a result of screen real estate)
64. !app (embedded experience) Multiple actions per app Single action per menu item Consider what artifact will be embedded into context
65. App actions Multiple actions per app Use when you want to operate on an entire artifact Huge potential for custom workflows
66. Looking ahead: 7.0 and beyond ! Deeper integrations Easier to use API We’re moving fast
67. Next steps: - Join the developer community - Explore the documentation - Join the conversation ! Templates available in the Jive Developer Community: http://developers.jivesoftware.com
68. Thank you for your time! Questions?