#User-Interface
5 notas · última:
How to write a great error message
The article argues that good error messages are clear, specific, actionable, and written in plain language. It criticizes vague alerts, unnecessary interruptions, and defaults that could be handled without modal dialogs.
How to build complex user interfaces without going completely insane
The article recommends delaying state updates in dialogs, separating model data from UI state, and favoring integration tests over unit tests when building complex web interfaces.
The Hamburger Menu Doesn't Work
The article argues that hamburger menus hide navigation, weaken information scent, and often perform poorly on mobile, with better results coming from visible tab bars or other explicit navigation.
UI is visible. Type is visible.
The page argues that typography should not always disappear. Legibility is a baseline, but type can also be overt, expressive, and appropriate to the content and context.
Part 7 - Special Considerations
The page advises against dynamic code generation in shared code and against reusing the same UI design across iOS, Android, and Windows Phone. Xamarin apps should follow each platform’s native constraints and familiar UI metaphors.