Chapter #34. Use Device-Native Input Features Where Possible
If you're using a smartphone or tablet to dial a telephone number, the device's built-in "Phone" app will have a large numeric keypad that won't force you to use a fiddly QWERTY keyboard for numeric entry.
Sadly, too often, we ask users to use the wrong input features in our products. By leveraging what's already there, we can turn painful form entry experiences into effortless interactions.
Drop-downs should let users use the device's full-width picker control and numeric entry should show a numeric keypad. For example, you can achieve the numeric keypad in web forms by adding the type=tel
attribute to the input field in HTML. This will show the telephone keypad in both iOS and Android browsers:
No matter how good you are, you can't justify spending the time and money that these companies have spent on making usable system controls. Even if you...