UI design: responsibilities and practical exercise
UI design defines how an interface presents information and makes actions recognisable. It describes components, visual hierarchy and relevant states, including errors and missing content. The handover should let implementation reproduce these rules with real copy and multiple languages.
These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.
Design the same product sheet with a long name, an absent image and a selection error.
Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.
Inventorate the components and their variants before drawing the screens.
Set typography, spaces, contrast and hierarchy with real content.
Predict loading, lack of results, success and error.
Document the behavior on a narrow screen and the visible return of each action.
Deliverable and checks
Show the product page in normal, missing-selection and missing-image states using the same reference data. Supply typography, spacing and component rules, and annotate changes required on a narrow screen or with a longer name.
Implementation should identify the primary action and reproduce an error without inventing a new visual rule. Compare design and rendering with identical content; also check that colour is not the sole indication of an error or selection.
A model with only the ideal case does not describe how the interface works. Translated texts and incomplete content should also be reviewed.
Collaboration to explore: Web integration.
Fictional deliverable excerpt : The component has an explicit label, a visible focus state and a distinct message when no slot is available.
What passes between the roles : The task context, observed obstacles and content constraints inform interface proposals. The solution is then checked in use; a design alone does not establish that the obstacle has disappeared.
Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.
Sample excerpt
Component: search within a list.
Idle: visible label and empty field.
Results: matching count and items.
No results: explanation and a way to clear the filter.
Keyboard: visible focus on the field and button.
What the author should be able to explain
The specification states what changes and what remains available.
Returning to the full list has an explicit action.
An empty result is not presented as a technical fault.
Is a mock-up with three results sufficient?
It shows a favourable case. Handover also needs long content, no results, focus and small-screen behaviour. The demonstration below lets you inspect two of those states.
Another case to examine
A failure does not mean “no results”
Fictional case: a remote search fails while three old cards remain visible. Those cards do not establish the result of the new search.
For this exercise, document a failure state that preserves input, identifies previous results and offers recovery. Distinguish it from a genuine absence of matches.
Hand over the copy and expected actions for both states. The small local list below does not simulate network failure: this case needs a separate test with a controlled remote response.
Try a small filtered list
These three fictional entries show a result, an empty state and a return to the full list. Try “mobile”, then an absent word. No network request is made.
3 of 3 examples shown.
Images and alternativesPrepare an image and its description.
Mobile checksCheck a journey on a phone.
Writing a service pageClarify an offer and its scope.
For review: use the keyboard, test an accented word and check the count after clearing. This local list demonstrates neither server loading nor network failure. Input is not saved or sent.
Assess the quality of the work
Take an enquiry form with error, waiting and confirmation states and examine what actually changes for visitors. UI design quality depends on messages and states as much as initial appearance. For the exercise, use a long label and a translation: specifications should explain the component without requiring knowledge of the original mock-up.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
Assess the quality of the work
Skill
Evidence to examine
Failure to spot
Understandable error
Provide the field label, useful help and a message associated with a specific error. Describe focus visibility and information retained after correction.
The state relies only on a red border, or “invalid” does not explain what to correct or how to locate the affected field.
Content and adaptation
Present the component with enlarged text, a long translation and an absent value. Describe behavior when elements wrap onto multiple lines.
The button disappears, a message is truncated or container dimensions require removing information essential to the decision.
Handover
Behaviours, spacing and decisions can be identified.
The design shows an effect without defining its trigger.
Component states
Prepare default, focus, error, pending and unavailable states with labels and long content.
The implementer can understand the intended behaviour, including without hover.
A focused next step
Have one component implemented from the specifications, then compare its error state and narrow layout with the mock-up. Identify what the implementer had to guess. Resolve behavioral ambiguity before multiplying the component’s visual variants.
Language and reading direction are separate information. Declaring ar alone does not establish the base direction; dir="rtl" does. Logical CSS properties adapt spacing without hard-coding left and right throughout the layout.
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
A review case to reproduce
The button state remains ambiguous
Situation to examine
A button changes colour after activation, but wording and interface do not show whether the action is pending, successful or failed.
Proposed check
Design normal, pending, success and error states for the same action. Check text, legibility and focus. Review meaning without colour and have another person interpret the messages.
Evidence to retain
A state table records trigger, visible response and recovery. Important outcomes are not communicated by colour alone.
Fictional finding example
Four states of one button: “Send”, “Sending”, “Enquiry recorded”, “Failed: try again”. The first mock-up distinguished them only by colour.
Interpret this outcome
Specify wording, trigger and recovery for each state. A green colour proves neither storage nor reading of the enquiry.
Three complementary checks
Fictional cases: adapt these expectations to your test contract and retain the limits of the check.
1Identifiable trigger
2Understandable state
3Available recovery
Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.
Scenario variations and expected evidence
Variation to test
Expected result in this case
Evidence to hand over
Submission remains pending
Announce waiting without displaying success
Text, trigger and available control
A field is rejected
Associate the error with that field
Designed state and correction route
The result is confirmed
Display a state matching the confirmation
Message-to-event correspondence
Decision to hand over : The handover describes each state and recovery path beyond the button colour.
Extended exercise: Design the statements of an application form, from the first entry to the receiving message. Plan the keyboard focus, an invalid field, an ongoing sending and a connection error. Work with realistic content and longer translation. Describe the role of each color and icon: essential information must also be expressed by text. The result to be delivered is a consistent state system, not just a capture of the empty form.
What to deliver with your work
Components and variants necessary for the course
Statement texts, errors and confirmations
Spacing and typographic hierarchy rules
Annotations for integration and behaviors
Acceptance criteria
These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.
All important states have a defined text and behavior.
The visible focus remains identifiable on each background.
The layout accepts a long translation without hiding an action.
An error does not depend only on the color or an icon.
Deliver the components with their states, texts and constraints. Indicate what falls under a general rule and what responds to a particular case. Discuss behaviors with the person who integrates the interface, then check the result in the browser. A static mockup does not alone prove that the form is usable on the keyboard or that its errors are correctly announced.
Compare changes to an individual screen with changes to shared components. Choose according to how often the problem occurs and which pages use the same elements.
Correction of a representative screen
When to choose it
Suitable for clarifying hierarchy or a form. Define the main task and required states before adjusting colours and spacing.
What to plan for
Include errors, loading states and long content. An ideal screenshot cannot show whether the interface remains understandable with real data.
Documented reusable component
When to choose it
Useful when the same need occurs across workflows. Specify structure, variants, states and conditions of use.
What to plan for
Check translations, keyboard use and small screens. Explain limitations to avoid extra variants being invented by each team.
A risk to anticipate
Contrast and font sizes alone do not establish accessibility. Check labels, states, relationships and interactions in the implemented interface.
How to decide
Show the screen before and after using the same task and content. Check that the improvement remains consistent on a second page.
Compare components, error states, narrow screens and long text. A mock-up image differs from a documented library ready for implementation.
Recurring operation
Define component upkeep and new requirements. Separate planned fixes from new variants; a design-tool licence does not cover recurring design work.
Exit and handover
Plan editable sources, usage rules and permitted assets. Check that the next team can modify components without relying on a contributor’s personal account.
For a form, show input, focus, error, pending and confirmation states. For a list, add no results and long content. Explain wording and behaviour: colour alone does not describe an error, and a static mock-up does not prove keyboard operation.
How should a component be handed to developers?
Include its purpose, variants, real content and state changes. Distinguish navigation from an action and agree how focus behaves. Review an example with a long label and an error before reusing the component across pages.
When should a new component variant be created?
When an identified need cannot be met without making the existing use ambiguous. Document the difference and affected states. An isolated aesthetic preference does not justify a variant that is difficult to maintain across pages.