Designing user-friendly interfaces that feel obvious
UX principles I use as an engineer to build interfaces people never have to think about, on mobile, on the web and on any screen in between.
Maher Jaafar
· 2 min read
A user-friendly interface is one people never have to think about. That is easy to say and hard to build. As an engineer who has built Flutter apps for phones, tablets and larger touch screens, as well as web products, these are the principles I rely on.
Design for the real context
A phone is used on the sofa, on the bus, with one thumb. A tablet might sit on a desk; a web app is used with a mouse and keyboard, often in a hurry between meetings. Before choosing layouts and sizes, ask: where is this person, what are they doing with their hands, and how much attention do they have to spare?
Less attention means bigger touch targets, higher contrast, fewer choices per screen and information that can be read at a glance.
One primary action per screen
Every screen should have one obvious thing to do next. Secondary actions can exist, but they should look secondary. If everything is highlighted, nothing is.
Feedback for every action
Every tap should produce an immediate response: a pressed state, a transition, a loading indicator, a confirmation. Silence makes users tap again, and that is how duplicate orders and double submissions happen.
Make errors human
"Error 500" helps nobody. A good error message says what happened, why, and what the user can do next. Even better: prevent the error with good defaults, validation as you type and disabled states that explain themselves.
Speed is a UX feature
A beautiful interface that stutters feels broken. In Flutter that means keeping build methods cheap, avoiding unnecessary rebuilds, using const widgets, and profiling on real mid-range devices, not just the newest phone on your desk.
Consistency beats creativity
Use the same patterns for the same things: the same button styles, the same navigation, the same wording. A small design system, even just a set of shared widgets and tokens, makes an app feel solid and makes the team faster.
Accessibility is not optional
Text that scales, enough contrast, labels for screen readers, touch targets of at least 48 pixels. Accessible interfaces are better for everyone, including the person using your app in bright sunlight or with tired eyes at the end of the day.
Test with real people early
Five users trying a rough prototype will teach you more than weeks of internal debate. Watch where they hesitate. Don't explain anything. The moment you need to explain the interface, you have found something to fix.
The engineer's role in UX
Designers own the vision, but engineers decide how it feels: the timing of animations, the loading states, the edge cases nobody drew. Caring about those details is one of the most visible things an engineer can do for a product.