Overview
A small product's first impression matters, but what makes people stay is found in moments they barely notice: a successful save, an understandable error, and a next step that does not need to be guessed.
Make the state visible
Users do not need to understand how a system works, but they do need to know what just happened. Button feedback, data timestamps, and the destination after an action should all be presented honestly.
Quiet does not mean silent. A good interface responds in time without turning every action into a notification that must be processed.
Respect interrupted use
Real use is often interrupted by phone calls, meetings, and other things. A product should preserve context as much as possible, so people can continue where they left off when they return.
It is a plain form of consideration, but it can greatly reduce the fatigue of having to start over.
Use words carefully
Every sentence in an interface helps build trust. Specific, short, and accurate explanations hold up better over repeated use than slogans that are enthusiastic but vague.