{"schemaVersion":1,"record":{"key":"mechanic/phone-sensors--t297","type":"mechanic","id":"phone-sensors--t297","lang":"en","title":"Multiple phones and cross-device interaction","summary":"Several phones divide information, roles or input space while coordinating events through an explicitly shared session.","updatedAt":"2026-10-22","status":"active","url":"https://gamemechanics.pro/en/knowledge/mechanic/phone-sensors--t297/","jsonUrl":"https://gamemechanics.pro/api/v1/knowledge/en/mechanic/phone-sensors--t297.json","markdownUrl":"https://gamemechanics.pro/content/knowledge/en/mechanic/phone-sensors--t297.md","aliases":["Interaction across multiple devices"],"tags":["Phones and built-in sensors","Mechanics and variants"],"sourceIds":["source-917b630098115bc7","source-83b748d3290cf9f1"],"sources":[{"id":"source-917b630098115bc7","title":"Android Developers: Sensors overview","url":"https://developer.android.com/develop/sensors-and-location/sensors/sensors_overview","verifiedAt":null},{"id":"source-83b748d3290cf9f1","title":"Quiplash","url":"https://store.steampowered.com/app/351510/","verifiedAt":null}],"sections":[{"id":"principle","title":"How it works","body":"Several phones divide information, roles or input space while coordinating events through an explicitly shared session."},{"id":"variants","title":"Variants","body":"### Mechanic variants\n\n<a id=\"t297-variants\"></a>\n\n- Private screens conceal roles from other participants. <a id=\"t297-v1\"></a>\n- Shared displays combine separate input results. <a id=\"t297-v2\"></a>\n- Transfers are confirmed across both devices. <a id=\"t297-v3\"></a>\n- Disconnections put roles into an explicit waiting state. <a id=\"t297-v4\"></a>"},{"id":"example","title":"Design example","body":"One phone shows a map, another controls machinery and a shared indicator confirms a rotation.\n\nPrototype check: Test joining the correct session, latency and reconnection; direct exchange needs a verified transport mechanism."},{"id":"context","title":"Context and limits","body":"Sensors provide device-dependent signals; mechanics must check channel availability and distinguish measurements, noise and missing data. Each overview separates player actions, state changes and alternative rules. Examples are hypothetical design scenarios, not claims about a named game. A prototype check states an observable question for the next iteration. Existing detailed references remain separately linked from the direction map."}],"relations":[],"placements":[{"catalogId":"phone-sensors","id":"t297","title":"Phones and built-in sensors","url":"https://gamemechanics.pro/en/mechanics/phone-sensors/#t297","categoryIds":["mechanics"]}],"supersededBy":[],"attributes":{"preview":{"updatedAt":"2026-10-22","title":"Interaction across multiple devices","description":"Several phones divide information, roles or input space while coordinating events through an explicitly shared session.","image":{"src":"images/mechanics/general-quiplash-02.webp","width":1440,"height":810,"game":"Quiplash","sourceUrl":"https://store.steampowered.com/app/351510/","originalUrl":"https://shared.akamai.steamstatic.com/store_item_assets/steam/apps/351510/ss_b43742be0818c5c18a6415f51ac4d2e383aa732f.1920x1080.jpg?t=1725046271","credit":"Jackbox Games, Inc. / Jackbox Games, Inc.","rights":"Game imagery © its respective rights holders. Publisher-distributed screenshot from Steam; all rights reserved. Excluded from MIT and CC BY 4.0.","caption":"Participants compare answers and vote","alt":"Participants compare answers and vote","markers":[{"x":48,"y":53,"label":"Two answers are offered for a shared choice"},{"x":68,"y":16,"label":"A room code connects personal devices to the game"}]},"tips":["Show the shared session and the device’s role before joint interaction begins."],"examples":[{"title":"Quiplash","url":"https://store.steampowered.com/app/351510/"}]}},"endsAt":null,"provenance":"Original bilingual editorial overviews authored for gamemechanics.pro on 2026-10-20 and reviewed on 2026-10-21. Scenarios are hypothetical design examples; prototype checks describe work to perform, not completed playtests. Primary sources support the stated techniques and implementation context, not every proposed variant.","license":"CC-BY-4.0","codeLicense":"MIT","attribution":"gamemechanics.pro contributors","catalogKey":"catalog/phone-sensors"}}