Gallery
See what others have created
azyahh
@azyahh
Requesting
Design a request flow for collecting information from a user in a hi-fi product mockup. Pick a realistic case: a support request, access request, callback request, or document request. Keep the flow tight: 3–5 steps or sections, with only the fields needed to complete the request.
Start with a clear entry point and a short explanation of what the user is about to submit. Group related inputs, mark required fields, and keep optional fields visually quieter. Use familiar controls only where they fit the data: text inputs for freeform details, radios or checkboxes for constrained choices, and a date/time picker only if timing matters.
Design the full submission path, not just the form. Show at least one validation error, one recovery state, and a confirmation state after submit. If the request needs review before sending, include a summary screen so the user can check what they entered. The final state should tell the user what happens next, when to expect it, and how to revise the request if needed.
What to deliver
- Design a multi-step request form with 3–5 fields or choices.
- Show inline helper text for any field that needs context.
- Include validation, error, and recovery states for at least one required field.
- Add a review/confirm step before submission if the request has consequences.
- Show a clear post-submit confirmation with next-step timing.
Always keep user fatigue in mind; request only essential information and use progressive disclosure to avoid overwhelming the user. The 'Requesting' flow should feel like a conversation, not an interrogation.