---
id: phone-sensors
status: active
supersededBy: []
lang: en
title: Phones and built-in sensors
description: >-
  Sensors provide device-dependent signals; mechanics must check channel
  availability and distinguish measurements, noise and missing data.
intro: >-
  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.
updatedAt: '2026-10-21'
sources:
  - title: 'Android Developers: Sensors overview'
    url: >-
      https://developer.android.com/develop/sensors-and-location/sensors/sensors_overview
    description: >-
      Primary documentation of sensor types, availability detection and events.
      Sensor presence and access depend on the particular environment.
counts:
  families: 2
  branches: 2
  variants: 8
url: 'https://gamemechanics.pro/en/mechanics/phone-sensors/'
markdownUrl: 'https://gamemechanics.pro/content/mechanics/en/phone-sensors.md'
license: CC-BY-4.0
codeLicense: MIT
attribution: gamemechanics.pro contributors
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.
---
# Phones and built-in sensors

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.

## Mechanics and variants

<a id="mechanics"></a>

### 1. Light, proximity and other available sensors

<a id="t296"></a>
id: t296
canonicalId: phone-sensors--t296
url: https://gamemechanics.pro/en/mechanics/phone-sensors/#t296

An available sensor turns a nearby physical condition into game state when the device exposes an appropriate measurement.

#### Mechanic variants

<a id="t296-variants"></a>
- Ambient light selects a state within a stable range. <a id="t296-v1"></a>
- Proximity switches modes when a sensor is covered. <a id="t296-v2"></a>
- Threshold margins suppress boundary chatter. <a id="t296-v3"></a>
- Manual controls replace unavailable measurements. <a id="t296-v4"></a>

Design example: A fictional sprout opens as light changes, with a slider supporting devices lacking light-sensor access.

Prototype check: Test sensor and access availability in the target environment, missing-data handling and fallback without fabricated readings.

- [Android Developers: Sensors overview](https://developer.android.com/develop/sensors-and-location/sensors/sensors_overview)

### 2. Multiple phones and cross-device interaction

<a id="t297"></a>
id: t297
canonicalId: phone-sensors--t297
url: https://gamemechanics.pro/en/mechanics/phone-sensors/#t297

Several phones divide information, roles or input space while coordinating events through an explicitly shared session.

#### Mechanic variants

<a id="t297-variants"></a>
- Private screens conceal roles from other participants. <a id="t297-v1"></a>
- Shared displays combine separate input results. <a id="t297-v2"></a>
- Transfers are confirmed across both devices. <a id="t297-v3"></a>
- Disconnections put roles into an explicit waiting state. <a id="t297-v4"></a>

Design example: One phone shows a map, another controls machinery and a shared indicator confirms a rotation.

Prototype check: Test joining the correct session, latency and reconnection; direct exchange needs a verified transport mechanism.

- [Android Developers: Sensors overview](https://developer.android.com/develop/sensors-and-location/sensors/sensors_overview)

## Sources and examples

Sources support particular techniques or methodology, not every family variant. Design examples and mechanic combinations are illustrative.

- [Android Developers: Sensors overview](https://developer.android.com/develop/sensors-and-location/sensors/sensors_overview): Primary documentation of sensor types, availability detection and events. Sensor presence and access depend on the particular environment.