Tweet
Tweet

Slide 1

Slide 1 text

Being Responsive Jason Grigsby • @grigs • cloudfour.com

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

http://www.opera.com/smw/ Not just smartphones. Opera Mini growing as well.

Slide 6

Slide 6 text

7.1 Billion Mobile phone for nearly everyone on the planet. Flickr photo by Pingnews: http://www.flickr.com/photos/pingnews/370061022/

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

http://www.flickr.com/photos/76074333@N00/317952268/ | http://futuristmovie.com Creative Commons BY-NC-SA 2.0

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

ME NEED IPHONE APP. http://www.flickr.com/photos/corbett3000/2327165138/in/set-72157604094629546/

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

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

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

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

Slide 26

Slide 26 text

But not the way you’re thinking.

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

There are other paths you can take… http://www.flickr.com/photos/95572727@N00/4204913417

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

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

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

Let’s say you’re going to build a separate site or app for specific form factor.

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

640 px 600 px 519 px 640 px 622 px 533 px 812 px Which are phones and which are tablets?

Slide 38

Slide 38 text

http://www.flickr.com/photos/geatchy/8489505999

Slide 39

Slide 39 text

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

Slide 40

Slide 40 text

PERFORMANCE

Slide 41

Slide 41 text

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

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

http://www.flickr.com/photos/beautyredefined/2643858323/

Slide 47

Slide 47 text

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

Slide 48

Slide 48 text

Most responsive web designs are…

Slide 49

Slide 49 text

The resounding answer from the community: Mobile First Responsive Web Design

Slide 50

Slide 50 text

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

Slide 51

Slide 51 text

Mobile First Design Principles Mobile First Responsive Design Forwarded by 
 Luke Wroblewski Technical Approach for Responsive Design

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

*FIRST Content First Structure First Performance First API First Command Line First

Slide 54

Slide 54 text

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

Slide 55

Slide 55 text

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

Slide 56

Slide 56 text

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

Slide 57

Slide 57 text

https://twitter.com/freediverx/status/354698695041744896

Slide 58

Slide 58 text

How do I make this responsive?

Slide 59

Slide 59 text

How do I make this responsive?

Slide 60

Slide 60 text

How do I make this responsive?

Slide 61

Slide 61 text

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

Slide 62

Slide 62 text

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

Slide 63

Slide 63 text

What would the mobile version look like?

Slide 64

Slide 64 text

What would the mobile version look like?

Slide 65

Slide 65 text

How does that map to desktop design?

Slide 66

Slide 66 text

How does that map to desktop design?

Slide 67

Slide 67 text

How does that map to desktop design?

Slide 68

Slide 68 text

How does that map to desktop design?

Slide 69

Slide 69 text

How does that map to desktop design?

Slide 70

Slide 70 text

How does that map to desktop design?

Slide 71

Slide 71 text

How does that map to desktop design?

Slide 72

Slide 72 text

How does that map to desktop design?

Slide 73

Slide 73 text

How does that map to desktop design?

Slide 74

Slide 74 text

How does that map to desktop design?

Slide 75

Slide 75 text

Can this desktop version be better using what we’ve learned from the mobile version?

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

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

Slide 78

Slide 78 text

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.

Slide 79

Slide 79 text

http://www.flickr.com/photos/soldiersmediacenter/6999691421 Yes, there are obstacles…

Slide 80

Slide 80 text

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

Slide 81

Slide 81 text

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

Slide 82

Slide 82 text

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

Slide 83

Slide 83 text

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

Slide 84

Slide 84 text

640 px 480 px

Slide 85

Slide 85 text

800 px 600 px

Slide 86

Slide 86 text

1024 px 768 px

Slide 87

Slide 87 text

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

Slide 88

Slide 88 text

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

Slide 89

Slide 89 text

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

Slide 90

Slide 90 text

Even our tools perpetuate the lie.

Slide 91

