Designing better target sizes
This is a wonderfully in-depth interactive explainer on touch target sizes, with plenty of examples.
This is a wonderfully in-depth interactive explainer on touch target sizes, with plenty of examples.
Well now, this is a clever bit of hardware hacking.
Surfaces viewed from an angle tend to look shiny, and you can tell if a finger is touching the surface by checking if it’s touching its own reflection.
Jason breaks down the myths of inputs being tied to device form factors. Instead, given the inherent uncertainty around input, the only sensible approach is progressive enhancement.
Now is the time to experiment with new forms of web input. The key is to build a baseline input experience that works everywhere and then progressively enhance to take advantage of new capabilities of devices if they are available.
Some interesting outcomes from testing gov.uk with blind users of touchscreen devices:
Rather than reading out the hierarchy of the page, some of the users navigated by moving their finger around to ‘discover’ content.
This was really interesting - traditionally good structure for screen readers is about order and hierarchy. But for these users, the physical placement on the screen was also really important (just as it is for sighted users).
This solution to the mobile tap delay by the WebKit team sounds like what I was hoping for:
Putting
touch-action: manipulation;
on a clickable element makes WebKit consider touches that begin on the element only for the purposes of panning and pinching to zoom. This means WebKit does not consider double-tap gestures on the element, so single taps are dispatched immediately.
It would be nice to know whether this has been discussed with other browser makers or if it’s another proprietary addition.
A fantastic collection of short videos from Luke on interaction design for devices of all shapes and sizes.
Make yourself a nice cup of tea, hit “Play all”, sit back, relax and learn from the master.
I think Chrome is doing the right thing by removing the 300 millisecond tap delay on sites that set width=device-width — it’s certainly better than only doing it on sites that set user-scalable=no, which felt like rewarding bad behaviour.
Well, this is interesting: it looks like Chrome might stop waiting 300ms for potential double-tap-to-zoom events if the site is using a meta viewport declaration that sets the width to device-width.
A great piece by Jason analysing the ever-blurring lines between device classes.
Mind you, there is one question he doesn’t answer which would help clear up his framing of the situation. That question is:
What’s a web app?
Josh takes an-depth look at the navigation design implications of touch/keyboard hybrid devices, coming to a similar conclusion as Luke and Jason:
Unfortunately, the top-of-screen navigation and menus of traditional desktop layouts are outright hostile to hybrid ergonomics. Tried-and-true desktop conventions have to change to make room for fingers and thumbs.
Want to test for a hybrid device? Tough luck. Instead, argues Josh, the best you can do is assume that any device visiting your site could be touch-enabled.
Luke and Jason have done some excellent research (and put together some demos) into how the placement of navigation could be optimised for touch screens of all sizes. Turns out that the “standard” convention of having navigation along the top is far from ideal on a touch-enabled device.
The next time you make a sandwich, pay attention to your hands. Seriously! Notice the myriad little tricks your fingers have for manipulating the ingredients and the utensils and all the other objects involved in this enterprise. Then compare your experience to sliding around Pictures Under Glass.
The premise of this work is simple: I meet two or more people on the street who are strangers to each other, and to me. I ask them if they will pose for a photograph together with the stipulation that they must touch each other in some manner. Frequently, I instruct or coach the subjects how to touch. Just as often, I let their tentative physical exploration play out before my camera with no interference.
There are two things I’d like to see after watching this video:
Jonathan Stark's book is available online, in HTML, for free.
A timely reminder: don't hide information behind mouseover events.
A hands-on account of the new accessibility features in the iPhone. Sounds like a great experience.
Stevie Wonder talks about assistive technology. I think this finally proves that yes, accessibility *is* sexy!
If, like me, you were going cold turkey on Mobile Scrobbler after updating your jailbroken iPhone/iPod Touch, you can stop sweating now. The official Last.fm app is really, really nice ...and it's free.
A step-by-step guide to hacking your iPod Touch even if you've already upgraded to the new firmware.