Mobile Multiplayer Made Manageable
summary
Demo shows a Google Play Games real‑time multiplayer stack that builds peer‑to‑peer meshes with libjingle and RTP, handling lobby, invites and NATs for you. Rooms use a RoomConfig builder with invite lists or automatch; messages are opaque byte arrays sent via sendReliableRealTimeMessage or sendUnreliableRealTimeMessage. The infra succeeds in ~92% direct connections and falls back to Google relay otherwise. Examples cover invitation inbox, waiting room, participant vs player IDs, required callbacks, and leaving rooms on onStop — all working end‑to‑end in the demo.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:11Why Multiplayer
- 0:47Social Graph
- 1:18Mobile Gaming
- 1:57Engagement Discovery
- 2:08Example
- 4:33What just happened
- 5:27Room definition
- 8:43Diagram
- 9:43Signin
- 12:02Room Config
- 13:19Dialogue Result
- 13:55Automate Settings
- 14:21Create Room
- 15:43Receiving Invitations
- 16:33Pending Invitations
- 18:45Activity Result
- 19:42Advanced Session
- 20:20Waiting
- 20:47On Room Connected
- 22:31Participant ID
- 23:58Reliable RealTime Message
- 24:55Receive Message
- 25:33Message Security
- 27:20Other Problems
- 28:19Callbacks
- 28:49One Word of Warning
- 29:13Leave Room
- 29:32NonStop
- 29:58Recap
related talks
59mFrom creation to connection: What’s new for multiplayer gaming at
44mSeamless mobile real-time communication with WebRTC
45mReal-Time Multiplayer on Android: Lessons from NYT Crossplay
47mReliving the History of Multiplayer Games
31mWhen one device is not enough
49mMultiplayer Misadventures - Tales from making our first PvP multiplayer game in Unity
35mHypercasual Games & Real Multiplayer, a Marriage Come True!
20mMultiplayer 101: Your Ideal Tech Stack