Switching who builds your Roku channel, Fire TV or Apple TV app? What to get from your old provider, which listings carry over, and what viewers notice.
Moving a TV app to a new provider means a different company builds and updates an app that is already in the store. Whether your existing listing, its ratings and its installed base come along depends on two facts per platform: whose developer account the app sits in, and who holds the key the app was signed with. As of November 2026, Roku and Amazon accept an update only when it is signed with the key of the first version, and Apple only from the developer account the app sits in. None of the three stores can give you a lost key back.
This guide covers Roku, Fire TV and Apple TV one by one: what to ask your current provider for, what happens to the store listing, and what your viewers will notice. We build these apps at Tappla, and we take over existing apps regularly, so read it with that in mind.
Before you cancel anything, ask your current provider for three things: access to the developer accounts (or confirmation that they are in your name), the signing key of every app, and where your videos are hosted. With those, an update to your existing app is usually possible on every platform. Without the key, Roku and Fire TV need a new listing, and Apple needs an app transfer.
Every store listing lives in a developer account: Roku’s Developer Dashboard, Amazon’s Developer Console, Apple’s App Store Connect. If the account is in your organization’s name, a new provider can work inside it. If your previous provider published the app under its own account, the app belongs to that account until it is moved to yours. Each store has its own process for that, and some are easier than others.
Every TV app is signed with a key before it goes into the store, and the store only accepts an update signed with the same key. The key is created once, by whoever packaged the first version. If that was your previous provider, they have it. A key is not something you can request from Roku, Amazon or Apple afterwards.
A Roku channel is packaged on a Roku device. The device signs the package with a key that has a developer ID, and the key is protected by a password. Roku calls the act of loading an existing key onto another device “rekeying”. To rekey, you need two things from your previous provider:
.pkg file that was signed with the channel’s key (any earlier version of your channel works)Neither of them can be recovered from Roku. Roku does not store your key password, and the Roku packaging documentation tells developers to package every update without generating a new key.
If your previous provider hands over the .pkg and the password, the new build is uploaded as an update to your existing channel. The channel keeps its listing, its ratings and everyone who has added it. Viewers get the new version as a normal update. Data the channel keeps on each device (Roku calls it the registry: sign-in state, settings) stays readable, because Roku shares registry data between packages signed with the same key.
The Roku Developer Dashboard compares the developer ID of every update with the previous one and reports a package from a different key as an error. Developers on Roku’s forum report cases where Roku’s partner support accepted such an update anyway; when that happens, the registry is lost and viewers sign in again. Roku does not document this as a standard path, so plan for a new channel unless Roku confirms otherwise for yours. With a new channel, viewers add it once, and ratings and the installed base stay with the old listing, which you can then retire.
Roku discontinued Direct Publisher in January 2024. A Direct Publisher channel was never signed by you or a provider, so there is no key to hand over: moving it means publishing an SDK channel. It is a path we know well; see the Roku channel builder and how a Roku channel is set up from scratch.
A Fire TV app is an Android app. Amazon’s guide to updating a published app requires the same package name as the previous version and a higher version code. Android itself refuses to install an update whose signature does not match the installed app, so the new build also has to be signed with the same keystore as the old one.
From your previous provider you need:
.jks or .keystore) and its two passwords (store and key)com.yourname.tv)If your package name starts with com.amazon.rialto.webapp, the app was made with Amazon’s web app tooling, and Amazon signed it with its own key. A native app cannot be uploaded as an update to that listing. You either publish a new listing or ask Amazon support whether they can migrate it.
Amazon moves a published app to another developer account only through its support team, and its own app transfer page advises against it unless it is necessary. For most organizations a new listing in their own account is faster.
Apple works differently. An Apple TV app is signed with certificates that belong to the developer account, not to whoever built the app. If the app is already in your own Apple Developer account, a new provider can ship updates under the same bundle ID with an App Store Connect API key that you create for them. Nothing has to be handed over by the previous provider. At Tappla you enter that key in your dashboard; our help article walks through it.
Apple’s App Transfer moves an app from one developer account to another. Apple states that the app keeps its bundle ID, its ratings and its reviews, and that users continue to receive updates. Only the account holder of the sending account can start it, and the receiving account has 60 days to accept. The app must have been released at least once and cannot be in review at the time. Apps that use iCloud need extra care, because the iCloud containers move with the app.
Our Apple TV apps can ship with an iPhone app under the same App Store listing. If your Apple TV app is in your account, the iPhone app joins that listing; there is no second app to migrate.
| Same key, same account | New listing needed | |
|---|---|---|
| Store listing, name, URL | Stays | New one |
| Ratings and reviews | Stay | Start from zero |
| Viewers who installed the app | Get the update automatically | Install the new app once |
| Data on the device (sign-in, settings) | Stays | Gone |
| Your videos and live stream | Unchanged | Unchanged |
Paid subscriptions sold inside an app through a store’s billing (Roku Pay, Apple in-app purchase) belong to that store listing. If a new listing is needed and you sell subscriptions this way, ask your provider and the store before you switch; we cannot promise those move.
A TV app is a front end. The videos live with a video host: Vimeo, Bunny Stream, a JSON or MRSS feed, a live stream URL. A new provider connects to the same source, so nothing is uploaded again. Tappla reads from these sources, and the Bunny Stream guide shows what that looks like for one of them. If your current provider also hosts your videos, export them first, and check that the export includes titles, descriptions and thumbnails.
Send this before you cancel anything:
.pkg signed with its key, and the key’s password.Keys and passwords should reach you through a password manager or another encrypted channel, never in a plain email.
The same rules apply in the other direction, so we set new apps up to make leaving easy. Since October 2026 every new Roku channel and every new Fire TV app we build gets a signing key of its own, and a customer who leaves gets that key. Apple TV apps sit in your Apple account from the start. Your listings stay yours either way; only the videos, which come through our service, stop when the subscription ends.
Yes, if your previous provider gives you a package signed with the channel’s key and the key’s password. Without them, Roku rejects updates from a different key, and the practical path is a new channel.
Not when the update goes to your existing listing; they receive it like any other update. Only a new listing means a one-time install.
Start with the developer accounts. If an account is in your name, you can reset its access with the store. If it is in theirs, you need them or the store’s support. Keys cannot be recovered without the provider.
Building the apps takes days. The longest step is usually the handover from the previous provider and, on Apple, a transfer that the receiving account has 60 days to accept.
Send us which platforms you are on today and whose accounts they are in, and we will tell you per platform what carries over. The short version of this guide, with a checklist, is on our migration page. Write to [email protected] or start a free 14-day trial and connect your video source first. Prices for every plan are on the pricing page.
Connect the video source you already run and ship native apps under your own accounts. From $49/month.