Slide 91 text

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

Slide 92

Slide 92 text

We often dismiss as unlikely the idea that someone will want to use our service on a small screen.

Slide 93

Slide 93 text

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/

Slide 94

Slide 94 text

http://www.flickr.com/photos/brunauto/5062644167/

Slide 95

Slide 95 text

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

Slide 96

Slide 96 text

TMI

Slide 97

Slide 97 text

39% use phone on toilet

Slide 98

Slide 98 text

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

Slide 99

Slide 99 text

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.

Slide 100

Slide 100 text

No content

Slide 101

Slide 101 text

Understanding mobile as the primary and sometimes only device… http://www.flickr.com/photos/e4a-2030/5106562313

Slide 102

Slide 102 text

is difficult when we spend so much time on our PCs. http://www.flickr.com/photos/goobi/4021009835/

Slide 103

Slide 103 text

Even the way we work as teams needs to change.

Slide 104

Slide 104 text

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

Slide 105

Slide 105 text

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

Slide 106

Slide 106 text

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

Slide 107

Slide 107 text

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

Slide 108

Slide 108 text

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

Slide 109

Slide 109 text

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

Slide 110

Slide 110 text

What’s the point?

Slide 111

Slide 111 text

Don’t go chasing waterfalls.

Slide 112

Slide 112 text

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

Slide 113

Slide 113 text

No way to design for every breakpoint in PhotoShop!

Slide 114

Slide 114 text

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

Slide 115

Slide 115 text

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/ “

Slide 116

Slide 116 text

http://daverupert.com/2013/04/responsive-deliverables/ Responsive Deliverables

Slide 117

Slide 117 text

No content

Slide 118

Slide 118 text

! 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

Slide 119

Slide 119 text

No content

Slide 120

Slide 120 text

Responsive Conversion: Converting existing, working site to responsive.

Slide 121

Slide 121 text

No content

Slide 122

Slide 122 text

Pattern identification exercise

Slide 123

Slide 123 text

Group similar items and brainstorm names

Slide 124

Slide 124 text

Repeat with larger components

Slide 125

Slide 125 text

Fair warning: I use patterns and components interchangeably.

Slide 126

Slide 126 text

No content

Slide 127

Slide 127 text

No content

Slide 128

Slide 128 text

No content

Slide 129

Slide 129 text

No content

Slide 130

Slide 130 text

An example sprint cycle T M F T W review briefing start F T M T W review approval end

Slide 131

Slide 131 text

• 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

Slide 132

Slide 132 text

Small screen sketching of patterns

Slide 133

Slide 133 text

Move into code as quickly as possible

Slide 134

Slide 134 text

Iterate quickly using whatever tools work best

Slide 135

Slide 135 text

No content

Slide 136

Slide 136 text

No content

Slide 137

Slide 137 text

Each sprint the patterns get more complex, and the work moves faster because the completed patterns are building blocks.

Slide 138

Slide 138 text

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.

Slide 139

Slide 139 text

#1 Iterative processes replace waterfalls. Design and development must work together. No silos. Designing systems of responsive components. #2 #3

Slide 140

Slide 140 text

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

Slide 141

Slide 141 text

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

Slide 142

Slide 142 text

Learn how to let go of the illusions that comfort us. http://www.flickr.com/photos/garibaldi/303085857/

Slide 143

Slide 143 text

No content

Slide 144

Slide 144 text

No content

Slide 145

Slide 145 text

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

Slide 146

Slide 146 text

It’s what our users expect. http://www.flickr.com/photos/johanl/6798184016

Slide 147

Slide 147 text

If you don’t adapt, then you are ripe for disruption. http://www.flickr.com/photos/gsfc/7521155076/

Slide 148

Slide 148 text

No content

Slide 149

Slide 149 text

Thank You! Special thanks to Luke Wroblewski, Eric Bidelman and Flickr users for generously sharing their photos under creative commons license.