Experiment · August 2026
What happens when the website stops owning the screen?
This experiment tested whether a native application could temporarily take over the TCL display, stream remote media, respond to voice, then return control to the existing portfolio without losing where it was.
“Atlas, demo” launches a native fullscreen video player on the Raspberry Pi while Chromium stays alive underneath. The browser is no longer treated as the system itself; it becomes one persistent application among other capabilities.
The test video was streamed remotely rather than copied onto the Pi. A 720p stream started in roughly four seconds and played at good quality, proving that larger media can live elsewhere while the Pi acts as the player.
Esc exits the native player and immediately reveals Chromium in its previous state. Early testing exposed a stale Atlas feedback bug; the cleanup lifecycle was corrected so Demo now closes cleanly without refreshing or navigating the site.
Movie audio initially overwhelmed Atlas. A simple experiment lowered playback volume and ducked it further when the wake word was detected. “Atlas” followed by “Exit” successfully closed the video, although recognition still took more than one attempt in testing.
It was proving a larger system model: a native capability can own the display temporarily, Atlas can still intervene, and the previous application can resume without being restarted. That is a meaningful step toward treating the Raspberry Pi as a local room computer with multiple capabilities instead of a television running one website.