the immobile web

178
e Immobile Web Jason Grigsby • @grigs • cloudfour.com Slides: bit.ly/immobilism

Upload: jason-grigsby

Post on 15-Jan-2015

17.623 views

Category:

Technology


5 download

DESCRIPTION

Presented at Mobilism.nlDevice diversity is about to get an order of magnitude worse. SmartTVs are hitting the market in mass this year. Sony, LG, Vizio, and Samsung are all shipping televisions with Google TV built in.And if the rumors that Apple will release a TV this year are true, 2012 will turn out to be the year web developers start to tackle the glass screen hanging on our walls.Why should web developers focused on mobile learn about the web on TVs? Because TVs represent the next challenge in device proliferation. They share common characteristics with their smaller brethren. They create new challenges and opportunities we haven't encountered yet. And most importantly, learning how to build for TVs helps inform our practices of building for mobile devices.

TRANSCRIPT

Page 1: The Immobile Web

!e Immobile Web

Jason Grigsby • @grigs • cloudfour.comSlides: bit.ly/immobilism

Page 2: The Immobile Web

Follow along

Tweets:@grigsSlides: bit.ly/immobilism

http://www.flickr.com/photos/stevegarfield/4247757731/

Page 3: The Immobile Web
Page 5: The Immobile Web

Photo by Alan Light http://www.flickr.com/photos/alan-light/216012860/

Page 6: The Immobile Web
Page 7: The Immobile Web
Page 8: The Immobile Web

Image source: http://gigaom.com/video/99-dollar-logitech-revue-worth-buying/

Page 9: The Immobile Web

Vimeo on Google TV

Page 10: The Immobile Web

Woah… it’s just a web page?

Page 11: The Immobile Web

View in Couch Mode

Page 12: The Immobile Web

If there is a coming zombie apocalypse of devices…

http://www.flickr.com/photos/adactio/6301799843

Page 13: The Immobile Web

then TVs are likely the next wave.http://www.flickr.com/photos/athena1970/3935208655/

Page 14: The Immobile Web

consumes 32.7% of peak downstream traffic in U.S.

Page 15: The Immobile Web

Big enough to get its own button.

Page 17: The Immobile Web
Page 18: The Immobile Web

http://www.flickr.com/photos/acaben/541334636/

“I "nally cracked it.”

Page 19: The Immobile Web
Page 20: The Immobile Web
Page 21: The Immobile Web
Page 22: The Immobile Web
Page 25: The Immobile Web

#e current Apple TV doesn’t have a browser…

Page 27: The Immobile Web

[People] “don’t want a computer on their TV,” Apple CEO Steve Jobs said today. “#ey have computers. #ey go to their wide-screen TVs for entertainment. Not to have another computer. #is is a hard one for people in the computer industry to understand, but it's really easy for consumers to understand. #ey get it.”

http://www.flickr.com/photos/acaben/541334636/

Page 28: The Immobile Web

And so, it turns out people want keyboards. I mean, when I started in this business one of the biggest challenges was that people couldn’t type.…

And if you do email of any volume, you gotta have a keyboard. So we look at the tablet and we think it’s gonna fail.

—Steve Jobs, 2003

http://www.flickr.com/photos/acaben/541334636/

Page 29: The Immobile Web

Big opportunity is an App Store on Apple TV.

Page 30: The Immobile Web
Page 31: The Immobile Web

Major Brands Using Combo of Web and Native

Page 32: The Immobile Web

Even Apple uses embedded webviews

Page 33: The Immobile Web
Page 34: The Immobile Web
Page 36: The Immobile Web

Apps =

http://www.flickr.com/photos/34818713@N00/1314251273/

Embedded Web Views =

Page 37: The Immobile Web

Apps =

http://www.flickr.com/photos/34818713@N00/1314251273/

Embedded Web Views = 3rd Party Browsers

Page 38: The Immobile Web

Apps =

If that is true, don’t you think Apple will ship Safari?http://www.flickr.com/photos/34818713@N00/1314251273/

Embedded Web Views = 3rd Party Browsers

Page 39: The Immobile Web

“By the summer of 2012, the majority of the televisions you see in stores will have Google TV embedded in it”

