In Europe, the connected TV question isn’t which platform wins. No platform does. Google TV leads the smart TV market at 32%, Samsung and LG sit on installed bases built over a decade, and a handful of newer operating systems are taking share from all of them. The decision that actually matters is the order in which you build. Here’s what drives the cost of connected TV app development in Europe, how to sequence it, and where Roku fits in that order.

Europe has no default platform

The American shortcut is to launch on Roku, learn from it, then add the rest. That works because one operating system carries enough users to justify going first.

What the shipment data says

European data refuses to cooperate. Omdia’s April 2026 TV Design & Features Tracker puts Google TV in front of the European smart TV market at 32%, with Android just over 30% of annual smart TV shipments, Samsung’s Tizen below a quarter and LG’s webOS around a fifth. Google TV is the current interface layer on Android TV, so those first two figures describe one family counted slightly differently rather than two separate contenders. V, Hisense’s platform formerly branded VIDAA, is forecast to overtake webOS during 2026.

Operating systems launched since 2022, including V, Titan OS and TiVo OS, are expected to climb from 21% of the European smart TV market in 2025 to roughly 28 to 30% by 2030. They’re winning shelf space by offering smart TV manufacturers a cut of advertising and data revenue rather than treating the TV screen as a one-off hardware sale.

Roku OS and Fire TV, in Omdia’s phrasing, play only minor roles in Europe. In the United States, Parks Associates put Roku OS at 28% of household usage in April 2026. Same company, different strategic weight, and every planning template written in California assumes the American version.

Three market share metrics that get mixed up

One caution before you build a business case on any of these numbers. They measure different things.

Omdia counts smart TV shipments. Parks measures household usage of the operating system. Pixalate counts open programmatic ad transactions, which is why its UK ranking (Samsung 32%, Amazon Fire TV 24%, Roku 19% in Q2 2025) describes advertising traffic rather than installed base. Vendor decks mix these market share figures freely. Your board paper shouldn’t.

Where Roku actually fits

Before you model Roku’s reach, check whether Roku is sold in your market at all.

The five supported markets

Roku’s own country selector lists five European territories: the United Kingdom, Ireland, France, Germany and Austria. The UK and Ireland have had Roku streaming devices since 2012 and France since 2015. Austria is a German-locale market with incomplete app coverage rather than a launch in its own right, and Switzerland isn’t supported. If you need the platform basics before the market picture, our explainer on what Roku TV is and how it works covers the operating system and the device range.

No other European market has an official Roku retail presence, for streaming devices or for smart TVs. That includes the Netherlands, Spain, Italy, Portugal, the Nordics, and the whole of eastern Europe from Poland to Romania. In those markets, Roku is unlikely to be a priority unless your own audience data shows meaningful usage.

Germany, and the DACH gap

Germany got Roku streaming players in September 2021 and Roku TV sets in October 2022 with Metz blue and TCL as the first licensing partners. Its 2025 deal with Vestel, Europe’s largest TV manufacturer, adds Roku OS smart TVs under the Finlux brand, starting in the UK. German connected TV households reached 70.3% in the AGF and Kantar Plattformstudie 2025-II, with internet-based reception jumping to 17.7% from 11.3% year on year. The audience is there. The question is which operating systems it sits behind.

For a DACH broadcaster this reduces neatly. Roku is a Germany consideration and rarely more than that. German-speaking broadcast groups routinely run all three markets from one product roadmap and one release train, so a platform that exists in one of your three territories needs its own business case and its own launch window rather than a slot in the group schedule.

How many platforms you actually need

Vincent Grivet, chair of the HbbTV Association, told the Connected TV World Summit in 2026 that European broadcasters typically interact with 10 to 15 different technical environments, each with its own operating system, app ecosystem and commercial framework.

The UK regulator arrived independently at a similar figure. Working from a threshold of more than 700,000 active users, Ofcom recommended designating 15 connected TV platforms as regulated Television Selection Services, from Amazon Fire TV and Google TV through to Sky Q, Virgin Media and Freely.

Two independent methods, one answer in the low teens. That’s the real scope of connected TV app development in Europe, and it’s why the interesting question isn’t which platform to pick. It’s what each additional one costs you.

Four codebases, not fifteen

