Surface pro comes with radio tip - pixel perfect accuracy, tilt, pressure, etc - input devices are not just mouse + touch

Touch matters: proliferation of touch devices (25% win 8 devices, smartphones, chromebook pixel)

Strategies: ignore/retrofit/design for touch Mouse emulation is often “good enough” to do nothing in some cases

Mouse: singular, touch: multiple

Recommends designing for touch 1st

Don’t use hover!

Sizing for touch (11mm avg human finger tip)

Ergonomics- think of position of user and environment

Touch hotspots - where will they naturally touch, reach of thumbs/ fingers Interaction areas: near edges. Reading areas: top/center

Pointer events capture all input device interactions

Poly fills: Hand.js Points.js

www: Modern.ie

www: docs.webplatform.org/PointerEvents

twitter: @joshholmes

JSConf 2013

This is a quick summary of a talk I attended at JSConf 2013. You can see a list of all those I've summarized notes from here. There's also a General thoughts during JSConf 2013 post for all the non-talk bits and pieces.

There were 3 concurrent tracks at the conference, so only those I attended myself are summarized here. Other attendees have summarized some of the talks I didn't get to due to scheduling conflicts - you can find those at jlongster.com (James Long) and Toby Ho's github repo.