Certification d'application Roku en 2026 : ce qui peut bloquer votre lancement

From 1 October 2026, a Roku app that does not integrate the platform’s memory monitoring interface will not be published. Static Analysis reports an error and stops the release before it reaches manual review. That single change tells you most of what you need to know about how Roku app certification works: the requirements are documented, the enforcement is automated, and the list grows as your audience does. Here’s what the certification criteria demand now, what changes this autumn, and how to build the process into your delivery cycle instead of discovering it a week before launch.

Ce qui change le 1er octobre 2026

Quatre éléments prennent effet à la même date, destinés à des groupes différents. Deux sont à l'échelle de la plateforme et s'appliquent à toutes les applications du store. Deux sont liés aux heures de streaming et ne s'appliquent qu'au-delà d'un certain seuil.

La surveillance de la mémoire devient un critère de publication

All apps will need to integrate the roAppMemoryMonitor interface and its events. Roku’s documentation is direct about the consequence: without those APIs, Static Analysis reports an error and blocks publishing. Since Roku OS 15.2, subscribed apps receive notifications when memory usage crosses 80%, 85%, 90% and 95% of the per-app limit.

Wiring in the API is trivial. Responding sensibly to a notification at 90% is not. The requirement asks, in effect, whether your app has a strategy for releasing resources under pressure, and on older Roku devices with limited memory that question has always mattered. Now it has a date attached.

Le manifeste et votre micrologiciel minimum évoluent ensemble

C'est le changement le plus susceptible de surprendre une équipe qui ne lit que la page des critères de certification. L'analyse statique exigera également rsg_version=1.3 dans le manifeste, et avec lui un firmware minimal pris en charge de Roku OS 15.1 ou version ultérieure.

The practical effect is larger than a manifest edit. Raising your minimum firmware drops every device still running an older Roku OS out of your addressable base, which for an audience on ageing hardware is a product decision rather than a build flag. Teams supporting Roku OS 12 today have the furthest to travel.

Pendant que vous êtes dans le manifeste, vérifiez le liste des API obsolètes également. L'utilisation d'une API obsolète peut entraîner l'échec d'une application aux tests de certification, et une application héritée d'une autre agence mérite d'être auditée sur ces deux aspects avant que quiconque ne fixe une date de lancement.

Continue Watching atteint des applications en dehors du US Streaming Store

Requirement 4.13 already obliges apps in the US Roku Streaming Store above an average of 5 million streaming hours per month to implement Continue Watching. From October, apps outside the US Streaming Store cross the same obligation at 1 million hours per month. TVOD, live linear and made-for-kids apps are excluded.

Un diffuseur régional desservant un marché linguistique unique aura une exigence qu'une application américaine comparable n'atteindra qu'à partir du moment où elle sera cinq fois plus grande. Pour les développeurs européens, c'est la ligne la plus déterminante du document.

Instant Resume dans le US Streaming Store

Instant Resume devient obligatoire pour les applications du Roku Streaming Store américain dépassant 5 millions d'heures par mois, à la même date.

Un changement qui s'applique déjà : le deep linking pour le direct

Indépendamment de l'échéance d'octobre, le mise à jour de la certification au printemps 2026 a supprimé l'exemption qui permettait aux diffusions en direct et aux rediffusions de contourner l'exigence de deep linking, et a renommé la section 2 en « Comptes et achats ». Les deux sont désormais en vigueur.

Si votre application diffuse du contenu en direct et que vous avez construit le deep linking autour de l'ancienne exemption, il s'agit d'un véritable travail et non d'une simple mise à jour de la documentation, et il est déjà en retard.

Ce que le programme développeur Roku attend avant votre soumission

Une grande partie de ce qui retarde le lancement d'une première application Roku n'a rien à voir avec le code. Le processus de soumission exige un ensemble de ressources et de détails de compte que les équipes laissent systématiquement de côté jusqu'à la fin, et le processus de publication ne démarrera pas sans eux.