Photo by JD Lasica/Socialmedia.bizhttp://www.flickr.com/photos/jdlasica/5181380514/

Page 40: The Immobile Web

?!?!

Page 41: The Immobile Web
Page 42: The Immobile Web

Samsung 23.6%

Vizio 15.4%

LG Electronics 12.4%

Sony 8.0%

Toshiba 7.8%

Others 32.8%

Q4 2011 US LCD TV Market Share

Page 43: The Immobile Web

Samsung 23.6%

Vizio 15.4%

LG Electronics 12.4%

Sony 8.0%

Toshiba 7.8%

Others 32.8%

Q4 2011 US LCD TV Market Share

Page 44: The Immobile Web

Samsung 23.6%

Vizio 15.4%

LG Electronics 12.4%

Sony 8.0%

Toshiba 7.8%

Others 32.8%

Q4 2011 US LCD TV Market Share

Page 45: The Immobile Web

Samsung 23.6%

Vizio 15.4%

LG Electronics 12.4%

Sony 8.0%

Toshiba 7.8%

Others 32.8%

Q4 2011 US LCD TV Market Share

?

Page 46: The Immobile Web
Page 47: The Immobile Web
Page 48: The Immobile Web

=

Page 49: The Immobile Web

=

Page 50: The Immobile Web

http://www.unwiredview.com/2011/12/21/andy-rubin-%E2%80%9Candroid-daily-activations-top-700k-a-day%E2%80%9D-on-the-way-to-1-million-a-day-in-q2-2012/

Will Google TV follow Android’s path?

Page 51: The Immobile Web

Considering TVs helps inform how we build for mobile.

http://www.flickr.com/photos/revdancatt/3789612273/

Page 52: The Immobile Web

And can help us avoid short-sighted solutions

http://www.flickr.com/photos/pss/4876189045/

Page 53: The Immobile Web

So let’s dig in shall we?

Page 54: The Immobile Web

First, the good news.

Page 55: The Immobile Web

Surprisingly good browsers in newer TVs.

Page 56: The Immobile Web

Year Brand Model Score Bonus Points Notes

2011 LG 60PZ950 221 6

2011 Sony KDL55HX729 222 6

2011 Sony NSZ-GT1 343 8 Google TV v3.2

2012 LG 47LS5700 302 8

2012 LG 55LM62BND1 302 8

2012 Sharp LC80LE844 281 0

2012 Samsung UN55ES6100 229 2

2012 Samsung UN55ES8000 244 2

2012 Sony KDL55HX750 267 6

2012 iPhone 4S 305 9 Running iOS 5.1

2012 Google Chrome 378 13 Chrome 18 on Mac

html5test.com

Total possible points: 475

Page 57: The Immobile Web

• backgroundsize

• borderimage

• borderradius

• boxshadow

• canvas

• canvastext

• csstransforms

• csstransitions

• fontface

• generatedcontent

• hashchange

• hsla

• input:autofocus

• input:max

• input:min

• input:pattern

• input:required

• input:step

• multiplebgs

• opacity

• postmessage

• rgba

• sessionstorage

• smil

• svg

• svgclippaths

• textshadow

100% of Smart TVs tested support

Page 58: The Immobile Web

• localstorage

• applicationcache

• csscolumns

• cssgradients

• history

• input:multiple

• input:placeholder

• inputtypes:email

• inputtypes:number

• inputtypes:search

• inputtypes:tel

• inputtypes:url

• webworkers

• audio:m4a

• audio:mp3

• cssanimations

• cssre!ections

• draganddrop

• !exbox-legacy

• inputtypes:range

• video:h264

• websqldatabase

70% or more support

Page 59: The Immobile Web

• websockets

• inlinesvg

• inputtypes:date

• inputtypes:datetime

• inputtypes:datetime-local

• inputtypes:month

• inputtypes:time

• inputtypes:week

• input:autocomplete

• input:list

• geolocation

• indexeddb

• inputtypes:color

• audio:wav

• webgl

• audio:ogg

• csstransforms3d

• !exbox

• touch

• video:ogg

• video:webm

• audio*

• video*

Poor support for the following

*!is has to be a mistake.

