Preview any TV app, by device: the TVAppLab TV app simulator
TV app simulator
Samsung · 55″ · 1080p · ≈ 48″ wide · 40 ppi
On web platforms (Tizen, webOS, VIDAA, SmartCast) the remote actually drives the demo app. On native runtimes like Roku and tvOS there is no web layer to talk to, so you get a layout, safe-area, and remote preview only, and the keycode stream flags those presses as not delivered.
QR scan test
Put a QR on the screen and see whether a phone can actually read it from the couch. Scanning a TV works at roughly 10x the code's width, and it drops off fast as the URL gets longer.
Reliably scannable to about 3.4 ft. You're sitting at 9 ft. Too far. Enlarge the code, shorten the URL, or expect people to walk closer.
Need the last mile? Test on real devices.
The harness catches layout, focus, and input. Memory ceilings, codec quirks, and store certification only show up on actual hardware. Tell us your targets and we'll help you cover them.
What this catches, and what it doesn't
Think of it as a layout, focus, and input harness. It gets the render surface, the safe areas, the remote, and the exact keycodes each platform fires right, which is where most TV app bugs actually live. What it does not do is emulate the platform system APIs (tizen.*, webOS.*), DRM, or store hooks. For those you still want the official vendor emulators. Our device database breaks down which layer catches which kind of bug.