Quiz Builder

Author assessments with question types, answer choices, scoring, timing, randomization, preview, and publish controls. This example brings Questions and Settings together so learners and course teams can find the next task without losing context.

It includes representative records such as Multiple choice and Scenario question. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Quiz Builder
Use this template in Figr

Template facts

Screen

Builder

Primary action

Publish quiz

Pattern

Builder

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to publish quiz while keeping questions, points and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Questions gives users an obvious place to start.
  • Supporting view: Settings keeps the related context close.
  • Primary action: Publish quiz stays visible when people need it.
  • First signal: Questions shows a useful value (18).
  • Second signal: Points gives additional context (100).
  • Sample record: Multiple choice.
  • Next record: Scenario question.

States worth designing

  • No configuration selected: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Invalid rule or block: say what changed, protect progress, and offer a clear next step.
  • Preview generated: say what changed, protect progress, and offer a clear next step.
  • Publish blocked: say what changed, protect progress, and offer a clear next step.
  • Version restored: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Questions → Settings → Publish quiz → Review outcome

Patterns used

Builder, Questions, Settings, contextual actions, error recovery

Why these choices work

Show constraints before adding blocks, keep a usable preview and protect unsaved changes as people test a different direction.

Pay attention to questions and settings. People need to distinguish Multiple choice from Scenario question. Keep questions visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Publish quiz”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Assignment Submission, Gradebook, Lesson Player.

Start from this in Figr

Design a quiz builder screen inside our existing product. Use our current components, tokens and content language. Include Questions and Settings views, credible records like Multiple choice, and a clear “Publish quiz” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr