Engage users with questions
- If we need the user to confirm something in One UI, we ask them! Phrasing things like popups as questions makes users feel like they’re interacting with a person and makes choices clearer and easier to understand.
- We also use questions rhetorically in marketing phrases. This should be done sparingly, however, as multiple questions in a row can be overwhelming. So, we limit it to one.
Provide help, not limits
- If there’s a solution to a problem, we tell users what it is. This helps users avoid having to connect the dots between a limit and the action they need to take to overcome that limit.
- Above all else, we never blame users for errors, single them out, or make it seem like the restriction applies only to them. This style isn't user-friendly and may seem rude. For example, instead of saying "You can't delete this file," we say "This file can't be deleted."
Entice users to explore
- In One UI we leave a little intrigue in things like menus and functions. Rather than trying to fit all of the technical details in a menu subtext, we omit the subtext and let the user try the function or explore the menu.
- This also extends to tips and other prompts. We want to give users time to explore and discover rather than pushing them to try every feature the first time they open an app. They'll find the good stuff as they go.