Platform count and engineering count are different numbers, and the gap between them is where the money is.

The smart TV web app family

Five of the smart TV platforms you care about in Europe run web apps on a Linux base: Samsung’s Tizen, LG’s webOS, V, Titan OS and TiVo OS. One well-built HTML5 and JavaScript codebase covers the application layer across all of them.

That’s a reduction in development, not an elimination of it. Each platform still needs its own work on video playback, DRM key exchange, remote control input, lifecycle events such as the TV screen going into standby, packaging, signing, QA and store certification.

In multi-platform CTV projects, that residual work is consistently underestimated. The pattern we see is that the extra effort rarely comes from rebuilding the interface. It comes from playback behaviour differing between device generations, DRM licence handling varying by platform, memory limits on older sets, and the QA matrix needed to prove all of it before submission. Teams that budget for one codebase and forget the tail end up shipping late on four platforms at once.

This family is still where smart TV apps are least expensive to add, and it’s where most of the European installed base sits. That coincidence is the strongest argument for the order of work set out below.

The Android family

Google TV, Android TV and legacy Fire OS share an Android stack in Kotlin or Java. One more codebase, three more surfaces, and it covers the operating system Omdia has leading the region. Android TV also dominates operator-supplied streaming devices across several European markets, so the same build often reaches set-top box users as well.

Roku, the outlier

Roku requires BrightScript and the SceneGraph framework, with no official HTML5 or React Native path. Nothing you’ve written for any other platform transfers.

That matters twice over in Europe, because Roku combines the highest marginal engineering cost with the lowest regional reach. It also has the most demanding hardware floor on the list. Roku streaming devices run anywhere from 512MB to 2.0GB of DRAM, and certification requires your app to work across every model receiving the current OS, so you’re testing against roughly a decade of hardware. From 1 October 2026, apps must integrate the roAppMemoryMonitor interface to pass certification at all.

None of that makes Roku a bad platform. Our guide to what makes Roku app development faster than other CTV platforms covers where it genuinely repays the effort. It makes Roku a platform to schedule deliberately rather than by default.

Apple TV and Amazon Vega OS

Apple TV runs tvOS and needs Swift, so it’s a fourth codebase. Apple doesn’t appear in Omdia’s European smart TV rankings, because tvOS ships on a streaming device rather than a television, and it discloses no European installed base. It does sit on Ofcom’s list of 15, which gives a UK public service broadcaster a reason to be there regardless of share.

Amazon has added a fifth target. Vega OS, launched in October 2025 on the Fire TV Stick 4K Select, is a Linux system built on React Native that uses VPKG packages rather than APKs, and existing Android-based Fire OS apps don’t run on it without re-engineering. Older streaming devices stay on Fire OS while new ones ship with Vega, so anyone already shipping to Fire TV now maintains both. Our breakdown of what Amazon Vega OS means for Fire TV sets out the migration decision.

What certification costs you in calendar time

Code is the part teams estimate. Certification is the part that moves launch dates.

Each platform has its own store account, signing keys, packaging format, review queue and criteria document, and none of it is shared. Roku is the most predictable of the group: a first review typically returns within 24 to 48 hours, and criteria are updated twice a year with roughly six months of notice before a requirement becomes blocking. That’s how the October 2026 memory rule was announced. Other stores are less regular.

What we see in practice is that the first submission on a new platform is rarely the one that ships. Something small comes back, usually navigation, metadata or an accessibility control, and the fix is quick while the re-review queue is not. Plan submissions as a staggered sequence with slack between them, because teams that send every platform to review in the same week find that one rejection holds the entire launch announcement.

Two things that change the order

Device share tells you where the users are. Two other factors decide whether a platform is worth the build.

Monetisation isn’t uniform. The UK share of voice figures quoted earlier were measuring advertising all along, describing where CTV ads actually transact rather than where devices sit in living rooms. A platform can hold users without carrying the demand. Ad stacks differ too: Roku requires its own advertising framework for ad-supported channels, and even under server-side ad insertion the measurement beacons must fire client-side through it. If you run your own ad stitcher, our guide to server-side ad insertion for broadcasters covers where that control is worth keeping. Judge a platform on inventory value and billing terms, not only on how many devices it ships.

