Second-screen companion apps and cloud — a counterpoint about the integration question

Companion apps run on phones or tablets alongside a primary game on console or PC. They show maps, manage inventory, deliver story content, or provide multiplayer team-coordination features.

Examples: Destiny 2 companion app, Final Fantasy XIV Companion, Pokemon GO Plus integration, many sports games' fantasy-team integration apps.

Cloud framing suggests second-screen integration doesn't work because the 'game' isn't running on the user's network — it's running in a cloud datacenter. The companion app can't easily find the game's session to integrate with.

This framing is widely repeated and assumed to be true.

Companion apps typically don't talk to the game session directly. They talk to the publisher's servers. The publisher's servers know about the user's game state regardless of where the game is being rendered.

Destiny 2 companion on phone works fine when the user is playing Destiny 2 on cloud. The companion is reading the user's character state from Bungie's servers; whether the game is local or cloud is irrelevant.

Pokemon GO integration works fine across cloud-played Pokemon main-series titles. Final Fantasy XIV Companion app works perfectly with FFXIV played through any cloud service.

Companion apps that use Wi-Fi local network discovery to find the game session. A handful of older titles do this — the companion app expects to find the game on the same LAN as the phone. Cloud sessions break this because the game isn't on the LAN.

Companion apps that use Bluetooth to connect to a console controller. Some Nintendo-style 'connect the toy to the game' integrations. Cloud sessions break these because the controller is paired to the cloud client, not to the actual game-running hardware.

Companion apps that require specific platform-side authentication that doesn't include cloud as a valid source. Rare but exists.

Standard framing: second-screen apps don't work with cloud.

Counterpoint: most do, because most use publisher-server-mediated state rather than direct game-to-companion communication. The exceptions are LAN-based and Bluetooth-toy-based integrations, which are a minority.

If you've avoided cloud gaming because of companion-app concerns, the concern is largely unfounded for the titles you actually want to play. Test the specific app's behavior with cloud rather than assuming it won't work.

Bungie's Destiny 2 companion: works on cloud.

Square Enix's FFXIV Companion: works on cloud.

Activision's Call of Duty companion features (clan/social): works on cloud.

Ubisoft's various companion features: works inconsistently on cloud, mostly functional.

Nintendo's first-party companion apps for Switch games streamed via the Tencent partnership: works because Nintendo controls the cloud-streaming side.

Newer Pokemon main series companion features: mostly work; some Bluetooth-toy-required features don't.

Cloud gaming framing tends to overstate the integration problems. The category has matured enough that companion-app compatibility is mostly fine, the publisher integration model handles it transparently, and the specific brokenness is a small minority of cases.

If a specific feature you care about is the gating decision for cloud-versus-local, actually test it. The category has progressed faster than the framing has updated.