ULT Movies: Android set-top-box app for remote theatre distribution
- 60%
- lower network and infrastructure costs
- 45%
- increase in average watch time
Smart TV App Development Company
Smart TV is a different platform from mobile and web. The 10-foot UI, remote control navigation, low-power rendering environments, and platform-specific certification requirements make TV app development a specialist discipline. RaftLabs builds smart TV apps for Apple TV (tvOS), Android TV, Google TV, Samsung Tizen, LG webOS, and Roku, for streaming services, content platforms, fitness apps, enterprise dashboards, and digital signage.
Multi-platform delivery across Apple TV, Android TV, Samsung Tizen, LG webOS, and Roku from a shared codebase where possible
10-foot UI and remote control navigation designed for lean-back viewing, not touch
DRM and content protection including Widevine, FairPlay, and HLS/DASH delivery
Platform certification support from submission to approval on every major TV store
The problem
OTT platform live on web and mobile but not on TV, losing the couch audience to competitors already on the big screen?
Fitness or content app with an engaged user base that keeps requesting a TV experience you haven't been able to deliver?
Short answer
RaftLabs offers smart TV app development for Apple TV, Android TV, Samsung Tizen, LG webOS, and Roku, and has shipped a production Android set-top-box streaming app that cut network and infrastructure costs 60% for a media distribution client. Exact platform scope for a new project is confirmed during discovery, since certification requirements and DRM mandates differ by store. A single-platform v1 typically takes 12 to 20 weeks at a fixed cost, with full source code ownership.
Key takeaways
Trusted by


