Being Responsive - Nike

Slide 1

Slide 1 text

Being Responsive Jason Grigsby • @grigs • cloudfour.com

Slide 2

Slide 2 text

http://bit.ly/grigs-nike15 Follow along at @grigs_talks

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

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

Slide 5

Slide 5 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 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 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 9

Slide 9 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 10

Slide 10 text

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

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

No content

Slide 17

Slide 17 text

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

Slide 18

Slide 18 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 19

Slide 19 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 20

Slide 20 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 21

Slide 21 text

2011 We must have a... 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.slideshare.net/jamesgpearce/html5-and-the- dawn-of-rich-mobile-web-applications-pt-1

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

http://www.ﬂickr.com/photos/ lukew/10412585943/

Slide 26

Slide 26 text

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

Slide 27

Slide 27 text

But not the way you’re thinking.

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

No content

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

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

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

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

Slide 37

Slide 37 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 38

Slide 38 text

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

Slide 39

Slide 39 text

320 iPad, iPad Mini, iPad Air x 480 x 568 320 x 667 375 x 736 414 x 768 1024 iPhone - iPhone 4s iPhone 5 iPhone 5c iPhone 5s iPhone 6 iPhone 6 Plus Even iOS is now a continuum.

Slide 40

Slide 40 text

iPad, iPad Mini, iPad Air 480 320 568 320 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 5 iPhone 5c iPhone 5s iPhone 6 iPhone 6 Plus Even iOS is now a continuum.

Slide 41

Slide 41 text

iPad, iPad Mini, iPad Air 480 320 568 320 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 5 iPhone 5c iPhone 5s iPhone 6 iPhone 6 Plus Even iOS is now a continuum.

Slide 42

Slide 42 text

iPad, iPad Mini, iPad Air 480 320 568 320 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 6 iPhone 6 Plus Even iOS is now a continuum. iPhone 5 iPhone 5c iPhone 5s

Slide 43

Slide 43 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 6 iPhone 6 Plus Even iOS is now a continuum. iPhone 5 iPhone 5c iPhone 5s

Slide 44

Slide 44 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 6 iPhone 6 Plus Even iOS is now a continuum. iPhone 5 iPhone 5c iPhone 5s

Slide 45

Slide 45 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 5 iPhone 5c iPhone 5s iPhone 6 iPhone 6 Plus Even iOS is now a continuum.

Slide 46

Slide 46 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 5 iPhone 5c iPhone 5s iPhone 6 iPhone 6 Plus Even iOS is now a continuum.

Slide 47

Slide 47 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 5 iPhone 5c iPhone 5s iPhone 6 iPhone 6 Plus Even iOS is now a continuum.

Slide 48

Slide 48 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 6 iPhone 6 Plus Even iOS is now a continuum. iPhone 5 iPhone 5c iPhone 5s

Slide 49

Slide 49 text

iPad, iPad Mini, iPad Air 480 320 568 667 375 736 414 768 1024 iPhone - iPhone 4s iPhone 6 iPhone 6 Plus Even iOS is now a continuum. The Magic 32 pixels iPhone 5 iPhone 5c iPhone 5s

Slide 50

Slide 50 text

https://twitter.com/_munter_/status/511770590123143168

Slide 51

Slide 51 text

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

Slide 52

Slide 52 text

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

Slide 53

Slide 53 text

PERFORMANCE

Slide 54

Slide 54 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 55

Slide 55 text

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

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

http://www.ﬂickr.com/photos/beautyredeﬁned/2643858323/

Slide 60

Slide 60 text

http://www.ﬂickr.com/photos/puuikibeach/3654517679

Slide 61

Slide 61 text

Most responsive web designs are…

Slide 62

Slide 62 text

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

Slide 63

Slide 63 text

http://www.ﬂickr.com/photos/localcelebrity/4831362933/ Diﬀerent than Mobile First Design Theory

Slide 64

Slide 64 text

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

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

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

Slide 67

Slide 67 text

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

Slide 68

Slide 68 text

