Services
Choose the scope that matches the question you need to answer.
Layouts that work with the content, from a narrow phone screen to a larger display. Navigation, headings, images and forms need a clear hierarchy at each size.
A brief should identify the page types, content owner, existing brand material and editing or hosting environment. A static presentation and a connected application have different requirements; integrations, deployment and maintenance are agreed explicitly.
Discuss a similar brief ↗Working browser examples make states and transitions easier to discuss. A prototype can explore the effect of a filter, the order of a short flow or the relationship between a control and its feedback.
The prototype scope should say which controls work, what sample data is used and which operations are simulated. A demonstration does not supply authentication, a database or security validation. Real service behaviour needs its own implementation and acceptance checks.
Discuss a similar brief ↗A small, coherent set of components can make repeated pages easier to understand. Labels, spacing, type hierarchy, buttons and feedback states need rules that remain useful in different contexts.
The work can define patterns and example compositions for an agreed application. Accessibility expectations, target browsers, content variants and handover formats belong in the brief. A component set is reviewed against real screens rather than treated as a guarantee for every future use.
Discuss a similar brief ↗