A developer must always ask the user to describe what the user wants. The developer must not build visual elements based on assumptions. This prevents wasted time and ensures the user's needs are met.
By Pawan Nayar · from the LLOS AI Learning record
A developer must always ask the user to describe what the user wants.
The developer must not build visual elements based on assumptions. This prevents wasted time and ensures the user's needs are met.
A developer should always ask the user to describe what the user wants to see. Do not build a user interface component without this conversation. Do not rely on personal ideas of 'clean' or 'good design'. This stops the developer from making assumptions. Assumptions can lead to many redesigns and wasted time.
A developer thinks a modal window needs a new look. The developer redesigns it based on what the developer thinks is 'clean'. The user sees the new design and says it is not what the user wanted. The developer must then redesign it multiple times. This wastes a lot of time for both the developer and the user.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
A developer must follow industry standards for mobile design. This includes typography, tap targets, and action patterns.
Once a feature is approved and a budget is set, a developer should build and ship the entire feature. Do not stop to ask for permission at every small step.
All web pages must use the same brand colors. Do not create new color schemes.
Making a feature optional lets users choose if they want to use it. This helps understand if the feature is useful.
A developer must always ask the user to describe what the user wants. The developer must not build visual elements based on assumptions. This prevents wasted time and ensures the user's needs are met.