Tweet
Tweet

Slide 1

Slide 1 text

Jason Grigsby • @grigs • cloudfour.com Adaptive Input http://www.flickr.com/photos/cobalt/7217055290/

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

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

Slide 6

Slide 6 text

Larger text and fewer words.

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

How do we know what is a TV?

Slide 9

Slide 9 text

This is HDTV. 1980 px 1080 px

Slide 10

Slide 10 text

Resolution does not define the optimal experience.

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

Responsive design for apps is inevitable.

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

Lines between device classes are blurring

Slide 15

Slide 15 text

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

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

but the specifics of the app that I was asked to look at presented a different challenge. The question I faced was a little different.

Slide 18

Slide 18 text

How do I make this existing application responsive?

Slide 19

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

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 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 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

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

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

Slide 26

Slide 26 text

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

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

For both the TV…

Slide 29

Slide 29 text

and the desktop web app…

Slide 30

Slide 30 text

input matters much more than screen size.

Slide 31

Slide 31 text

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

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

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

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

640 px 480 px

Slide 37

Slide 37 text

800 px 600 px

Slide 38

Slide 38 text

1024 px 768 px

Slide 39

Slide 39 text

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

Slide 40

Slide 40 text

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

Slide 41

Slide 41 text

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

Slide 42

Slide 42 text

Even our tools perpetuate the lie.

Slide 43

Slide 43 text

http://www.flickr.com/photos/69797234@N06/7203485148/ We’ve made tremendous progress.

Slide 44

Slide 44 text

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

Slide 45

Slide 45 text

= =

Slide 46

Slide 46 text

Supports hover and pointer events.

Slide 47

Slide 47 text

Keyboard and touch.

Slide 48

Slide 48 text

Even the iPhone can have a keyboard.

Slide 49

Slide 49 text

Are these laptops or tablets?

Slide 50

Slide 50 text

Desktop computer with 23” touch screen

Slide 51

Slide 51 text

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

Slide 52

Slide 52 text

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

Slide 53

Slide 53 text

Input represents a bigger challenge than screen size. http://www.flickr.com/photos/cblue98/7254221968

Slide 54

Slide 54 text

And it is changing more rapidly than ever before. http://www.flickr.com/photos/taedc/9278192929

Slide 55

Slide 55 text

So let’s take a closer look…

Slide 56

Slide 56 text

Let’s start with futuristic input. http://www.flickr.com/photos/jdhancock/3714748769/

Slide 57

Slide 57 text

http://uncyclopedia.wikia.com/wiki/File:Man_yelling_at_computer.JPG VOICE

Slide 58

Slide 58 text

Siri gets all of the hype… http://www.98ps.com/viewnews-15222.html

Slide 59

Slide 59 text

but both Microsoft and Google have compelling voice input in their products.

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

No content

Slide 63

Slide 63 text

How should web pages change to support voice control?

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

Google voice search

Slide 67

Slide 67 text

You can use speech recognition too. http://www.google.com/intl/en/chrome/demos/speech.html http://www.moreawesomeweb.com/demos/speech_translate.html

Slide 68

Slide 68 text

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.

Slide 69

Slide 69 text

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

Slide 70

Slide 70 text

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

Slide 71

Slide 71 text

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

Slide 72

Slide 72 text

Special thanks to Eric Bidelman http://moreawesomeweb.com Speech Recognition API Support ?

Slide 73

Slide 73 text

Gestures?

Slide 74

Slide 74 text

Amazing, but too new to know what, if anything, this technology will mean for the web.

Slide 75

Slide 75 text

Let’s come back from the future and look at something much Dumber. Dumber

Slide 76

Slide 76 text

-pad remote controls Dumber

Slide 77

Slide 77 text

-pad remote controls D

Slide 78

Slide 78 text

http://www.flickr.com/photos/stewc/6669743035/ TVs browsers that support d-pad, send arrow key events.

Slide 79

Slide 79 text

If then http://www.wasdkeyboards.com/index.php/catalog/product/gallery/id/7164/image/343/

Slide 80

Slide 80 text

is undetectable. This is a recurring theme for input.

Slide 81

Slide 81 text

Sensors and camera Camera http://www.flickr.com/photos/retrocactus/2170677056

Slide 82

Slide 82 text

GPS GeoLocation http://www.flickr.com/photos/3dking/149450434

Slide 83

Slide 83 text

Gyroscope & Accelerometer

Slide 84

Slide 84 text

Add list of sensors from Luke’s slides

Slide 85

Slide 85 text

Back to today’s problems. http://www.flickr.com/photos/chrisjagers/4694134078

Slide 86

Slide 86 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 difficult Right clicking and “power” tools Single and multi-touch gestures

Slide 87

Slide 87 text

No content

Slide 88

Slide 88 text

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

Slide 89

Slide 89 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 90

Slide 90 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 91

Slide 91 text

Detect a mouse? Not reliably.

Slide 92

Slide 92 text

Surely we can detect a keyboard? NOPE

Slide 93

Slide 93 text

Input is dynamic.

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

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

Slide 96

Slide 96 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 97

Slide 97 text

No content

Slide 98

Slide 98 text

http://ie.microsoft.com/testdrive/ieblog/2011/Sep/20_TouchInputforIE10andMetrostyleApps_1.png http://www.w3.org/TR/pointerevents/ http://blog.webplatform.org/2013/02/pointing-toward-the-future/ New Pointer Events spec normalizes touch and mouse Pointer Events builds on the DOM event model to offer a new way to handle input on the web, enabling developers to build touch-first experiences that work with mouse, pen, and other pointing devices as well…They are also designed from the ground up to allow modern browsers to accelerate the touch-surface performance, leading to a smoother user experience.

Slide 99

Slide 99 text

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

Slide 100

Slide 100 text

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

Slide 101

Slide 101 text

No content

Slide 102

Slide 102 text

Display density settings

Slide 103

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

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

Slide 105 text

Vimeo Couch Mode

Slide 106

Slide 106 text

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

Slide 107

Slide 107 text

http://www.flickr.com/photos/raver_mikey/504815463

Slide 108

Slide 108 text

Progressive Input?

Slide 109

Slide 109 text

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

Slide 110

Slide 110 text

Who are we to judge which input is better? http://www.flickr.com/photos/fensterbme/4783366926

Slide 111

Slide 111 text

We need to learn to adapt. http://www.flickr.com/photos/cdm/147947664/

Slide 112

Slide 112 text

So that’s the puzzle that has been haunting me. http://www.flickr.com/photos/sravishankar/3460495

Slide 113

Slide 113 text

http://www.flickr.com/photos/wwworks/1384952210

Slide 114

Slide 114 text

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