Fire TV app development

Fire OS is Android with Google removed

Fire OS is an Android fork, and that is genuinely good news for most of your code: same language, same build system, same player stack, same layout system.

The catch is that Google Play services are not on the device. Amazon states that APIs relying on Google-specific services, such as Google location services, are not available on Fire TV, and that you must use Amazon services instead.

That absence is rarely where teams look, because the dependency is usually indirect. The things that break are the ones nobody listed in the estimate:

• Billing, because Play Billing is a Play service.
• Sign-in, if it uses Google identity.
• Cast, which is a Google service.
• Push and analytics, wherever they run through Firebase. Amazon's guidance is to check each Firebase SDK: if it does not need Google Play services you can keep it, and if it does you either find an alternative or disable that feature on Amazon devices.

Amazon supplies replacements — the Appstore SDK covers in-app purchasing and DRM, and the A3L libraries cover authentication, location and cloud messaging — but each one is an integration, not a flag.

So the honest framing for a rollout: Fire TV shares your code and not your dependencies. Compared with Roku, where nothing transfers at all, that is still a bargain. Compared with the afternoon people budget for it, it is not.

Your viewers are on an older Android than the hardware suggests

This is the number that changes the estimate, and it is easy to check.

Amazon maps each Fire OS release to the Android versions underneath it:

Fire OS	Android base	API level
Fire OS 16	Android 16 / 15	36 / 35
Fire OS 14	Android 14 / 13 / 12L / 12	34 / 33 / 32 / 31
Fire OS 8	Android 10 / 11	29 / 30
Fire OS 7	Android 9	28
Fire OS 6	Android 7.1	25
Fire OS 5	Android 5.1	22

Now look at which devices sit where. The Fire TV Stick 4K Plus from 2025 runs Fire OS 8 — Android 10 or 11. The Fire TV Stick HD from 2024 runs Fire OS 7, which is Android 9. Fire OS 14 and 16 appear largely on partner smart TVs, from manufacturers such as Hisense and TCL.

The consequence is worth stating plainly: hardware release date is a poor guide to API level on this platform. A stick sold new last year can be several Android generations behind the phone in your pocket, and your minimum SDK has to reach it.

Fire TV app development for broadcasters runs into this hardest, because a broadcaster's audience skews toward the cheapest streaming stick in the range rather than the newest.

Set your minimum SDK from the Fire OS distribution, not from Android's. The two are different populations, and the Android dashboard will flatter you.

Amazon takes the payment, in its own way

Fire TV uses Amazon's In-App Purchasing API, not Google Play Billing.

That completes a set worth seeing together, because a television rollout meets three incompatible answers to the same commercial question:

• Apple — in-app purchase by default, with the reader-app route and the External Link Account Entitlement as the way to keep your own billing, at the cost of in-app purchase entirely.
• Roku — Roku Pay, on the device, with external sign-up webpages prohibited.
• Amazon — Amazon In-App Purchasing, through the Appstore SDK.

Three platforms, three billing integrations, three sets of entitlement plumbing to reconcile against whatever your own subscriber system already believes. This is why we ask about the business model before the design: it is the decision that shapes the most code across the whole rollout, and it is the one most often deferred.

Fire TV app development for vod platforms carries the most of this work, because a subscription catalogue needs entitlement state to agree across every store that sold a subscription.

The Appstore closed on phones, not on televisions

Worth clearing up, because it causes confusion in scoping conversations.

On 20 August 2025, Amazon discontinued the Amazon Appstore for Android mobile devices — developers can no longer submit or update apps targeting Android phones there, and apps downloaded from it are no longer guaranteed to work on Android devices. Amazon Coins were discontinued on the same date.

The Appstore continues on Fire TV and Fire tablets. So if someone tells you the Amazon Appstore is being wound down, they are describing the mobile side. The distribution channel for your television app is unaffected.

One related detail at submission: Amazon's own application DRM — the licensing wrapper on the app package, not the content protection on your streams — is optional. You can offer the app DRM-free, manage your own, or apply Amazon's.

Voice, search and the launcher work differently

Amazon does not use the Android TV mechanisms here, so the parts of your app that surface content need rebuilding rather than porting.