http://www.ﬂickr.com/photos/gumption/3639682201/

Slide 69

Slide 69 text

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

Slide 70

Slide 70 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 71

Slide 71 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 72

Slide 72 text

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

Slide 73

Slide 73 text

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

Slide 74

Slide 74 text

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

Slide 75

Slide 75 text

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

Slide 76

Slide 76 text

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

Slide 77

Slide 77 text

640 px 480 px

Slide 78

Slide 78 text

800 px 600 px

Slide 79

Slide 79 text

1024 px 768 px

Slide 80

Slide 80 text

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

Slide 81

Slide 81 text

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

Slide 82

Slide 82 text

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

Slide 83

Slide 83 text

Even our tools perpetuate the lie.

Slide 84

Slide 84 text

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

Slide 85

Slide 85 text

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

Slide 86

Slide 86 text

It’s fairly certain that the highest-value use will stay predominantly on desktop. —Jakob Nielsen http://www.ﬂickr.com/photos/dplanet/82899080/

Slide 87

Slide 87 text

Most complex tasks have vastly better user experience on the desktop and thus will be performed there… Yes, you might enter a stock trade with your broker's mobile app, but you'll research new mutual funds on the desktop. —Jakob Nielsen

Slide 88

Slide 88 text

http://www.ﬂickr.com/photos/brunauto/5062644167/

Slide 89

Slide 89 text

80% during misc downtime 76% while waiting in lines 86% while watching TV 69% for point of sale research http://www.ﬂickr.com/photos/carbonnyc/5140154965

Slide 90

Slide 90 text

TMI

Slide 91

Slide 91 text

39% use phone on toilet

Slide 92

Slide 92 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/ﬀ/entry.asp?1333

Slide 93

Slide 93 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 94

Slide 94 text

No content

Slide 95

Slide 95 text

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

Slide 96

Slide 96 text

is diﬃcult when we spend so much time on our PCs. http://www.ﬂickr.com/photos/goobi/4021009835/

Slide 97

Slide 97 text

Even the way we work as teams needs to change.

Slide 98

Slide 98 text

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

Slide 99

Slide 99 text

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

Slide 100

Slide 100 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 101

Slide 101 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 102

Slide 102 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 103

Slide 103 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 104

Slide 104 text

What’s the point?

Slide 105

Slide 105 text

Don’t go chasing waterfalls.

Slide 106

Slide 106 text

Old Waterfall Process http://viljamis.com/blog/2012/responsive-workﬂow/

Slide 107

Slide 107 text

No way to design for every breakpoint in PhotoShop!

Slide 108

Slide 108 text

New Responsive Design Process http://viljamis.com/blog/2012/responsive-workﬂow/

Slide 109

Slide 109 text

Older version of Marriott Search Results

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

What if this was the design for the small screen version?

Slide 112

Slide 112 text

See a challenge making this responsive?

Slide 113

Slide 113 text

Anyone see a challenge making this responsive? Eventually Flexbox will make this easy. But in the meantime, it requires a lot of DOM manipulation.

Slide 114

Slide 114 text

Another example of why design and development need to work closely.

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

1. Discovery 2. Sketching 3. Dynamic Mockups 4. Expansion + Iteration Cloud Four’s Responsive Design Process

Slide 121

Slide 121 text

An example sprint cycle

Slide 122

Slide 122 text

No content

Slide 123

Slide 123 text

No content

Slide 124

Slide 124 text

No content

Slide 125

Slide 125 text

No content

Slide 126

Slide 126 text

Tools that we commonly use.

Slide 127

Slide 127 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 diﬃcult 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 128

Slide 128 text

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

Slide 129

Slide 129 text

We need to learn to let go.

Slide 130

Slide 130 text

http://www.flickr.com/photos/cdm/51747860/

Slide 131

Slide 131 text

http://www.flickr.com/photos/rheaney/4397863376 It started with TVs.

Slide 132

Slide 132 text

Designing for a 10-foot UI is very diﬀerent. http://www.flickr.com/photos/chrisbartow/5835428673

