Collecting information on a phone.
WHY IT MATTERS
Typing on a phone is slow and error-prone, and forms are where users abandon.
WHAT TO DO FIRST
Ask for less.
WHAT TO SET FOR EVERY FIELD
The appropriate keyboard type The appropriate autocomplete hint Capitalisation and correction behaviour
WHY THE AUTOCOMPLETE HINTS
They allow the system to fill names, addresses, and one-time codes automatically.
WHAT THAT SAVES
Substantial typing, and errors.
WHAT TO AVOID
Placeholder text as a label Fields that clear on error Forms that lose input when the application is backgrounded Validation that fires while typing
WHAT TO DO ABOUT KEYBOARDS
Ensure the focused field is not hidden behind it.
WHY
It is one of the commonest mobile interface faults.
WHAT TO DO ABOUT LONG FORMS
Split them into steps, save progress, and show where the user is.
WHAT TO ALLOW
Pasting, everywhere, including verification codes.
WHAT TO PRESERVE
Everything entered, on any error or interruption.
WHAT TO TEST
Completing the form with an interruption partway.
