Adaptive Input — BDConf Nashville

Transcript

1. Adaptive Input Jason Grigsby • @grigs • cloudfour.com http://bit.ly/grigs-bdconf14
4. http://theunipiper.com
7. https://twitter.com/droidweb/status/494163677000372224
8. Follow along at @grigs_talks http://bit.ly/grigs-bdconf14
9. http://www.flickr.com/photos/cdm/51747860/
10. http://www.flickr.com/photos/rheaney/4397863376 It started with TVs.
11. Designing for a 10-foot UI is very different. http://www.flickr.com/photos/chrisbartow/5835428673
12. Larger text and fewer words.
13. Make up, down, left, right directions clear. http://images.dailytech.com/nimage/29122_large_amazon_prime_screen_5.jpg
14. How do we know what is a TV?
15. This is HDTV.
16. This is HDTV. 1980 px 1080 px
17. Resolution does not define the optimal experience.
18. Next came responsive web apps. https://twitter.com/freediverx/status/354698695041744896
19. Responsive design for apps is inevitable. http://blog.cloudfour.com/responsive-design-for-apps-part-1/
20. Lines between device classes are blurring Model Type Size Size Display Resolution Resolution Viewport 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
21. 640 px 600 px 519 px 640 px 622 px 533 px 812 px Which are phones and which are tablets?
22. http://www.flickr.com/photos/geatchy/8489505999
23. How do I make this responsive? How do I make this responsive?
25. 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
32. 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 different platforms with different 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
33. Sometimes it’s hard to envision a responsive version. http://demos.kendoui.com/web/grid/editing.html
34. http://www.flickr.com/photos/jesuspresley/384080245/ We want people to be productive…
35. and stay in the zone. http://www.flickr.com/photos/raccatography/8038855203
36. http://www.flickr.com/photos/shantellmartin/4543010568 Which seems very different from playing on an iPad.
37. For both the TV…
38. and the desktop web app…
39. input matters much more than screen size.
40. The grid is important to support d-pad interaction. http://images.dailytech.com/nimage/29122_large_amazon_prime_screen_5.jpg
41. http://www.flickr.com/photos/royalsapien/2387707860
42. And keyboard and mouse are what we envision work is. http://www.flickr.com/photos/royalsapien/2387707860
43. http://www.flickr.com/photos/hellogeri/6154034099/ A few years ago, Jeremy talked about how…
44. http://www.flickr.com/photos/60415054@N00/14301113/ we told ourselves that the web was…
45. http://www.flickr.com/photos/60415054@N00/14301113/
46. http://www.flickr.com/photos/60415054@N00/14301113/ 640 px 480 px
47. 640 px 480 px
52. 1024 px 768 px
53. http://www.flickr.com/photos/adactio/6153481666/
54. http://www.flickr.com/photos/adactio/6153481666/ Then mobile came and made us realize…
55. that it was a consensual hallucination all along. http://www.flickr.com/photos/garibaldi/303085857/
56. The web never had a fixed canvas. http://www.flickr.com/photos/paulocarrillo/124755065/
57. Even our tools perpetuate the lie.
58. http://www.flickr.com/photos/69797234@N06/7203485148/ We’ve made tremendous progress.
59. But there is another consensual hallucination. http://www.flickr.com/photos/garibaldi/303085857/
61. = =
63. Supports hover and pointer events.
66. Keyboard and touch.
69. Even the iPhone can have a keyboard.
72. Are these laptops or tablets?
75. Desktop computer with 23” touch screen
77. Luke nailed it. http://static.lukew.com/unified_device_design.png
79. We can no longer make assumptions about input based on screen size or form factor. And we probably never should have.
80. http://www.flickr.com/photos/cblue98/7254221968
81. Input represents a bigger challenge than screen size. http://www.flickr.com/photos/cblue98/7254221968
82. http://www.flickr.com/photos/taedc/9278192929
83. And it is changing more rapidly than ever before. http://www.flickr.com/photos/taedc/9278192929
84. So let’s take a closer look…
85. Let’s start with futuristic input. http://www.flickr.com/photos/jdhancock/3714748769/
86. http://uncyclopedia.wikia.com/wiki/ File:Man_yelling_at_computer.JPG VOICE
87. http://uncyclopedia.wikia.com/wiki/ File:Man_yelling_at_computer.JPG VOICE
88. http://www.98ps.com/viewnews-15222.html
89. Siri gets all of the hype… http://www.98ps.com/viewnews-15222.html
90. but both Microsoft and Google have compelling voice input in their products.
94. How should web pages change to support voice control?
97. Google voice search
98. You can use speech recognition too. http://www.google.com/intl/en/chrome/demos/speech.html http://www.moreawesomeweb.com/demos/speech_translate.html
99. Web Speech API Specification 19 October 2012 Editors: Glen Shires, Google Inc. Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups.
100. Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult
101. Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult
102. Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult
103. Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events
104. Hans Wennborg, Google Inc. Please refer to the errata for this document, which may include some normative corrections. Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events 5.1.4 SpeechRecognitionError 5.1.5 SpeechRecognitionAlternative 5.1.6 SpeechRecognitionResult Copyright © 2012 the Contributors to the Web Speech API Specification, published by the Speech API Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available. Abstract This specification defines a JavaScript API to enable web developers to incorporate speech recognition and synthesis into their web pages. It enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives. Status of This Document This specification was published by the Speech API Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups. All feedback is welcome. Table of Contents 1 Conformance requirements 2 Introduction 3 Use Cases 4 Security and privacy considerations 5 API Description 5.1 The SpeechRecognition Interface 5.1.1 SpeechRecognition Attributes 5.1.2 SpeechRecognition Methods 5.1.3 SpeechRecognition Events
105. Special thanks to Eric Bidelman http://moreawesomeweb.com Speech Recognition API Support
107. Gestures?
108. http://leapmotion.com
109. https://www.kickstarter.com/projects/1761670738/ring-shortcut-everything
110. https://www.kickstarter.com/projects/1761670738/ring-shortcut-everything
111. https://vine.co/v/MIjTE3ZDxa3
113. Amazing, but too new to know what, if anything, this technology will mean for the web.
114. Let’s come back from the future and look at something much Dumber. Dumber
115. Dumber
116. Dumber
117. -pad remote controls D
118. -pad remote controls D
119. -pad remote controls D
120. http://www.flickr.com/photos/stewc/6669743035/
121. http://www.flickr.com/photos/stewc/6669743035/ TVs browsers that support d-pad, send arrow key events.
122. http://www.wasdkeyboards.com/index.php/catalog/product/gallery/id/7164/image/343/
123. If then http://www.wasdkeyboards.com/index.php/catalog/product/gallery/id/7164/image/343/
125. is undetectable. This is a recurring theme for input.
126. Sensors and camera http://www.flickr.com/photos/retrocactus/2170677056
127. Sensors and camera Camera http://www.flickr.com/photos/retrocactus/2170677056
128. GPS http://www.flickr.com/photos/3dking/149450434
129. GPS GeoLocation http://www.flickr.com/photos/3dking/149450434
131. Gyroscope & Accelerometer
132. http://www.flickr.com/photos/chrisjagers/4694134078
133. Back to today’s problems. http://www.flickr.com/photos/chrisjagers/4694134078
135. Hover state No hover state
136. Hover state Typing easier for many No hover state Typing often more difficult
137. 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 difficult
138. 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 difficult Right clicking and “power” tools Single and multi-touch gestures
141. http://www.flickr.com/photos/28096801@N05/5012309802
142. I got this. Detect touch. http://www.flickr.com/photos/28096801@N05/5012309802
144. 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/
145. 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
147. Detect a mouse? Not reliably.
150. Surely we can detect a keyboard?
151. Surely we can detect a keyboard? NOPE
153. Input is dynamic.
154. Input is dynamic.
155. Boris Smus’s experiments responding to input. http://smus.com/touch-laptop-experiments/
156. Boris Smus’s experiments responding to input. http://smus.com/touch-laptop-experiments/
157. http://www.flickr.com/photos/lyza/7382235106 Maybe we need to be more zen about input.
159. 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
161. What about those who won’t let go of their “power” interfaces? http://www.flickr.com/photos/ecos/4092571213/
162. http://www.flickr.com/photos/scarygami/5689980135/ One option: give them a choice.
164. Gmail display density settings
167. 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
168. 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
169. 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
170. Vimeo Couch Mode
172. The key benefit of this approach: You’re designing for user need not for a specific form factor or input.
173. http://www.flickr.com/photos/raver_mikey/504815463
175. Progressive Input?
176. Graph from Chapter 1 of Adaptive Web Design by Aaron Gustafson http://easy-readers.net/books/ adaptive-web-design/
177. Graph from Chapter 1 of Adaptive Web Design by Aaron Gustafson http://easy-readers.net/books/ adaptive-web-design/ Progressive enhancement contains a value judgment
178. Who are we to judge what input is better? http://www.flickr.com/photos/fensterbme/4783366926
179. We need to adapt and respond. http://www.flickr.com/photos/cdm/147947664/
180. Learn how to let go of the illusions that comfort us. http://www.flickr.com/photos/garibaldi/303085857/
184. 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
185. It is what our users expect. http://www.flickr.com/photos/johanl/ 6798184016
187. http://www.flickr.com/photos/wwworks/138495
188. Thank You! SLIDES: http://bit.ly/grigs-bdconf14 Special thanks to Flickr users for generously sharing their photos under creative commons license.