- Embrace Typical Processes Instead of Screens
- Leverage Computers Instead of Serving Them
- Adapt to Individuals
Embrace Typical Processes Instead of Screens
Too often the gut reaction to solving a problem is to slap a screen based interface on it. Instead we should take a step back, look at the typical process and see if there's a better way of solving the problem.
Example: Creating an app to unlock a car door. It doesn't improve anything but only makes something simple more complicated. Instead the app might notice that you're very close to your car and unlocks the doors without any user interaction required.
Leverage Computers Instead of Serving Them
No UI is about machines helping us, instead of us adapting for computers.
Too often computers behaves like spoiled children, craving our attention and our constant input through input fields and buttons. Instead they should use sensors and API's to collect data about us and our use and support us in that.
Example: Form validation. "Phone numbers must only include numbers". Why can't computers simply handle that internally instead of burdening the user with removing dashes and spaces.
Adapt to Individuals
We should create systems that learn from users behaviour and adapt accordingly.
Example: The Nest thermostat learns what temperatures are suitable at different times and different circumstances.