Casting must separate the content stream from the control stream
Aliases: Chromecast · AirPlay video · cast versus mirror · remote playback
What it is
Chromecast sends the film to the television and turns the phone into a remote: scrubber, volume, next episode stay in the hand, the TV shows only picture. Mirroring is the opposite—touch still happens in the source’s coordinates, the TV is another monitor. Content stream and control stream are separate pipes: one carries the media or window being watched, the other carries play, pause, and title changes. When they are fused, nobody knows which screen to watch or where to tap. AirPlay video is “TV plays, phone controls.” AirPlay mirroring is “the phone is both source and control.” One word, “cast,” covers both structures and two opposite expectations.
Why it happens
True cast moves decode and display to the receiver. The source sends a URL or a bitstream and can then lock and do something else. Control is a second, narrow protocol: play, pause, seek, volume. Hands are freed; eyes stay on the large screen. Mirroring has no such split. All input remains in the source screen’s coordinate space; the large display is a pixel echo. Pausing means looking down at the phone, which fights the posture of watching the TV. If a product silently falls back from cast to mirror (no independent session, network too weak to send anything but the whole screen), the control surface jumps from a remote beside the TV to the source’s original UI, and the mode change may be invisible. The two streams can also desynchronize: the TV still plays while the phone’s chrome is gone, or the chrome remains while the TV has returned to its home screen.
Where it stops holding
Mirroring a computer desktop to a projector, with keyboard and mouse already on the computer, already has control on the source; a phone remote is unnecessary. Games and low-latency demos need input and picture on one timeline, so they want mirroring or a wireless display, not “send to a box then remote it.” With no second touch surface (a TV and a traditional remote only), control lives on the remote’s keys; the product must fit those keys rather than assume a phone is still in hand. Static slides can be content-only, with a single presenter device turning pages.
Applying it
- On entering a cast, state that picture plays on the receiver and control stays on the initiator; keep a findable chrome (play/pause/volume/exit) even when the initiator is locked.
- Do not silently switch a session from independent playback to whole-screen mirroring. If the capability is missing, make the person choose before starting, not mid-stream.
- The chrome’s playhead must match the receiver. If the TV remote interrupts, the initiator’s chrome should become “ended on the TV,” not a fake pause.
- Verify by casting a film, locking the phone, and unlocking it. The chrome should still pause the TV; the TV must not fall back to mirroring the desktop because the phone locked. Then press Home on the TV remote and check that the phone chrome reflects an ended session within seconds.