Slide 133

Slide 133 text

Larger text and fewer words.

Slide 134

Slide 134 text

Make up, down, left, right directions clear. http://images.dailytech.com/nimage/29122_large_amazon_prime_screen_5.jpg

Slide 135

Slide 135 text

How do we know what is a TV?

Slide 136

Slide 136 text

This is HDTV. 1980 px 1080 px

Slide 137

Slide 137 text

Resolution does not define the optimal experience.

Slide 138

Slide 138 text

Next came responsive web apps. https://twitter.com/freediverx/status/354698695041744896

Slide 139

Slide 139 text

How do I make this existing application responsive?

Slide 140

Slide 140 text

mobile desktop THE ART OF WEB DEVELOPMENT THE ART OF WEB DEVELOPMENT Web widgets THE ART OF WEB DEVELOPMENT THE ART OF WEB DEVELOPMENT Mobile widgets

Slide 141

Slide 141 text

No content

Slide 142

Slide 142 text

No content

Slide 143

Slide 143 text

No content

Slide 144

Slide 144 text

It’s not that we’re technically incapable, but adapting a phone UI to a tablet UI is not so dissimilar from trying to automatically adapt desktop UI to a phone. They are fundamentally diﬀerent platforms with diﬀerent usability considerations, and something that makes sense on phones may or may not belong on tablets. —Todd Anglin, Kendo UI http://www.kendoui.com/blogs/teamblog/posts/12-09-11/universal_mobile_apps_with_html5_and_kendo_ui.aspx

Slide 145

Slide 145 text

Sometimes it’s hard to envision a responsive version. http://demos.kendoui.com/web/grid/editing.html

Slide 146

Slide 146 text

http://www.flickr.com/photos/jesuspresley/384080245/ We want people to be productive…

Slide 147

Slide 147 text

and stay in the zone. http://www.flickr.com/photos/raccatography/8038855203

Slide 148

Slide 148 text

http://www.flickr.com/photos/shantellmartin/4543010568 Which seems very diﬀerent from playing on an iPad.

Slide 149

Slide 149 text

For both the TV…

Slide 150

Slide 150 text

and the desktop web app…

Slide 151

Slide 151 text

input matters much more than screen size.

Slide 152

Slide 152 text

The grid is important to support d-pad interaction. http://images.dailytech.com/nimage/29122_large_amazon_prime_screen_5.jpg

Slide 153

Slide 153 text

And keyboard and mouse are what we envision work is. http://www.flickr.com/photos/royalsapien/2387707860

Slide 154

Slide 154 text

We’ve started letting go of some of our mistaken assumptions. http://www.flickr.com/photos/paulocarrillo/124755065/

Slide 155

Slide 155 text

But there is another consensual hallucination. http://www.flickr.com/photos/garibaldi/303085857/

Slide 156

Slide 156 text

= =

Slide 157

Slide 157 text

Supports hover and pointer events.

Slide 158

Slide 158 text

Keyboard and touch.

Slide 159

Slide 159 text

Even the iPhone can have a keyboard.

Slide 160

Slide 160 text

Are these laptops or tablets?

Slide 161

Slide 161 text

Desktop computer with 23” touch screen

Slide 162

Slide 162 text

Luke Wroblewski nailed it. http://static.lukew.com/unified_device_design.png

Slide 163

Slide 163 text

We can no longer make assumptions about input based on screen size or form factor. And we probably never should have.

Slide 164

Slide 164 text

What makes desktop diﬀerent? http://www.flickr.com/photos/chrisjagers/4694134078

Slide 165

Slide 165 text

Higher precision with mouse means smaller targets possible Hover state Less precise than mouse and requires larger touch targets Typing easier for many No hover state Typing often more diﬃcult Right clicking and “power” tools Single and multi-touch gestures

Slide 166

Slide 166 text

No content

Slide 167

Slide 167 text

I got this. Detect touch. http://www.flickr.com/photos/28096801@N05/5012309802