Page 60: The Immobile Web

More importantly, the 2012 models are much faster.

Page 61: The Immobile Web

More importantly, the 2012 models are much faster.

(How fast remains a secret. No one publishes CPU speeds.)

Page 62: The Immobile Web

So what’s it like to use these TVs?

Page 64: The Immobile Web

#e biggest problem is input.

Page 65: The Immobile Web

Welcome back T9. We’ve missed you.

Page 66: The Immobile Web
Page 67: The Immobile Web
Page 68: The Immobile Web

Which is why you see remotes like this

Page 69: The Immobile Web

Apple hasn’t solved this problem either

Page 70: The Immobile Web

Apple’s iOS Remote App Makes Life Bearable

Page 71: The Immobile Web

Nearly every manufacturer has their own apps now.

Page 72: The Immobile Web

Nearly every manufacturer has their own apps now.

Page 73: The Immobile Web

Nearly every manufacturer has their own apps now.

Page 74: The Immobile Web

One of the core lessons:Multi-screen world.

It’s a multi-screen world.

http://www.flickr.com/photos/marcof/5139160297/

Page 75: The Immobile Web

How does the web play in this new world?

Page 76: The Immobile Web

Two main methods of input on these TVs.(Other than linked apps)

Page 77: The Immobile Web

D-pads

Page 79: The Immobile Web

When done properly, D-Pad works very well.

(Free Opera TV SDK Emulator!)

Page 80: The Immobile Web

When done properly, D-Pad works very well.

(Free Opera TV SDK Emulator!)

Page 81: The Immobile Web

But when D-pads control on-screen pointers… Yuck!

Page 82: The Immobile Web

Pointers work well with on screen cursors, but are harder to use

precisely. Easy to miss your target.

Well implemented D-pad is faster.

Page 83: The Immobile Web

Plenty of experiments.

Page 84: The Immobile Web
Page 85: The Immobile Web

Touchpads integrated into remotes

Page 86: The Immobile Web

Voice control?

Page 87: The Immobile Web

Gesture Controls?

Page 88: The Immobile Web

Eventually something will stick, right?

Page 89: The Immobile Web

#e TV Context

http://www.flickr.com/photos/imnohero/2330548144

Page 90: The Immobile Web

#e TV Context

Yes, I said “Context.”http://www.flickr.com/photos/imnohero/2330548144

Page 91: The Immobile Web

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

Our vision of mobile context is often wrong.

Page 92: The Immobile Web

80% during misc downtime

76% while waiting in lines

62% while watching TV

69% for point of sale research

http://www.flickr.com/photos/missmeng/5327470961

Page 93: The Immobile Web

TMI: 39% use phone on the toilet.

Page 94: The Immobile Web

Yes, we can’t know the mobile context.

http://www.flickr.com/photos/timcaynes/158599960/

Page 95: The Immobile Web

But when it comes to TVs,

context seems to matter again.http://www.flickr.com/photos/imnohero/2330548144

Page 96: The Immobile Web

Two great sources for information on designing for TVs.

Page 99: The Immobile Web

http://www.flickr.com/photos/chrisbartow/5835428673

Designing for a 10-foot UI

Page 100: The Immobile Web

• Limit paragraphs to 90 words

• Break into small chunks

• Line length: 5-7 words

• Body text around 21pt on 720p and 28pt on 1080p

• Add more leading

• Minimum font size of 22px

• Line length: 10 words or less

• Generous leading

Making text easy to read

Google Opera

Page 101: The Immobile Web
Page 102: The Immobile Web

“A good rule of thumb is to increase the size of an element (such as an image or font) 1.5x for 720p and 2.0x for 1080p relative to the size of that element in a normal PC browser experience.”

—Google TV Guide

Page 103: The Immobile Web

• When designing a web page for TV, the viewable area should display less information overall, and what's there should focus on a con"ned set of tasks (even consider performing their desired task automatically or select by default).

• Primary activity often revolves around quick information look-up (for instance, cast and crew details for a particular movie, weather reports, TV listings) and quick access to services. Web content for TV should therefore be optimised — in terms of overall presentation, navigation and functionality — and task-focused, giving quick and clear access to all relevant features and information.