Fire TV supports some but not all of Android's Leanback support library, and Amazon states that SearchFragment specifically is not supported. Voice runs through Amazon's own system controls and Alexa, and getting your catalogue into Fire TV's search and recommendations means submitting to the Amazon Catalog rather than implementing local content providers as you would on Android TV.

There is an irony worth noticing if you are scoping both platforms at once. On Android TV, Google has deprecated Leanback and points you at Compose. On Fire TV, Leanback is partially supported. The two platforms are moving in different directions, so a shared TV interface layer is less shareable than the common Android lineage implies.

The remote has extra hardware buttons — rewind, fast-forward and menu — which are useful and optional, and worth handling because viewers who have them expect them to work.

The Android TV emulator does most of the work

For Fire TV development Amazon documents using the Android TV emulator from Android Studio's AVD Manager — created under the TV category as an Android TV device, at API level 23 or higher. Below that, Amazon notes that media playback fails in the emulator outright.

There are documented quirks. You cannot click media player buttons with the mouse, because mouse clicks generate motion events that break playback; keyboard controls or the emulator's own side buttons are the workaround.

Amazon's own recommendation is still to test on an actual Fire TV device, and for a streaming app that is the right instinct — but for the wrong reason to skip the emulator entirely. The split worth planning around is:

• The emulator handles layout, focus and navigation, and most application logic. That is a large share of day-to-day work and it does not need hardware.
• Only real devices show you Amazon services — the Appstore SDK, Amazon IAP, Amazon DRM — Alexa and voice integration, the remote's extra hardware buttons, and performance on an older stick. Given the Fire OS spread above, that last one decides whether your app feels acceptable to a real audience.

So you need real sticks spanning the Fire OS versions you support, and you need them before the sprint where playback lands — but you do not need one on every desk from day one.

What carries over from Android TV

The honest split, if you have an Android TV app already:

Carries over. Kotlin or Java. Your build system. Your player and DRM integration. Your API client, entitlement model and catalogue code. Your layout and focus handling. React Native is workable too, though check the supported-library list before assuming a given package runs.

Does not. Every Google Play services dependency, per the section above. Billing. Voice and search integration. Store listing, submission and metadata. And your test strategy in part, because anything touching Amazon services has to move onto real hardware.

Fire TV app development for fast channel operators is the lightest version of this work, because a linear channel has little entitlement plumbing and often no billing integration at all.

What drives the cost

A range that fits everyone helps nobody, so here is what actually sets the number.

1. Whether an Android TV app already exists. This is the biggest saving on the platform, and it is real — just not total.
2. How many Google Play services dependencies you have. Each one is a replacement, and the list is usually longer than the team expects.
3. Whether billing is in scope. Amazon IAP is its own integration.
4. The oldest Fire OS you support. Fire OS 6 and 7 devices are still in living rooms, and they set your minimum SDK.

Tell us those four and you get a real number rather than a range that covers everyone.

Who builds it

Everything above is how we actually work rather than a checklist assembled for this page.

We build our own tooling. VibeView came out of exactly this problem — shipping to every platform means testing on every platform — which on Fire TV means real hardware for everything Amazon-specific. When a project needs middleware rather than only an app, MwareTV is a technology partner of ours, so both sides come from one conversation.

And the people who scope your project are the people who build it. There is no account layer between you and the engineer who knows which of your Firebase SDKs will stop working on a Fire TV Stick.

Where Fire TV sits in the rest of your rollout

Fire TV belongs immediately after Android TV. The code is shared, the dependency work is contained, and doing them together means you find the Google Play services list once rather than twice.

Against Roku, the two are the streaming-stick pair every OTT service eventually needs, and they are opposite in character: Roku shares none of your code and publishes exact certification timings; Fire TV shares most of your code and asks you to prove which parts of it still work without Google.

We build these, end to end

The Fire TV app, the replacement of Google Play services dependencies, Amazon IAP where the business model needs it, Amazon Catalog integration for search and voice, real-device testing across the Fire OS versions you support, and Appstore submission.

If you already have an Android TV app, we will tell you honestly which of your dependencies survive the move — before you commit to a number based on the assumption that Android is Android.

Send us your Android TV status, your list of Google and Firebase dependencies, and the oldest Fire OS you intend to support. You will get back a scope and a number rather than a brochure.