Configuration du compte développeur et du tableau de bord

Everything runs through the Roku Developer Dashboard. You create a Roku developer account, register the app, upload the package, and run the certification tools from the same place. The developer account is a long-lived asset holding your monetization setup, payout enrolment and certification history, so it should sit with the company rather than with an individual engineer or an agency.

Ce que vous devez fournir avec la soumission

Roku requires Streaming Store information in every language the app supports: an app name, a description, and a 540×405 poster as a JPEG or PNG. The app name must clearly identify the company behind it, you must hold the rights to it, and it cannot include the Roku name or anything misleading.

Ad-supported Roku apps must provide the URL path to an app-ads.txt file, the IAB protocol that records which sellers are authorised to sell against your inventory. If Roku asks to be added as an authorised seller, you add it. Apps that run no programmatic advertising are advised to say so explicitly in the file.

You also supply customer support details, meaning a URL, an email address and a phone number, plus named administrative and technical leads. TVE, TVOD, PVOD and vMVPD apps must include working login credentials with the submission, so prepare test accounts that will still be valid weeks later rather than throwaway ones.

Canaux bêta et tests avant soumission

Roku provides an access code for distributing beta versions of an app, which lets stakeholders preview the most recent upload. Worth knowing: updates are not reviewed for certification until formally submitted, so a beta that behaves perfectly proves nothing about passing certification. Use beta channels for product feedback and the certification tools for compliance.

Two small requirements catch new apps regularly. The app must carry a non-zero version number, incremented for every build and updated in the manifest. The splash screen must support both FHD and HD resolutions, use broadcast-safe colours, avoid transparency, and have its URI listed in the package manifest file.

Des validations automatisées plutôt qu'une longue file d'attente de révision

La distinction utile entre Roku et les autres grandes plateformes de télévision connectée ne réside pas dans la vitesse en soi. Elle réside dans l'endroit où la vérification s'effectue.

Roku states that a submitted app typically takes at least five business days to be certified and published, and that apps requiring additional testing should expect feedback within about a week. Neither Samsung nor LG publishes an equivalent figure, though implementation documentation from EaselTV, a vendor that submits apps across platforms as a routine part of its work, budgets 4 to 8 weeks for a Samsung Tizen review and 8 to 12 weeks for LG, and developers on Samsung’s own forum have reported longer waits. Treat those as practitioner estimates rather than published policy.

What Roku does publish is the tooling. Every Roku app must pass Static Analysis to be published. AVOD and free apps, along with subscription apps, must also pass App Behavior Analysis, which launches the app and checks state-driven results to verify compliance with the certification criteria. Errors from either tool block publishing automatically, before a reviewer sees the app at all. We’ve written separately about ce qui rend le développement d'applications Roku plus rapide que les autres plateformes CTV.

That shapes how you plan. Where a platform leans on a manual review queue, your exposure is calendar risk and you manage it by submitting early. Where the certification checks are automated and deterministic, your exposure sits at a gate you can run yourself, so you manage it by running those checks continuously during development. Once an app has passed both tools, a self-published app can schedule its own publishing start date, then goes to Roku for final review before going live.

Les exigences qui accompagnent votre succès

Several Roku obligations are keyed to streaming hours, calculated as a monthly average over the past three months. They also apply to new apps projected to reach the threshold shortly after launch, which means a well-marketed launch can trigger them before you have any history at all.

The pattern is worth stating plainly: on Roku, commercial success generates engineering obligations. A Roku app that certified cleanly at launch can fall out of compliance eighteen months later without a single line of its code changing, purely because more people watched it.

That is a planning problem rather than a technical one. The integrations themselves are well documented. What hurts is doing them under pressure, in the same quarter you are also handling the growth that triggered them. Teams that handle this well decide at architecture stage which thresholds they expect to cross within two years, and build the hooks for those features early even if they switch them on later.