Optimize for tasks

Google Opera

Page 104: The Immobile Web
Page 105: The Immobile Web

Hover is back!

Page 106: The Immobile Web

“!e main interface of Google TV encourages the use of the D-pad on the remote to make selections on a screen -- it's likely that users will keep this habit even on the web.”

Page 107: The Immobile Web

/* CSS */#copyright { nav-down: #logo;}

CSS3 Basic User Interface speci"cation for directional focus navigation

http://dev.opera.com/articles/view/tweaking-spatial-navigation-for-tv-browsing/

Page 108: The Immobile Web

button#b1 { nav-index:1; nav-right:#b2; nav-left:#b4; nav-down:#b2; nav-up:#b4;}

button#b2 { nav-index:2; nav-right:#b3; nav-left:#b1; nav-down:#b3; nav-up:#b1;}

W3C’s example of four buttons

button#b3 { nav-index:3; nav-right:#b4; nav-left:#b2; nav-down:#b4; nav-up:#b2;}button#b4 { nav-index:4; nav-right:#b1; nav-left:#b3; nav-down:#b1; nav-up:#b3;}

http://www.w3.org/TR/css3-ui/#nav-dir

Page 109: The Immobile Web

Unfortunately, only 2 of the 10 TVs I tested supported spatial navigation.

Page 110: The Immobile Web

Google TV jQuery UI Library

http://code.google.com/p/gtv-resources/

Page 111: The Immobile Web

Unfortunately, I had trouble getting the Google TV jQuery UI library to work on non-Google TVs.

Needs more testing.

Page 112: The Immobile Web

Both solutions require adding a layer of CSS or JS speci"cally to support TV interaction.

Page 113: The Immobile Web

• Google TV may not be able to render a page as quickly as your workstation.

Performance Challenges

Google Opera• Modest hardware. Somewhere

between high-end smart phones and low end laptops.

• Avoid overly heavy and complex JavaScript.

• Avoid layering and opacity.

• Low limit on caching. Cannot assume assets cached. Cannot rely on cookies for subsequent session.

Page 114: The Immobile Web

http://thereisnofold.com/

Uh oh… scrolling sucks on many TVs.

Page 115: The Immobile Web

Horizontal paging is preferred

http://gtv-resources.googlecode.com/svn/trunk/gtv-jquery-demo/index.html

Page 116: The Immobile Web

• Only HDTVs.

• 720p and 1080i/p

• "e exact pixel dimensions of the display varies by TV manufacturer.

• Provides an auto-zoom feature which you need to design for or around.

Supporting different screen resolutions

Google Opera• Most modern web-enabled

TVs support 1280×720 as a minimum resolution.

• 720p content is usually upscaled

• Virtual resolutions — as an example, the Nintendo Wii has a virtual width of 800 pixels. Height varies based on the type of TV (4:3 or 16:9 aspect ratio) and user settings.

Page 117: The Immobile Web

Browserscope report screen sizes

Actual resolutions differ greatly.

Page 118: The Immobile Web
Page 119: The Immobile Web

No problem. We’ll adapt to the screen resolution.

http://bradfrostweb.com/blog/web/mobile-first-responsive-web-design/

Page 120: The Immobile Web

No problem. We’ll adapt to the screen resolution.

http://bradfrostweb.com/blog/web/mobile-first-responsive-web-design/

Page 121: The Immobile Web
Page 122: The Immobile Web

HDTV!

Page 123: The Immobile Web

No worries. We’ll use media type.<link rel="stylesheet" media="screen" href="..."><link rel="stylesheet" media="tv" href="...">

Page 124: The Immobile Web

None of the TVs supported the TV media type.

Page 125: The Immobile Web

https://twitter.com/#!/patrick_h_lauke/status/190078528568569856https://twitter.com/#!/patrick_h_lauke/status/190078688287653889

Media types are useless except for screen and print.

Page 126: The Immobile Web

Web developers are litter bugs.

http://www.flickr.com/photos/jpdaigle/3393858438/

Page 127: The Immobile Web
Page 128: The Immobile Web

Sympathy for the Browser Makers

Page 129: The Immobile Web

We need to be careful of the impact we have on the world.

