Enable Developer Mode
Follow Roku’s setup guide. Record the device IP address and choose an installer password. Roku has one sideload slot: this app replaces the current development app.
Developer preview · 0.1.0-beta.1
Your playlists.
A native
Roku player.
Bring your M3U playlist to the big screen. Browse categories, save favorites, and play with the Roku remote.
Unsigned development ZIP · Hardware validation pending
SHA-256 · Build provenance
OTT PLAYROKU
All channels
Favorites
Demo
01 Bip Bop test stream
02 Your first channel
03 Your channels
Interface illustration · no streams included in the website
One package. Ready to sideload.
The first preview is prepared without a connected device. Compilation and automated host tests are checked; playback, focus and compatibility still need a real Roku test.
Upload the ZIP
Open the device’s Development Application Installer in a browser on the same network. Sign in as rokudev, select the downloaded ZIP, and install it.
Add your playlist
Open the app’s playlist settings and enter an HTTP(S) M3U URL reachable from Roku. Or start with the bundled demo. Your playlist address and favorites stay in the app registry.
A temporary channel comes next.
Sideload ZIP: available. Signed package and Roku Beta access code: pending a physical device.
Build and verifySource → sideload ZIP + checksum
→
Package on RokuPhysical device + signing identity
→
Create Roku Beta appUpload .pkg in Developer Dashboard
Roku Beta is a temporary testing route: up to 20 test users, 120 days per app, and up to 10 beta apps per developer account. Updating the same Beta app distributes its new package to existing testers.
A physical Roku creates the signed .pkg. Keep the same signing identity for updates so settings survive. No account credentials or signing keys belong in the public download.
What this preview includes
IN THIS CLIENT
- Native channel list and category selection
- HTTP(S) M3U sources and a bundled demo
- Local favorites and remembered selection
- Native Roku video decoding
- Repeatable ZIP builds and release checksums
NOT IN THIS PREVIEW
- Controller pairing or
ottCLI commands - Shared favorites import from other players
- Plex, VPortal, Stalker, DRM or an on-device torrent engine
- Certified Store publication or a Beta access code
- A claim of testing on physical hardware
Built for Roku, released independently.
Why a separate repository?
Roku uses its own runtime, UI, packaging and signing process. Keeping it in ottplay-roku lets the client ship independently from the web player. Shared profile and controller support will use versioned contracts, with explicit compatibility tests.
Why BrightScript rather than the new TypeScript SDK?
The current RSG 2.0 SDK beta supports sideload only. BrightScript and SceneGraph let the same app move from sideload to a signed Beta package. The new SDK can be evaluated later without blocking this delivery path. Roku SDK status.
Will every video work?
Playback depends on your Roku model, native codecs and source. The app passes supported HTTP(S) streams to Roku Video. Browser-only engines, custom HTTP headers, DRM and unsupported codecs are not converted by this client. A media server may be needed for compatible output.
Where are my files and playlist credentials?
The website does not receive your playlist. The app reads the URL you enter and plays its media directly. The source URL and favorites are saved in the device registry; use HTTPS for private sources. Remove personal data before sharing a device or any custom package.
0.1.0-beta.1
Native developer preview · MIT source
Release notes ↗Native developer preview · MIT source