Proof
A mobile layout scaled up to 4K fails on every dimension. Type is unreadable. Navigation built for a thumb doesn't work with a five-button remote. Tap targets become directionless. Focus states that worked on a 390px screen disappear at 10 feet.
Smart TV platforms also have meaningful technical constraints that don't exist on mobile. Memory limits are tighter. JavaScript engines on older Tizen and webOS devices are slower. GPU capabilities vary across hardware generations. And each platform has its own certification criteria that your app must pass before it can reach users.
We build TV apps that are designed for the TV context, not adapted from another platform.
According to Nielsen's 2024 US TV household report, 87% of US TV households now have at least one internet-connected TV device. For content businesses, that means the couch audience is reachable, but only if the app is built for the TV context, not ported from the mobile version.
We offer development across Apple TV, Android TV, Samsung Tizen, LG webOS, and Roku. Our production TV-adjacent delivery experience is a set-top-box streaming app built for Android hardware, not an app-store submission to any of the five platforms above, verified in the case study below. Which of the five platforms fits your audience, budget, and content rights is something we scope honestly during discovery rather than assume, including telling you if a platform needs a proof-of-concept before we commit to the full build.
Everything on the left should already be true for your product. Even one thing on the right, and a responsive site or casting support is the smarter first step.
You have a content catalogue or experience people already use on web or mobile, and are losing the couch audience to competitors who already have a TV app.
Your audience concentrates on specific platforms (Roku, Fire TV, and Apple TV in the US and UK; Samsung Tizen and LG webOS in built-in smart TVs worldwide) that you can name, not a guess.
You need native playback performance, DRM the studios require, or app-store discoverability a browser can't give you.
Capabilities
Native tvOS apps, built with the frameworks Apple's own apps use: the Focus Engine for Siri Remote navigation, native transport controls or a custom playback UI, and Top Shelf, Universal Links, and Siri voice search where the product needs them. Platform-specific detail (exact DRM tier, certification specifics) is confirmed during discovery for your content and studio requirements.
Android TV and Google TV apps with D-pad focus control, HLS/DASH adaptive playback, offline download, and live-stream ad cues, with Widevine DRM implemented against your licence server. Fire TV typically ships from the same Android codebase with platform-specific manifest and store changes, which we scope explicitly rather than assume is a drop-in.
Samsung Tizen apps on the web-based Tizen stack, with remote-control key-event handling for D-pad traversal (CSS focus alone doesn't produce it) and playback through Samsung's AVPlay API, tuned for the hardware generations your audience actually runs. Certification requirements are confirmed against Samsung's current checklist at scoping, not assumed from a prior project.
LG webOS apps on LG's SDK and the Enact framework, with Spotlight handling D-pad navigation and DASH as the primary delivery format. As with Tizen, we confirm the current LG Content Store certification requirements and the SDK/hardware range your audience runs before locking architecture.
Roku channels in BrightScript and SceneGraph XML, with list/grid content browsing, native playback, PlayReady DRM, and Roku Pay for subscription billing where the product needs it. Roku Search registration and certification specifics are confirmed against Roku's current requirements at scoping.
Across whichever platforms a project targets: authentication with link-on-TV code activation so users don't type passwords on a remote, content discovery through platform search registration and a content API that serves the same catalogue to every surface, backend and CMS integration so your existing content system feeds the TV app instead of a separate one, and an analytics integration so playback and engagement data reaches the tools your team already uses. We scope which of these a given project actually needs rather than building all of it by default.
There is no single "smart TV app." Each platform has a different language, focus model, DRM stack, and certification queue. The order you ship them in should follow where your audience actually watches, not which SDK your team already knows. In the US and UK, Roku, Fire TV, and Apple TV carry most of the connected-TV audience; Samsung Tizen and LG webOS dominate the built-in smart-TV install base worldwide. The table below is general platform information, current as of when this page was last updated, not a certification guarantee, we confirm each store's live requirements against your specific submission during scoping.
| Platform | Language and UI | DRM | First-time certification |
|---|---|---|---|
| Apple TV (tvOS) | Swift, SwiftUI, Focus Engine | FairPlay | 1 to 2 weeks (App Store review) |
| Android TV / Google TV | Kotlin, Leanback, Compose for TV | Widevine L1 | 1 to 2 weeks (Play review) |
| Amazon Fire TV | Android codebase, minor manifest changes | Widevine / PlayReady | 1 to 2 weeks (Amazon Appstore) |
| Samsung Tizen | HTML5, JavaScript, Tizen Web API | Widevine / PlayReady | 3 to 4 weeks (Samsung Seller) |
| LG webOS | HTML5, Enact, webOS SDK | Widevine | 3 to 4 weeks (LG Content Store) |
| Roku | BrightScript, SceneGraph | PlayReady | Channel review, varies by scope |
How we work
We plan every TV build backward from each store's certification checklist, because on TV it is the review, not the code, that decides your launch date. Scope is locked and price is fixed before development starts.
We map your content catalogue and DRM needs, then rank the platforms by where your audience watches, not by engineering convenience. You leave this step with a written scope, a shipping order, and a fixed-price quote per platform. No build starts without your sign-off.
Focus traversal is designed before any production code, because every platform enforces it differently: the Focus Engine on tvOS, Leanback on Android TV, a spatial key-event manager on Tizen, Spotlight on webOS. Text sizing, focus states, and D-pad paths are built for the couch, never scaled up from a mobile layout.
HLS and DASH adaptive streaming with the DRM each store mandates: FairPlay on tvOS, Widevine L1 on Android TV, PlayReady on Roku, Widevine or PlayReady on Tizen and webOS. Licence-server integration, offline caching where the platform allows it, and SCTE-35 ad cues for live monetisation are all tested on real hardware, not emulators.
We build against each store's certification checklist from sprint one, so the submission package is ready before the final sprint, not scrambled after it. We manage the review back-and-forth with Apple, Google, Amazon, Samsung, LG, and Roku through to approval. Every project includes post-launch support.
Most TV projects that slip do so for the same handful of reasons. We design around them from week one.
Key Insight
Where TV apps are heading: FAST and CTV ads. The growth on the big screen is no longer only subscriptions. Free ad-supported streaming TV (FAST) channels and connected-TV advertising are where new revenue is opening up, and both depend on server-side ad insertion and SCTE-35 cue handling built into the video pipeline. If ad-supported tiers or FAST channels are on your roadmap, we architect the streaming stack for them from the start rather than retrofitting monetisation after launch.
Why us
The engineers who assess your problem also build the solution. No bait-and-switch, no offshore handoff after the contract is signed. The team you meet in week 1 is the team that ships your v1.
We scope the work, calculate the cost, and lock it in writing before any development starts. A scope change is a change request: priced, agreed, or dropped. It never absorbs into the project and appears on the final invoice.
Trusted by enterprise clients including Vodafone, T-Mobile, Aldi, Nike, Cisco, and Lockheed Martin, as relationships, not attached metrics. Verified delivery spans healthcare (a HIPAA-compliant remote patient monitoring platform), logistics (UrShipper's multi-carrier platform), and TV-adjacent media work (ULT Movies, detailed below).
GDPR, HIPAA, and SOC 2 requirements are scoped in week 1, not retrofitted before launch, whatever your content-rights or data-handling requirements turn out to be.
Our verified TV-adjacent delivery is ULT Movies: a custom Android app for set-top boxes that sends weekly film releases to 4,000+ remote theatres across India, with offline playback for low-connectivity locations. This is an Android set-top-box deployment, not a submission to the Apple TV, Roku, Samsung, or LG app stores, and we describe it that way rather than implying broader app-store platform experience it doesn't demonstrate.
Proof
Stay on topic

Article
Cost to Build a Messaging App Like WhatsApp: The Engineering Reality
WhatsApp sends 100 billion messages a day on infrastructure that started as a small team's project. If you are building a messaging app for a niche audience - enterprise teams, a specific community, or a regulated industry - you do not need to solve WhatsApp's scale problems. You need to solve your users' communication problems. Here is what that actually requires.
Read more
Article
Cost to Build a Messaging App Like Telegram: Features and What Actually Ships
Messaging app development cost, phased features, clone tool failures, and how RaftLabs builds compliant encrypted messaging platforms for regulated industries and community operators.
Read more
Article
Quick Commerce Platform Development: Build a Blinkit-Style App That Actually Ships
Quick commerce platform development costs $30,000-$140,000 depending on dark store count, platform scope, and delivery model. Here is the full cost breakdown, the SaaS tools that fail at volume, and a phased feature plan for grocery chains and dark store operators.
Read moreWe build for Apple TV (tvOS), Android TV, Google TV, Samsung Tizen, LG webOS, and Roku. Each platform has its own SDK, UI framework, certification process, and store. tvOS uses SwiftUI and TVML/TVJS. Android TV and Google TV use the Leanback library on top of the Android SDK. Samsung Tizen uses a web-based stack (HTML5, CSS, JavaScript) with the Tizen Web API. LG webOS uses a similar web-based stack with the webOS SDK. Roku uses BrightScript and SceneGraph XML. We advise on which platforms to prioritise based on where your target audience watches, with US and UK audiences heavily weighted toward Apple TV, Roku, and Fire TV.
The '10-foot UI' describes the design constraint of a screen viewed from across the room, navigated by a remote control with directional pad and select button, not a touchscreen or mouse. Text must be large enough to read at distance (minimum 24pt for body, 36pt+ for titles), focus states must be visually prominent so the user always knows which element is selected, and the entire interaction model shifts from tap/click to D-pad traversal. Building a TV app by resizing a mobile or web layout produces an unusable experience. We design and build for the TV context from the start.
Content protection for streaming TV apps requires platform-specific DRM implementations. For Apple TV (tvOS), FairPlay Streaming is the mandatory DRM system, integrated via AVKit and AVFoundation. For Android TV and Google TV, Widevine L1 (hardware-secured, required by most studios) is the standard. Samsung Tizen and LG webOS support both PlayReady and Widevine depending on the hardware generation. Roku supports PlayReady. We implement DRM licence server integration, licence caching for offline playback where the platform supports it, and SCTE-35 ad cue handling for live stream monetisation.
A single-platform v1 with core playback, content browsing, user authentication, and store submission starts around $20,000 to $45,000. That is the smallest shippable slice and where most teams start. From there it grows: a multi-platform build across three to four platforms with a shared backend and platform-specific UI layers runs $50,000 to $120,000, and a full OTT app with DRM, live streaming, offline downloads, subscription billing, and analytics grows higher with scope. We scope every project and fix the price before development starts.
Every smart TV platform has its own review and certification process. Apple TV App Store review follows the same guidelines as iOS, with additional checks for TVUIKit and remote navigation behaviour. Google Play (Android TV) requires Leanback UI compliance. Samsung Apps (Tizen) and LG Content Store (webOS) each have their own technical certification criteria. Roku requires a channel certification review covering channel performance, content metadata, and deeplink handling. Certification timelines vary: Apple TV and Google Play typically take one to two weeks; Samsung and LG can take three to four weeks for first-time submissions.
Yes. We sign a mutual NDA before any project discussions begin. This covers your content strategy, platform roadmap, backend architecture, and any proprietary data shared during scoping. All source code is assigned to you on final payment. We do not retain rights to your codebase or reuse your platform-specific implementations for other clients.
We build for OTT streaming, fitness content, eLearning, enterprise digital signage, and community content, and our production TV-adjacent delivery is a set-top-box streaming app for a media distribution client. Our clients are typically established businesses across the US, UK, Europe, Canada, and Australia with an existing web or mobile audience they want to extend to the big screen. The common thread is a content catalogue or an experience that genuinely benefits from the lean-back TV context.
Work with us
Which platforms matter for your audience, what your content catalogue looks like, and whether DRM is in scope. We'll give you a fixed cost and a realistic timeline.