http://www.flickr.com/photos/samout3/3411361042/

Page 130: The Immobile Web

Detect a TV with JavaScript?

Page 131: The Immobile Web

Detect a TV with JavaScript?

Nope.

Page 132: The Immobile Web

http://www.flickr.com/photos/77799978@N00/5351372848/

Alright "ne.We’ll use device

detection.

Page 133: The Immobile Web

Mozilla/5.0 (DirectFB; Linux; ko-KR) AppleWebKit/534.26+ (KHTML, like Gecko) Version/5.0 Safari/534.26+

User Agent String for a 2012 LG Smart TV

Page 134: The Immobile Web

Mozilla/5.0 (DirectFB; Linux; ko-KR) AppleWebKit/534.26+ (KHTML, like Gecko) Version/5.0 Safari/534.26+

User Agent String for a 2012 LG Smart TV

Nothing we can use in that string!

Page 135: The Immobile Web

#at sucks.

http://www.flickr.com/photos/plunkmasterknows/357836855/

Page 136: The Immobile Web

What’s the solution?I don’t see many people actively working on it.

Page 137: The Immobile Web

Are Smart TVs the equivalent of phones before the iPhone was released?

http://www.flickr.com/photos/rhodes/6297487639/

Page 138: The Immobile Web

Are Smart TVs the equivalent of phones before the iPhone was released?

#is gives me hope.http://www.flickr.com/photos/rhodes/6297487639/

Page 139: The Immobile Web

Responsive web design still makes sense.

Page 140: The Immobile Web

Choosing responsiveness, as a characteristic shouldn’t necessarily de"ne the wider implementation approach. Device Experiences (i.e. standalone sites, aimed at a group of devices) can also be responsive, providing the %exibility to support a much wider range of devices.

—Stephanie Rieger

Page 141: The Immobile Web

ARTICLES TOPICS ABOUT CONTACT CONTRIBUTE FEED

D E C E M B E R 14, 2010

Smartphone Browser Landscapeby P E T E R - P A U L K O C H

Published in: User Interface Design, Mobile, Mobile Design, Mobile Development

Discuss this article » | Share this article »

Users expect websites to work on their mobile phones. In two to three years, mobile support

will become standard for any site. Web developers must add mobile web development to their

skill set or risk losing clients.

How do you make websites mobile compatible? The answer is obvious: By testing them on all

mobile phones, and by solving the problems you encounter. But, that’s a useless answer. It’s

impossible to test your designs on every mobile phone out there. Within the mobile phone

landscape, there are at least ten operating systems (OSs) and fifteen browsers that require

consideration. Mobile devices are expensive, and not every web developer can afford to buy

five to ten of them. Testing “on all mobile phones” is impossible for most web developers.

In this article, I’ll give you an overview of the mobile web market, as well as phone platforms

and their browsers, so that you can decide which mobile devices to test on. Then, we’ll look at

how to set up a mobile test bed.

Search ALA

include discussions

TopicsCode

Content

Culture

Design

Mobile

Process

User Science

SnapshotMost web designers and

developers (not to

mention the entire

blogosphere) fall

squarely in the high-end

market. A cultural bias

exists against OSs aimed

at any other market. As

a result, most people

focus on the struggle

between iOS and

Android, and ignore the

rest. This has to change.

Stay in better touch withcustomers with

No.

320

Page 142: The Immobile Web

“Testing on as many devices as possible is a great idea in theory, but in practice it is untenable. Even if we buy a few devices to try to cover more ground, they will be outdated in just a few months or a year at most. So are we supposed to buy multiple devices per year?”posted at 11:32 am on December 14, 2010 by klayon

“If that’s the mobile landscape, I want no part of it.”posted at 07:22 am on December 15, 2010 by Polsonby

http://www.alistapart.com/comments/smartphone-browser-landscape/

Page 143: The Immobile Web

If you thought phones were bad,You ain’t seen nothing yet!

Page 144: The Immobile Web

Most stores have no remotes and no wi-"

http://www.flickr.com/photos/elmada/1431918753/

Page 145: The Immobile Web

Bring your phone for tethering to TVs

http://www.flickr.com/photos/bendodson/3367856091/