Votre modèle de monétisation détermine les règles applicables

Roku’s certification criteria are written against app model types, and a single Roku app can combine several. Free apps give access to content without video advertising and without a recurring subscription fee. Live TV apps carry linear content supported by advertising. AVOD apps show video advertisements against on-demand content. SVOD apps charge a recurring fee. TVOD apps take a one-time fee to rent or purchase content, which Roku’s own definition extends to pay-per-view events and premium early-access offers. TVE and vMVPD apps authenticate against an existing pay-television subscription. If you are still settling which of these models you run, our breakdown of Modèles économiques VOD et OTT couvre l'aspect commercial de ce choix.

The rule that catches people: where an app offers subscriptions alongside advertising or transactional content, it must comply with the requirements for each model. A hybrid service carries all of them, and each brings its own test cases into the certification process.

Un catalogue hybride multiplie également la surface d'intégration. La Xarxa+, which we built for Xarxa Audiovisual Local, the Catalan regional network, carries more than thirty local television channels and radio stations across web, mobile and connected TV, on our CTV App Framework with analytics, payment gateways and backend systems integrated into it. Each of those pieces has certification criteria attached to it, and the work is in making them behave consistently rather than in any one of them individually.

Les limites qui déterminent votre architecture

Certains critères de certification sont des listes de contrôle. D'autres déterminent discrètement la manière dont vous construisez.

Performances mesurées sur du matériel de 2019

Roku apps must launch to a fully rendered home screen within 15 seconds, complete screen-to-screen transitions within 3 seconds, respond to Roku remote button presses within 250 milliseconds, and start video playback within 8 seconds of initiation. Any process visible to users that runs longer than 3 seconds needs a loading indicator, and apps must respond to user requests within 10 seconds.

Those numbers are not measured on your development hardware. Roku specifies that requirements 3.2 to 3.6 are measured on the Roku Streaming Stick+ (Amarillo-2019 3810X) or the Roku Premiere+ (Gilbert 4K 3921X), and reserves the right to block launch across all other Roku devices if the app fails on those. Your performance budget is set by hardware from 2019.

La mesure est aussi de votre responsabilité. Les applications ont besoin d'une balise de signal pour mesurer les temps de lancement, vérifiée via la console de débogage, et les applications dotées de lecteurs vidéo personnalisés doivent déclencher elles-mêmes les balises de démarrage vidéo.

Le package d'application de 4 Mo

The app package must be 4 MB or less. Combined with the rule that an app must be available on all Roku device models receiving the current Roku OS, and that all content from the service must be available on all those models, this settles a set of architectural questions before you write anything. Assets load remotely. Libraries stay lean. Anything you were planning to bundle, you are not bundling.

Modèles d'appareils Roku et matrice de tests

Roku requires testing across multiple Roku device models before submission, specifically a combination of Roku devices with varying processing power and memory, because the app must perform on every model still receiving OS updates. If your QA estate is three recent Roku devices, you are testing the easy half of your install base.

C'est la même discipline qui s'applique lorsque lancement de services OTT basés sur le cloud: la contrainte qui vous fait échouer en production est rarement celle contre laquelle vous vous êtes entraîné.

La boucle fermée autour des comptes et des paiements

La section 2 est celle où les diffuseurs exploitant une stack unifiée sur toutes les plateformes rencontrent des frictions.

Roku apps must integrate on-device authentication, and sign-up and sign-in workflows are prohibited from using external web pages, off-device promotional material, or any other off-device authentication mechanism. Upgrades and downgrades must also complete on the device.

Apps offering transactional content or services must integrate Roku Pay, covering signup, sign-in, payment and entitlements. Requirement 2.5 goes further: apps may not facilitate or direct customers to any method of payment other than Roku Pay, and must disclose any non-Roku SDK, library or feature that enables or links to monetary transactions, with Roku holding the right to approve or deny it.