Slide 168

Slide 168 text

Whatever you may think, it currently isn't possible to reliably detect whether or not the current device has a touchscreen, from within the browser. —Stu Cox, You Can’t Reliably Detect a Touch Screen http://www.stucox.com/blog/you-cant-detect-a-touchscreen/

Slide 169

Slide 169 text

Chrome has entertained idea of enabling touch by default. https://code.google.com/p/chromium/issues/detail?id=159527 https://docs.google.com/a/cloudfour.com/presentation/d/1-n1qyzewpagREbzW2zm0wOalq33UhbtbSkWf9mEdly8/edit#slide=id.gc2d80e5b_171

Slide 170

Slide 170 text

Detect a mouse? Not reliably.

Slide 171

Slide 171 text

Surely we can detect a keyboard? NOPE

Slide 172

Slide 172 text

Input is dynamic.

Slide 173

Slide 173 text

No content

Slide 174

Slide 174 text

http://www.flickr.com/photos/lyza/7382235106 Maybe we need to be more zen about input.

Slide 175

Slide 175 text

After poking at this problem for a few weeks, my conclusion is: every desktop UI should be designed for touch now. When any desktop machine could have a touch interface, we have to proceed as if they all do. —Josh Clark http://globalmoxie.com/blog/desktop-touch-design.shtml

Slide 176

Slide 176 text

No content

Slide 177

Slide 177 text

What about those who won’t let go of their “power” interfaces? http://www.flickr.com/photos/ecos/4092571213/

Slide 178

Slide 178 text

http://www.flickr.com/photos/scarygami/5689980135/ One option: give them a choice.

Slide 179

Slide 179 text

No content

Slide 180

Slide 180 text

Display density settings

Slide 181

Slide 181 text

Th Dream Experience - … Uploaded 2 years ago More Of The Dream Exp… Uploaded 2 years ago The Dream Experience -… Uploaded 2 years ago The Dream Experience … Uploaded 2 years ago The Love King Breaks It… Uploaded 2 years ago War Paint for Trees From Lincoln Motor Company Join Log In Create Watch Upload Search s [ ] – VIDEOS Vimeo Couch Mode

Slide 182

Slide 182 text

Couch Mode + See all Centric TV’s videos / Recently viewed / Related videos Th Dream Experience - … Uploaded 2 years ago More Of The Dream Exp… Uploaded 2 years ago The Dream Experience -… Uploaded 2 years ago The Dream Experience … Uploaded 2 years ago The Love King Breaks It… Uploaded 2 years ago PROMOTED War Paint for Trees From Lincoln Motor Company Join Log In Create Watch Upload Search s [ ] – VIDEOS Couch Mode + See all Centric TV’s videos / Recently viewed / Related videos Th Dream Experience - … Uploaded 2 years ago More Of The Dream Exp… Uploaded 2 years ago The Dream Experience -… Uploaded 2 years ago The Dream Experience … Uploaded 2 years ago The Love King Breaks It… Uploaded 2 years ago PROMOTED War Paint for Trees From Lincoln Motor Company Join Log In Create Watch Upload Search s [ ] – VIDEOS Vimeo Couch Mode

Slide 183

Slide 183 text

Vimeo Couch Mode

Slide 184

Slide 184 text

The key benefit of this approach: You’re designing for user need not for a specific form factor or input.

Slide 185

Slide 185 text

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

Slide 186

Slide 186 text

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

Slide 187

Slide 187 text

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

Slide 188

Slide 188 text

No content

Slide 189

Slide 189 text

No content

Slide 190

Slide 190 text

This is the web as it should be. As it wants to be. The web in its natural state. http://www.ﬂickr.com/photos/25062265@N06/6069101123

Slide 191

Slide 191 text

It is what our customers expect. http://www.ﬂickr.com/photos/johanl/6798184016

Slide 192

Slide 192 text

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

Slide 193

Slide 193 text

No content

Slide 194

Slide 194 text

No content

Slide 195

Slide 195 text

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