Help players stay connected.

Build social relationships into your game so players can find familiar people and return to play together.

Relationship lifecycle

Friend lists

Supported discovery

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

Plan the integration

Plan a relationship flow that makes invitation, acceptance, and removal clear to each player.

Show the relationships a player is permitted to see and handle privacy and unavailable accounts.

Choose supported ways to locate players without exposing more identity information than necessary.

ILLUSTRATIVE GAME WORKFLOW

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

Relationships belong to your game’s social experience. Provider imports, global networks, discovery, blocking, and privacy require explicit support.

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

SERVICE 1

Show when friends are ready to play.

SERVICE 2

Keep the group together as they play.

SERVICE 3

Keep the conversation inside your game.

A test workspace with access to Friends.

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.