Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Mobile Design: Adding Mobile to Your Learning Ecosystem

1,593 views

Published on

Presented at DevLearn 2013, 24 October 2013, Las Vegas

Every platform offers unique challenges and opportunities. As mobile becomes the preferred platform, you have to address what makes it work well to assure success, satisfaction, and maybe delight. And it’s a lot more than size and touch. Mobile and desktop are very different in their principles and in the way people use them. Learn about the pitfalls and fallacies of designing for mobile and multi-platform, multi-user experiences.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Mobile Design: Adding Mobile to Your Learning Ecosystem

  1. 1. Mobile Design Adding Mobile to Your Learning Ecosystem @shoobe01 @DevLearn 1
  2. 2. Mobile is not the next big thing. 2
  3. 3. More mobiles that people. 3
  4. 4. 75%. 4
  5. 5. Local… 5
  6. 6. Everyone has access. 6
  7. 7. 5 billion SMS users. 7
  8. 8. Know your audience. 8
  9. 9. Ask yourself: • What is your audience? • What are their goals? • What are they using now to solve this need? 9
  10. 10. Nothing. 10
  11. 11. PHOTO OF GROUND STRAP NOT IN PLACE? 11
  12. 12. Don’t design for yourself. 12
  13. 13. An app is not a mobile strategy. 13
  14. 14. “I'm as interested in "channels" as a thing when designing ecosystems as I am in pages when reading a book.” – Andrea Resmini @resmini 14
  15. 15. “Sadly, no decision about architecture is a decision, one that will determine your success or failure as a company.” – ??? @??? 15
  16. 16. ® Post It notes. 16
  17. 17. Design an ecosystem. 17
  18. 18. Cleaning your room. 18
  19. 19. Look over your shoulder. 19
  20. 20. Heuristic evaluations. 20
  21. 21. Set constraints. 21
  22. 22. Know your audience. 22
  23. 23. Know what the audience uses. 23
  24. 24. Know how your audience works. 24
  25. 25. Don’t forget the browser. 25
  26. 26. Think about the ecosystem. 26
  27. 27. Don’t get lost. 27
  28. 28. Thing 28
  29. 29. Embrace diversity. 29
  30. 30. 30
  31. 31. “…inequality is where the opportunities/challenges for design really are.” – Andrea Resmini @resmini 31
  32. 32. Every platform is a unique and special snowflake. 32
  33. 33. 33
  34. 34. 34
  35. 35. 35
  36. 36. 36
  37. 37. Design for failure. 37
  38. 38. Arbitrary complexity. 38
  39. 39. Systems all the way down. 39
  40. 40. Networks of delay. 40
  41. 41. Systems are fault-intolerant. 41
  42. 42. Users are fault-intolerant. 42
  43. 43. “Error is viewed, therefore, not as an extraneous and misdirected or misdirecting accident, but as an essential part of the process under consideration.” – John VonNeuman 43
  44. 44. Accounting for tolerances. 44
  45. 45. PHOTO. REG CODES ON CEREAL BOXES. 45
  46. 46. Design for imperfection. 46
  47. 47. • Assume the unknown. • Think systematically. • Use and make patterns and guidelines. • Analyze and focus. 47
  48. 48. Assume the unknown. 48
  49. 49. Think systematically. 49
  50. 50. Use and make patterns and guidelines. 50
  51. 51. Analyze and focus. 51
  52. 52. Design is complex. 52
  53. 53. 53
  54. 54. Agile? Lean? 54
  55. 55. None are right. None are wrong. 55
  56. 56. Wrap your arms around a module. 56
  57. 57. Look over your shoulder. 57
  58. 58. Is it sensible? 58
  59. 59. Is it error-free? 59
  60. 60. Is it ecosystem friendly? 60
  61. 61. Are you lying? 61
  62. 62. Validate your work. 62
  63. 63. Context is more important than working code. 63
  64. 64. Find your audience. 64
  65. 65. One on one. 65
  66. 66. Ask them, don’t tell them. 66
  67. 67. Your memory is terrible. 67
  68. 68. Make good decisions. 68
  69. 69. Don’t trust users. 69
  70. 70. Bringing mobile back home. • • • • • • • Know the market. Know your users. An app is not a strategy. Systems first. Design for failure, and resiliency. Look over your shoulder. Show it to users. 70
  71. 71. Philosophy, Not Process 71
  72. 72. Ask for help. 72
  73. 73. Contact me for consulting, design, to follow up on this deck, or just to talk: Steven Hoober steven@4ourth.com +1 816 210 045 @shoobe01 shoobe01 on: www.4ourth.com 73

×