The plain-English version
Following multiple simultaneous contact points using their individual identifiers and lifecycles.
Why it matters
It allows one finger to steer while another activates an action without the two controls stealing each other's input.
Let’s make it click
A game binds the first contact on the left control to movement and a second contact on the right to firing.
Vibe Bro’s heads-up
Assuming the first item in each touch event is always the same finger can swap controls when contacts end.
The docs behind it
Documentation links checked .
Editorial review · October 28, 2026
Supported: Per-contact identity and release/cancellation are supported. The warning concerns changing event-list positions, not a claim that identifiers never get reused.