Video Meeting Lobby

Let participants check camera, microphone, identity, permissions, and meeting context before joining a live call. This example brings Preview and Devices together so team members can find the next task without losing context.

It includes representative records such as Check camera framing and Confirm microphone input. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Video Meeting Lobby
Use this template in Figr

Template facts

Screen

Onboarding

Primary action

Join meeting

Pattern

Onboarding

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to join meeting while keeping participants, camera and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Preview gives users an obvious place to start.
  • Supporting view: Devices keeps the related context close.
  • Primary action: Join meeting stays visible when people need it.
  • First signal: Participants shows a useful value (7).
  • Second signal: Camera gives additional context (On).
  • Sample record: Check camera framing.
  • Next record: Confirm microphone input.

States worth designing

  • No setup steps complete: say what changed, protect progress, and offer a clear next step.
  • Step in progress: say what changed, protect progress, and offer a clear next step.
  • Identity check failed: say what changed, protect progress, and offer a clear next step.
  • Invite sent: say what changed, protect progress, and offer a clear next step.
  • Access denied: say what changed, protect progress, and offer a clear next step.
  • Setup complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Preview → Devices → Join meeting → Review outcome

Patterns used

Onboarding, Preview, Devices, contextual actions, error recovery

Why these choices work

Make each setup step and completion state clear. Allow admins to resume without repeating the work they finished.

Pay attention to preview and devices. People need to distinguish Check camera framing from Confirm microphone input. Keep participants 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 “Join meeting”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Email Composer, Call History, Shared Inbox Rules.

Start from this in Figr

Design a video meeting lobby screen inside our existing product. Use our current components, tokens and content language. Include Preview and Devices views, credible records like Check camera framing, and a clear “Join meeting” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr