Keep a business status page in view
Put an existing web dashboard on a dedicated Android display. The website supplies its own data and refresh behavior.
Result to check: The intended page remains readable on the target screen.
Follow this task ↗Keep a business page visible or rotate information and local media. Start with the content you already maintain, then check how it behaves on the intended screen.
A team status page, reception welcome screen, or product information loop already has a source of content. Web Launcher gives that content an Android display; it does not create the business data or manage a remote screen fleet.
For a live business page, use the status-display workflow. For a mixed loop, follow the media and configuration checks below. Network, WebView, authentication, and media decoding remain device-specific. Neither a promotional scene nor an R2 test screenshot proves a customer’s installation.
Put an existing web dashboard on a dedicated Android display. The website supplies its own data and refresh behavior.
Result to check: The intended page remains readable on the target screen.
Follow this task ↗Arrange webpages, local images, and compatible MP4 clips in one on-device playlist, then test a full cycle.
Result to check: Every enabled item displays in order with usable orientation and timing.
Follow this task ↗Test readability, login, updates, and the full playback loop before relying on the setup. These are application patterns, not customer deployment claims.