Page 146: The Immobile Web

Don’t be surprised if your data gets used…

Page 147: The Immobile Web

What are people actually expecting when they buy a smart tv?

http://www.flickr.com/photos/presta/623444414/

Page 148: The Immobile Web

Storage capacity not listed as a spec.

Page 149: The Immobile Web

Is there a Smart TV market?

Page 150: The Immobile Web

Opera TV Emulator

http://www.opera.com/business/tv/emulator/

Page 151: The Immobile Web
Page 152: The Immobile Web

Google TV Emulator

https://developers.google.com/tv/android/docs/gtv_emulator

Page 153: The Immobile Web

Google TV Spotlight in Chrome Fullscreen

http://www.google.com/tv/spotlight-gallery.html

Page 154: The Immobile Web

Google TV Spotlight in Chrome Fullscreen

http://www.google.com/tv/spotlight-gallery.html

Page 155: The Immobile Web

What lessons can we take away from TVs?

Page 156: The Immobile Web

320 px

Too much focus on the smaller screen.

Page 157: The Immobile Web

Why do we need to look at our phones to get directions?

One vibration for left.Two for right.

http://www.flickr.com/photos/williamhook/4225307113

Page 158: The Immobile Web

TV resolution reinforces this idea1980 px

1080

px

This is HDTV

Page 159: The Immobile Web

It may be multiple screens interacting together.

Need to think about multiple screens.

http://www.apple.com/ipad/features/

Page 160: The Immobile Web

It may be multiple screens interacting together.

Need to think about multiple screens.

http://www.apple.com/ipad/features/

Page 161: The Immobile Web

What does TV tell us about context?

Page 162: The Immobile Web

No context Context?

What does TV tell us about context?

Page 163: The Immobile Web

Or is TV context different simply because we’re still in the feature phone era of Smart TVs?

http://www.flickr.com/photos/rhodes/6297487639/

Page 164: The Immobile Web

Net%ix: posture de"ning different experienceshttp://www.%ickr.com/photos/ezu/66815736/

Page 165: The Immobile Web

“Some people at Net%ix have been arguing for a single experience across all devices. #is has never born out in any kind of testing. Instead, Net%ix has a variety of experiences on different devices and even regions.”

http://www.lukew.com/ff/entry.asp?1339

Page 166: The Immobile Web

• User posture: Stationary, Lean back, on-the-go, shared

• Input capabilities: pointer/keyboard, LRUD/OSK, Gesture/OSK

• Navigation style: controls & windows, panes

• Display capabilities: Hi-Res, near, far away, small, medium, large

•"ese constraints are really powerful. You need to embrace them to get to appropriate designs.

http://www.lukew.com/ff/entry.asp?1339

Page 167: The Immobile Web

When we need more control to craft an experience for a given device, how can we do so in a sustainable manner?

Page 168: The Immobile Web

http://www.flickr.com/photos/nathaninsandiego/4829858186/

Yes, Smart TVs suck right now.

Page 169: The Immobile Web

But it would be dangerous to dismiss them.

Page 170: The Immobile Web
Page 171: The Immobile Web
Page 172: The Immobile Web

Fundamental Truth:We can’t predict future behavior from

a current experience that sucks.

Page 173: The Immobile Web

So even if we don’t have to design for

TVs today…

Page 174: The Immobile Web

It behooves us to start thinking about and planning for what it will be like to do so…

Page 175: The Immobile Web

Flickr photo by Drift Words: http://www.flickr.com/photos/44124413076@N01/11846265/

So we won’t build solutions for today’s problems and

then "nd ourselves surprised by what comes next.

Page 176: The Immobile Web
Page 177: The Immobile Web

Jason Grigsby @grigs • cloudfour.comSlides: bit.ly/immobilism

!ank You!Special thanks to Patrick H. Lauke, the Google TV team, Flickr users sharing under creative commons & the kind

folks at Beaverton Video Only.

http://www.flickr.com/photos/sualk61/4083223760/

Page 178: The Immobile Web

Get 40% off of the print and 50% off of ebook version using code AUTHD at oreilly.com.

OR Amazon link (no code): http://bit.ly/hf-mw