- There is no connection between form factor and input
- We can’t detect input until someone uses it
- Aiming for “touch” as the input is a good starting point
- Designing for user needs and usage works across form factors
For years, we treated the web as if it was a fixed canvas. It took the iPhone and Ethan Marcotte’s article on Responsive Web Design for us to realize how dynamic the UI could be.
But in addition to keyboards, we now have touch screens, cameras, voice control, and sensors as different kinds of inputs. Plus, we can’t know which inputs the user prefers to use until after we’ve tried designing with—and for—those inputs.
So how do we design for all of the explosion of these dynamic inputs?
There is no connection between form factor and input
We can’t detect input until someone uses it
Aiming for “touch” as the input is a good starting point
Designing for user needs and usage works across form factors
Remember when you got your first mobile phone? How you instantaneously became obsessed with the global potential of carrying such powerful connectivity right in your pocket?
OK, maybe that’s a bit strong. But it is exactly what Jason Grigsby felt when he bought his first mobile phone in 2000.
Since then, Jason has built a renowned career championing mobile design. He co-founded Cloud Four, a mobile design and development agency, and founded Mobile Portland to educate and support Portland’s mobile community. He also co-authored a book, Head First Mobile Web, and manages to energize everyone (including us!) whenever he speaks on the topic. Catch him on Twitter @grigs.