In some markets, reach isn’t the only reason to be there. The UK Media Act 2024 requires designated connected TV platforms to carry public service broadcaster players prominently and accessibly, and the regulations designating 15 platforms came into force on 1 July 2026. Germany’s Medienstaatsvertrag requires easy findability in user interfaces. From 8 May 2027, Article 20 of the European Media Freedom Act obliges device and interface makers to keep a broadcaster’s visual identity clearly visible. If you’re a designated broadcaster, some platforms are on your list for legal reasons before commercial ones.

One thing regulation won’t do for you. Connected TV operating systems aren’t designated gatekeepers under the Digital Markets Act, so the billing concessions reshaping mobile app stores don’t reach connected devices. Roku Pay’s 80/20 split, its requirement that sign-up and sign-in complete on the device, and the equivalent terms at Samsung and LG are legally stable. Plan your monetisation on that basis.

The order to build in

The aim is simple: reach as much of the European audience as you can for the least engineering effort, then add platforms as your own data justifies them.

  1. Build the smart TV web app family first. Tizen, webOS, V, Titan OS and TiVo OS from one HTML5 codebase gives you the largest share of European smart TV shipments for a single engineering effort, with the platform-specific tail budgeted honestly.
  2. Add the Android family. Google TV and Android TV lead the region, and legacy Fire OS comes largely from the same stack.
  3. Treat Fire TV as two targets. Vega OS is a separate build rather than an update.
  4. Add Roku where your data supports it. The UK first, Germany if usage justifies it, and budget for a standalone BrightScript codebase plus the October 2026 certification changes.
  5. Sequence Apple TV by audience, or earlier if a regulator has put it on your list.
  6. Handle operator platforms and HbbTV separately. Sky, Virgin Media, MagentaTV, Swisscom blue TV and Freely don’t work like app stores. Distribution there is negotiated rather than certified, HbbTV and OpApp reach the TV screen through the broadcast signal, and the lead times are commercial. Start those conversations early.

Be clear about what sequencing doesn’t solve. It reduces the cost of coverage, and it doesn’t reduce the number of certification regimes, store accounts or release calendars you operate. A shared codebase has a ceiling too: reaching users well still means tuning smart TV apps across a decade of devices, and live streaming makes it harder again, since live sports concentrate concurrency into minutes and the oldest devices fail first.

The European market won’t consolidate around one platform in time to make this easier. Build the widest coverage you can for a single engineering effort, then add platforms in the order your audience data, your monetisation and your regulator justify. Connected TV app development gets expensive when the order is wrong, not when the list is long.

If you’re planning connected TV app development across European markets and want the sequencing, cost drivers and certification calendar set out before you commit engineering time, talk to our experts in media and entertainment.

FAQ

Realistically between 10 and 15. The HbbTV Association puts the number of distinct technical environments European broadcasters deal with at 10 to 15, and Ofcom independently designated 15 connected TV platforms in the UK using a threshold of 700,000 active users. The engineering count is lower, because several platforms share a codebase.

Google TV, at 32% of the European market according to Omdia’s April 2026 tracker, with Android just over 30% of annual smart TV shipments. Samsung’s Tizen sits below a quarter and LG’s webOS around a fifth, while V is forecast to overtake webOS during 2026. No single platform dominates the way Roku does in the United States.

No. Roku officially supports the United Kingdom, Ireland, France, Germany and Austria, with Austria a limited German-language market. Switzerland isn’t supported, and there’s no official Roku retail presence in the Netherlands, Spain, Italy, Portugal, the Nordics or eastern Europe. The Roku Channel is available in only one European country, the UK.

Roku requires BrightScript and the SceneGraph framework, with no official HTML5 or React Native route. Samsung’s Tizen, LG’s webOS, V, Titan OS and TiVo OS all run web apps, so one HTML5 codebase covers the application layer across them. Roku shares nothing with the others, which makes it a standalone codebase and a standalone maintenance commitment.

It covers the application layer, not the whole build. Tizen, webOS, V, Titan OS and TiVo OS are web platforms, so the interface and business logic can be shared. Each still needs its own work on playback, DRM, remote control input, lifecycle handling, packaging, QA and certification, and that tail is the part most projects underestimate.

arrow_circle_right Table of contents

Damian Maicher

Business Researcher

Related articles