Show when friends are ready to play.

Use player presence to give social features context, such as whether someone is connected or available within your game.

Presence states

Subscriptions

Disconnect behavior

Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Choose which connection or availability states are meaningful for your game’s social UI.

Observe permitted changes for the players your UI displays and handle delayed notifications.

Use conservative offline states when a session expires or connectivity is interrupted.

ILLUSTRATIVE GAME WORKFLOW

This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Connection state is time-sensitive. Design for disconnects, delayed updates, visibility permissions, and multiple devices.

Explore complementary services for your game, with integration details for each building block.

SERVICE 1

Help players stay connected.

SERVICE 2

Keep the group together as they play.

A test workspace with access to Presence.

Step 1: pending

A confirmed API version and documented permissions for the workflow.

Step 2: pending

Client and backend tests for successful, invalid, repeated, and interrupted requests.

Step 3: pending

How does this fit my game?

What should my team own?

Can I use this integration today?

YOUR NEXT CHAPTER STARTS HERE

Explore the services and plan your first player experience.