Deep linking closes the loop from the other side. Apps must support deep linking for all media types and implement Direct to Play for voice playback commands, while being prohibited from deep linking into other apps or directing users out of the app to buy content, goods or services. Nested content, embedded browsers and cross-app functionality are all out.

If you operate a single identity and billing stack across web, mobile and other connected TV platforms, Roku is the platform that expects you to work inside its own. That is a commercial question as much as a technical one, and it belongs in your business case rather than in a sprint retrospective. Teams running Roku alongside Android TV ou Tizen les découvrent généralement lors de l'intégration plutôt que lors de la planification. Le même principe s'applique aux droits et à la lecture : la certification ne vous dira pas que vos Stratégie DRM est erroné, seulement que votre application a échoué.

Intégrer la certification dans le cycle de livraison

Trois points pratiques découlent du fonctionnement réel du processus.

Une application mise à jour nécessite une nouvelle certification

Roku is explicit that updating the implementation code of an existing Roku app means the app must be re-certified and re-published, while changing the content it streams does not. A hotfix on Roku is not the same operation as a hotfix on the web, and your release cadence has to account for that. Batch code changes deliberately rather than shipping small updates continuously.

Certification compliance is also ongoing rather than a one-off. Roku reserves the right to remove published apps from the Roku Streaming Store at any time if they do not maintain compliance with the criteria, under the terms of the distribution agreement.

Exécutez les outils de certification en continu

Static Analysis, App Behavior Analysis and Roku’s test automation software are all available to developers throughout Roku app development, not only at submission. The automation tools let you write and execute test cases covering purchasing, performance, deep linking and other certification criteria.

Treating certification testing as part of the build, alongside your own unit and integration tests, converts a launch-blocking surprise into an ordinary failing check. This is the single highest-value habit we bring into Roku projects, and it costs nothing but discipline.

Surveiller le calendrier de publication

Roku blacks out the Streaming Store each year around the holiday season and advises submitting early because of the higher volume of submissions. In the 2025 season that meant two windows, one across Black Friday and one from mid-December into early January. Roku announces the dates for each season separately, so check them before committing to a launch date.

The arithmetic matters more than the exact dates. With a minimum of five business days to certify and publish, and the possibility of a second certification round, a December launch needs locking down in October. For any broadcaster whose year peaks in December, that is a hard constraint rather than an inconvenience.

Ce que le statut de partenaire officiel change, et ce qu'il ne change pas

We are an official Roku development partner, so it’s worth being straight about what that does and doesn’t mean. The certification criteria are the same document for everyone, and Static Analysis applies the same rules to our submissions as to anyone else’s. Partner status is not a shortcut through the gates described above, and you should be sceptical of anyone who implies otherwise.

What it gives us is context: a working relationship with the platform, and enough accumulated experience across Roku certification projects to know which requirements are quick to satisfy and which quietly reshape an architecture. That is the difference between reading the criteria and knowing what they cost.

Où cela vous mène

Roku certification rewards teams that treat it as a design input and costs time for teams that treat it as paperwork. The review cycle is short and the criteria are published in full, which makes the process more predictable than most. The automated gates are deterministic, they run before any human looks at your app, and the obligations attached to streaming hours mean the standard you certified against at launch is not the standard you will be held to in two years.

Planifiez en fonction du matériel de 2019, intégrez les outils de certification dans votre pipeline, préparez tôt les ressources de la boutique et les comptes de test, et décidez quels seuils vous prévoyez de franchir. Le reste, c'est de l'exécution.

Si vous prévoyez le lancement d'une application Roku ou si votre application approche de l'un des seuils d'heures de streaming, nous pouvons mettre en correspondance les exigences de certification avec votre version actuelle et organiser le travail avant qu'il ne devienne urgent. Parlez à nos experts dans l'ingénierie des médias et du divertissement.

FAQ