Recommended preparation
Premium

UI Component and State Design From a Mock

By FrontendAtlas Editorial · Updated Jul 28, 2026

Try the prompt first

Mid-level15 min first pass

Turn a support-inbox mock into clear component boundaries, URL and server state, local drafts, optimistic mutations, responsive behavior, and accessible focus.

Constraints

  • Keep client, server, and rendering ownership explicit.
  • Cover loading, failure, recovery, and accessible interaction states.

Challenge summary

Turn a customer-support inbox mock into component boundaries and explicit URL, server, draft, mutation, and responsive view state.

What you'll practice

  • Derive product questions and responsive behavior from incomplete visual evidence.
  • Separate shareable URL state, versioned server entities, ticket drafts, and optimistic command overlays.
  • Preserve an unsent reply while background updates and failed mutations reconcile.
  • Restore meaningful focus as the workspace moves between desktop panes and mobile routes.

What Premium unlocks

Premium unlocks the full architecture walkthrough, evaluation rubric, trade-offs, and failure-mode analysis.

Free related practice

Upgrade to FrontendAtlas Premium to access this system design scenario. Already upgraded? Sign in to continue.