FIGR / UI TEMPLATE

Matchmaking Lobby

Multiplayer lobby for party members, roles, mode, region, readiness, voice state, estimated queue time, and match-found transitions.

This matchmaking reference covers gaming. Its sample screen includes Maya · Support and Jon · Duelist and the Find match action. Adapt its workflow to your product and design system.

Matchmaking Lobby

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Lobby

Primary action

Find match

Pattern

Matchmaking Lobby lobby

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The matchmaking lobby screen supports “Find match” while keeping lobby and party in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Find match
  • Main area: Lobby brings the user to the relevant workflow
  • Related area: Party keeps nearby context accessible
  • Party: 4/5 in the sample screen
  • Queue: 1:42 in the sample screen
  • Example 1: Maya · Support
  • Example 2: Jon · Duelist
  • Input: Mode

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Preserve the page structure and explain what is still loading
  • Empty: Say why there are no records and offer a clear first action
  • Error: Explain what failed, keep entered work, and allow retry
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Find match and say what happens next

Where it fits

Lobby → Party → Find match → Review result

Patterns in this screen

Matchmaking Lobby lobby, Lobby, Party, permission handling, error recovery

UX choices to review

Keep the main user task and nearby context on the same screen

In this example, Maya · Support is one of the records worth checking. Keep the sample data clearly separate from a live system.

Make the current state and next action easy to find

Consider empty, loading, permission, and recovery states

Try a similar screen in Figr

Design a matchmaking lobby screen for an existing gaming product. Use our actual design system, components, and content rules. Cover Lobby and Party, include believable records such as Maya · Support, and make "Find match" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