Created
August 12, 2015 10:02
-
-
Save vedranjaic/533772598b66b2255814 to your computer and use it in GitHub Desktop.
A checklist for designing mobile input fields
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Should it be there at all | |
1. Is this field absolutely necessary? | |
Description | |
2. Is the label above it? (Not inside, not below) | |
3. Is the field marked as required (*) or optional? | |
4. Have you removed any placeholder from inside the field? | |
Visibility | |
5. Is the field big enough so that most possible field values are visible? | |
6. Is the field visible in both orientations when the keyboard is displayed? | |
Filling it in for the user | |
7. Do you have any good defaults for this field? | |
- Any history available? | |
- Frequently used values? | |
8. Can you use the phone features (camera, GPS, voice, contacts ) to populate it? | |
9. Can you compute it for the user based on other info (e.g., state based on zip code, coupon field)? | |
Typing | |
10. Do you support copy & paste into the field? | |
11. What is the right keyboard for this field? | |
12. Can you make suggestions/autocomplete based on the first letters typed? | |
- Do not autocorrect for names, addresses and email addresses. | |
13. Do you allow typos or abbreviations? | |
14. Do you allow users to enter it in whatever format they like? (e.g., phone numbers credit cards) | |
- You can autoformat it for them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment