Being Responsive

Being Responsive

Talk about how we need to break free of our illusions and rewire our brains in order to build better, more future-friendly products.

Dac45089aeda3bca56193072601a49d4?s=128

Jason Grigsby

March 24, 2016
Tweet

Transcript

  1. Being Responsive Jason Grigsby • @grigs • cloudfour.com

  2. Got email from this guy... http://www.flickr.com/photos/corbett3000/2327165138/in/set-72157604094629546/

  3. Mobile is Disruptive Technology http://www.flickr.com/photos/talkephotography/4523849236/ Creative Commons BY-NC-SA 2.0

  4. 10 20 30 40 50 60 Q1 Q3 Q5 Q7

    Q9 Q11 Q13 Q15 Q17 Q19 Quarters Since Launch Subscribers (MM) iPhone + iTouch NTT docomo i-mode AOL Netscape iPhone + iTouch vs. NTT docomo i-mode vs. AOL vs. Netscape Users First 20 Quarters Since Launch Note: *AOL subscribers data not available before CQ3:94; Netscape users limited to US only. Morgan Stanley Research estimates ~39MM netbooks have shipped in first eight quarters since launch (10/07). Source: Company Reports , Morgan Stanley Research. Mobile Internet Outpaces Desktop Internet Adoption iPhone + iTouch Users = 8x AOL Users 9 Quarters After Launch Desktop Internet AOL* v 2.0 Launched 9/94 Mobile Internet NTT docomo i-mode Launched 6/99 Mobile Internet iPhone + iTouch Launched 6/07 ~57MM ~25MM ~7MM Desktop Internet Netscape* Launched 12/94 ~11MM 26 Source: http://www.morganstanley.com/institutional/techresearch/mobile_internet_report122009.html
  5. http://www.opera.com/smw/ Not just smartphones. Opera Mini growing as well.

  6. 7.1 Billion Mobile phone for nearly everyone on the planet.

    Flickr photo by Pingnews: http://www.flickr.com/photos/pingnews/370061022/
  7. Technology Cycles - Wealth Creation / Destruction New Companies Often

    Win Big in New Cycles While Incumbents Often Falter Mainframe Computing 1960s Personal Computing 1980s Desktop Internet Computing 1990s Mobile Internet Computing 2000s Mini Computing 1970s New Winners New Winners New Winners New Winners Note: Winners from 1950s to 1980s based on Fortune 500 rankings (revenue-based), desktop Internet winners based on wealth created from 1995 to respective peak market capitalizations. Source: FactSet, Fortune, Morgan Stanley Research. Microsoft Cisco Intel Apple Oracle EMC Dell Compaq Google AOL eBay Yahoo! Yahoo! Japan Amazon.com Tencent Alibaba Baidu Rakuten Digital Equipment Data General HP Prime Computervision Wang Labs IBM NCR Control Data Sperry Honeywell Burroughs 16 Source: http://www.morganstanley.com/institutional/techresearch/mobile_internet_report122009.html
  8. Image Source: Computersciencelab.com, Wikipedia, IBM, Apple, Google, NTT docomo, Google,

    Jawbone, Pebble. Technology Cycles Have Tended to Last Ten Years Technology Cycles – Still Early Cycle on Smartphones + Tablets, Now Wearables Coming on Strong, Faster than Typical 10-Year Cycle Mainframe Computing 1960s Personal Computing 1980s Desktop Internet Computing 1990s Mobile Internet Computing 2000s Mini Computing 1970s Wearable / Everywhere Computing 2014+ Others? 49
  9. http://www.flickr.com/photos/76074333@N00/317952268/ | http://futuristmovie.com Creative Commons BY-NC-SA 2.0

  10. None
  11. None
  12. None
  13. None
  14. None
  15. None
  16. ME NEED IPHONE APP. http://www.flickr.com/photos/corbett3000/2327165138/in/set-72157604094629546/

  17. 2008 We must have an iPhone App! http://www.slideshare.net/jamesgpearce/html5-and-the- dawn-of-rich-mobile-web-applications-pt-1

  18. 2009 We must have an Android App! http://www.slideshare.net/jamesgpearce/html5-and-the- dawn-of-rich-mobile-web-applications-pt-1

  19. 2010 We must have an iPad App! http://www.slideshare.net/jamesgpearce/html5-and-the- dawn-of-rich-mobile-web-applications-pt-1

  20. 2011 We must have a... http://www.slideshare.net/jamesgpearce/html5-and-the- dawn-of-rich-mobile-web-applications-pt-1

  21. http://www.slideshare.net/jamesgpearce/html5-and-the-dawn-of-rich-mobile-web-applications-pt-1

  22. http://www.slideshare.net/jamesgpearce/html5-and-the- dawn-of-rich-mobile-web-applications-pt-1

  23. http://www.flickr.com/photos/adactio/6301799843 Zombie apocalypse of devices

  24. http://www.flickr.com/photos/ lukew/10412585943/

  25. Responsive is the answer. http://www.flickr.com/photos/38208449@N00/7712219364

  26. But not the way you’re thinking.

  27. None
  28. None
  29. None
  30. None
  31. There are other paths you can take… http://www.flickr.com/photos/95572727@N00/4204913417

  32. But they will lead you to the same place. http://www.flickr.com/photos/cuppini/2631488256

  33. Responsive design is inevitable. http://www.flickr.com/photos/gwilmore/3848170723/

  34. Content & Services Car sketch: http://www.flickr.com/photos/cloppy/5081768461/ HTML HTML HTML HTML

    HTML HTML HTML HTML NATIVE NATIVE NATIVE
  35. Let’s say you’re going to build a separate site or

    app for specific form factor.
  36. Lines between device classes are blurring Model Type Size Display

    Resolution Viewport W H W H W H Samsung Galaxy Note 2 Phone 3.17” 5.95” 5.5” 720 1280 360 640 Motorola RAZR HD Phone 2.67” 5.19” 4.7” 720 1280 360 519 Motorola Atrix HD Phone 2.75” 5.26” 4.5” 720 1280 540 812 HTC Droid DNA Phone 2.78” 5.5” 5” 1080 1920 360 640 Nexus 7 Tablet 4.72” 7.81” 7” 800 1280 600 793 Kindle Fire Tablet 4.72” 7.44” 7” 600 1024 600 819 Kindle Fire HD Tablet 5.4” 7.6” 7” 800 1280 533 731
  37. 640 px 600 px 519 px 640 px 622 px

    533 px 812 px Which are phones and which are tablets?
  38. http://www.flickr.com/photos/geatchy/8489505999

  39. Technical challenges Being inevitable doesn’t make it easy. http://www.flickr.com/photos/presidioofmonterey/7025086135

  40. PERFORMANCE

  41. http://www.guypo.com/uncategorized/real-world-rwd-performance-take-2/ Most responsive sites are bloated 2013: 476 sites from

    mediaqueri.es tested
  42. http://www.thefoxisblack.com/2012/10/02/the-design-thinking-behind-the-new-disney-com/

  43. None
  44. None
  45. None
  46. http://www.flickr.com/photos/beautyredefined/2643858323/

  47. http://www.flickr.com/photos/puuikibeach/3654517679

  48. Most responsive web designs are…

  49. The resounding answer from the community: Mobile First Responsive Web

    Design
  50. http://www.flickr.com/photos/localcelebrity/4831362933/ Different than Mobile First Design Theory

  51. Mobile First Design Principles Mobile First Responsive Design Forwarded by

    
 Luke Wroblewski Technical Approach for Responsive Design
  52. None
  53. *FIRST Content First Structure First Performance First API First Command

    Line First
  54. COFFEE FIRST! http://www.flickr.com/photos/leah8691/2184863624/

  55. http://www.flickr.com/photos/gumption/3639682201/

  56. But we’ve already got a desktop design and we can’t

    start over.
  57. https://twitter.com/freediverx/status/354698695041744896

  58. How do I make this responsive?

  59. How do I make this responsive?

  60. How do I make this responsive?

  61. http://www.flickr.com/photos/ancphotos_/6728574731

  62. Ok, let’s start from a clean slate http://www.flickr.com/photos/salendron/5569020488/

  63. What would the mobile version look like?

  64. What would the mobile version look like?

  65. How does that map to desktop design?

  66. How does that map to desktop design?

  67. How does that map to desktop design?

  68. How does that map to desktop design?

  69. How does that map to desktop design?

  70. How does that map to desktop design?

  71. How does that map to desktop design?

  72. How does that map to desktop design?

  73. How does that map to desktop design?

  74. How does that map to desktop design?

  75. Can this desktop version be better using what we’ve learned

    from the mobile version?
  76. None
  77. Frequent concern for this project: How something will scale to

    desktop? Actual times this has been a problem when mobile has been solid already: 0
  78. Small screen assets Large screen assets Progressive enhancement based on

    screen size Mobile First Responsive Web Design is a technical approach for responsible responsive designs.
  79. http://www.flickr.com/photos/soldiersmediacenter/6999691421 Yes, there are obstacles…

  80. But the biggest challenge is us. http://www.flickr.com/photos/yamagatacamille/5434502250/

  81. http://www.flickr.com/photos/hellogeri/6154034099/ A few years ago, Jeremy Keith talked about how…

  82. http://www.flickr.com/photos/60415054@N00/14301113/ we told ourselves that the web was…

  83. http://www.flickr.com/photos/60415054@N00/14301113/ 640 px 480 px

  84. 640 px 480 px

  85. 800 px 600 px

  86. 1024 px 768 px

  87. http://www.flickr.com/photos/adactio/6153481666/ Then mobile came and made us realize…

  88. that it was a consensual hallucination all along. http://www.flickr.com/photos/garibaldi/303085857/

  89. The web never had a fixed canvas. http://www.flickr.com/photos/paulocarrillo/124755065/

  90. Even our tools perpetuate the lie.

  91. http://www.flickr.com/photos/69797234@N06/7203485148/ We’re making some progress.

  92. We often dismiss as unlikely the idea that someone will

    want to use our service on a small screen.
  93. It’s fairly certain that the highest-value use will stay predominantly

    on desktop… Most complex tasks have vastly better user experience on the desktop and thus will be performed there. —Jacob Nielsen https://www.nngroup.com/articles/transmedia-design-for-3-screens/
  94. http://www.flickr.com/photos/brunauto/5062644167/

  95. 80% during misc downtime 76% while waiting in lines 86%

    while watching TV 69% for point of sale research http://www.flickr.com/photos/carbonnyc/5140154965
  96. TMI

  97. 39% use phone on toilet

  98. But if there’s one thing I’ve learned in observing people

    on their mobile devices, it’s that they’ll do anything on mobile if they have the need. Write long emails? Check. Manage complex sets of information? Check. And the list goes on. If people want to do it, they’ll do it on mobile -especially when it’s their only or most convenient option. —Luke Wroblewski lukew.com/ff/entry.asp?1333
  99. http://mobithinking.com/mobile-marketing-tools/latest-mobile-stats#mobile-only 25% of mobile web users in U.S. never or

    infrequently access the desktop web.
  100. None
  101. Understanding mobile as the primary and sometimes only device… http://www.flickr.com/photos/e4a-2030/5106562313

  102. is difficult when we spend so much time on our

    PCs. http://www.flickr.com/photos/goobi/4021009835/
  103. Even the way we work as teams needs to change.

  104. http://mashable.com/2012/12/11/responsive-web-design/ Common first approach: Mobile, Tablet, & Desktop Breakpoints

  105. Resize until the page looks bad then… BOOM! you need

    a breakpoint.
  106. Major Breakpoint 1 (media query in document head) Major Breakpoint

    3 (media query in document head) 320 px to 720 px wide 720 px to 1024 px major breakpoints Example major layout changes 320 720 Major Breakpoint 2 (media query in document head) nothing is here...but that’s ok! (P) = Portrait (L) = Landscape (L*) = Landscape w/ native viewport adaptation < 320 px wide and/or unable to understand further instructions 1024 iPhone (P) many Android (P) many BlackBerry S60 QWERTY Most S60 (L) S40 QWERTY some tablets most NetBooks many Desktops http://www.slideshare.net/yiibu/pragmatic-responsive-design
  107. Major Breakpoint 3 (media query in document head) iPhone (L*)

    Android (L*) some Symbian touch (L) some tablets (L) some Symbian touch (L) 640 768 360 720 Major Breakpoint 1 (media query in document head) Major Breakpoint 2 (media query in document head) 720 px to 1024 px 320 px to 720 px wide nothing is here...but that’s ok! 320 minor breakpoints Example Symbian touch (P) (P) = Portrait (L) = Landscape (L*) = Landscape w/ native viewport adaptation iPhone (P) many Android (P) many BlackBerry S60 QWERTY Most S60 (L) S40 QWERTY < 320 px wide and/or unable to understand further instructions iPad (P) some Android tablets (P) Minor Breakpoint (@media) 1024 Minor Breakpoint (@media) Minor Breakpoint (@media) Minor Breakpoint (@media) 480 some tablets most NetBooks many Desktops content-related tweaks http://www.slideshare.net/yiibu/pragmatic-responsive-design
  108. iPhone (L*) Android (L*) some Symbian touch (L) some tablets

    (L) Minor Breakpoint (@media) Major Breakpoint 3 (media query in document head) 480 640 768 360 Symbian touch (P) 720 Major Breakpoint 1 (media query in document head) Major Breakpoint 2 (media query in document head) 720 px to 1024 px 320 px to 720 px wide nothing is here...but that’s ok! 320 240 Minor Breakpoint for small devices w/media query support < 320 px wide and/or unable to understand further instructions ...and so on Example some Symbian touch (L) (P) = Portrait (L) = Landscape (L*) = Landscape w/ native viewport adaptation iPad (P) some Android tablets (P) 1024 TVs Minor Breakpoint (@media) Minor Breakpoint (@media) Minor Breakpoint (@media) iPhone (P) many Android (P) many BlackBerry S60 QWERTY Most S60 (L) S40 QWERTY some Android (P) many S40 (P) most S60 (P) some tablets most NetBooks many Desktops http://www.slideshare.net/yiibu/pragmatic-responsive-design
  109. as you can see, this has the potential to get

    out of hand... iPhone (L*) Android (L*) some Symbian touch (L) some tablets (L) Minor Breakpoint (@media) some tablets (L) 640 768 360 Symbian touch (P) 720 Major Breakpoint 1 (media query in document head) Major Breakpoint 2 (media query in document head) TVs 720 px to 1024 px 320 px to 720 px wide nothing is here...but that’s ok! 320 240 Minor Breakpoint for small devices w/media query support some Android (P) many S40 (P) most S60 (P) < 320 px wide and/or unable to understand further instructions some Symbian touch (L) iPad (P) some Android tablets (P) Minor Breakpoints (@media) some tablets (L) 1280 800 Minor Breakpoint (@media) 600 some tablets (P) some tablets most NetBooks many Desktops 1366 many laptops Minor Breakpoint (@media) Minor Breakpoint (@media) Minor Breakpoint (@media) Major Breakpoint 3 (media query in document head) iPhone (P) many Android (P) many BlackBerry S60 QWERTY Most S60 (L) S40 QWERTY Minor Breakpoint (@media) 480 1024 http://www.slideshare.net/yiibu/pragmatic-responsive-design
  110. What’s the point?

  111. Don’t go chasing waterfalls.

  112. Old Waterfall Process http://viljamis.com/blog/2012/responsive-workflow/

  113. No way to design for every breakpoint in PhotoShop!

  114. New Responsive Design Process http://viljamis.com/blog/2012/responsive-workflow/

  115. Tiny Bootstraps, for Every Client Responsive deliverables should look a

    lot like fully-functioning Twitter Bootstrap- style systems custom tailored for your clients’ needs. These living code samples are self-documenting style guides that extend to accommodate a client’s needs as well as the needs of the ever-evolving multi-device web. —Dave Rupert, Responsive Deliverables http://daverupert.com/2013/04/responsive-deliverables/ “
  116. http://daverupert.com/2013/04/responsive-deliverables/ Responsive Deliverables

  117. None
  118. ! download " view on github # view demo pattern

    lab documentation about resources demo on github pattern lab atoms molecules organisms templates pages create atomic design systems http://patternlab.io
  119. None
  120. Responsive Conversion: Converting existing, working site to responsive.

  121. None
  122. Pattern identification exercise

  123. Group similar items and brainstorm names

  124. Repeat with larger components

  125. Fair warning: I use patterns and components interchangeably.

  126. None
  127. None
  128. None
  129. None
  130. An example sprint cycle T M F T W review

    briefing start F T M T W review approval end
  131. • How the patterns are used. • Any edge cases

    for the patterns. • Analytics information on the patterns. • User testing that has been done. • Support or user feedback on patterns. • Relevant documentation or styleguides. Each sprint starts with UX briefing on patterns
  132. Small screen sketching of patterns

  133. Move into code as quickly as possible

  134. Iterate quickly using whatever tools work best

  135. None
  136. None
  137. Each sprint the patterns get more complex, and the work

    moves faster because the completed patterns are building blocks.
  138. Some things we commonly do: Focus on parts of the

    interface, not the whole page. Prototype outside of the actual environment to keep things lightweight and fast. Pick the pieces of the interface that we think will be the most difficult to do on small screens and start there. Only when we have the small screen interface nailed, worry about larger screens and integration. Do the minimal possible to convey how it should work.
  139. #1 Iterative processes replace waterfalls. Design and development must work

    together. No silos. Designing systems of responsive components. #2 #3
  140. Responsive is the answer. http://www.flickr.com/photos/38208449@N00/7712219364

  141. We need to be responsive. http://www.flickr.com/photos/cdm/147947664/

  142. Learn how to let go of the illusions that comfort

    us. http://www.flickr.com/photos/garibaldi/303085857/
  143. None
  144. None
  145. This is the web as it should be. As it

    wants to be. The web in its natural state. http://www.flickr.com/photos/25062265@N06/6069101123
  146. It’s what our users expect. http://www.flickr.com/photos/johanl/6798184016

  147. If you don’t adapt, then you are ripe for disruption.

    http://www.flickr.com/photos/gsfc/7521155076/
  148. None
  149. Thank You! Special thanks to Luke Wroblewski, Eric Bidelman and

    Flickr users for generously sharing their photos under creative commons license.