Skip to main content
This topic breaks down the flow for multiplayer game invites from one user to another on XBOX. With the XBOX One, the UX for multiplayer game invites has changed. This is a change to the UX only and doesn’t affect any behavior or functionality from the perspective of your title. This means that you don’t have to make any code changes to accommodate this UX change.

Summary of changes

  • The initial invitation toast notification has changed from “join my party” to “<game title> Let’s Play”. Users can launch the game and jump right into gameplay by selecting a button in the notification.
  • The Party app doesn’t snap by default when the user selects the new toast with the deprecation of app snapping across XBOX One family consoles and XBOX Series consoles. This change was also made so that the user can jump right into gameplay.
  • A new toast has been added on the sender’s side that says “Adding <number> friends to the game”. This makes it clear that invites were sent out when a game session was associated with a user’s party.
The detailed UX flows are described in the following sections. Each table shows an example flow for two users, Felix and Hannah. These flows are shown in each column and occur in parallel. The highlighted text shows the adjustments that have been made from the prior UX flows.

Inviting users from within a game

In a party and switching titles flow

Invite flow from Home

More about game invitation toast notifications

The Game Invite Sent toast notification only appears the first time a game session is established with remote party members. Subsequent requests that are sent to remote party members don’t generate this toast notification, so that the user isn’t spammed with repeated notifications if the title makes multiple calls to PullReservedPlayersAsync.
The best practice is to add all desired friends as Reserved, and then call PullReservedPlayersAsync only once.
Last modified on September 1, 2026