## Introduction The New Zealand government has proposed a bold mandate: require television manufacturers to feature local streaming apps-like TVNZ+, ThreeNow. And MΔori+-on the default home screen of every smart TV sold in the country. This isn't just a policy talking point; it's a technical intervention into the platform dynamics that have silently shaped the viewing habits of millions. For developers and engineers working in the digital media space, this move raises profound questions about the future of app distribution, user choice, and the sovereignty of local content ecosystems. The real story isn't about a button on a remote-it's about rewriting the default rules of a platform economy that has long favoured global giants over local Innovation. The announcement, captured in the 1News article titled "Lock it in: Govt wants local NZ apps on TV screens by default - 1News", has already sparked debate among broadcasters, tech vendors and consumer advocates. Yet much of the conversation has remained at the policy level, ignoring the gritty engineering realities of making it happen. As a senior engineer who has worked on embedded TV platforms and smart-TV app development, I want to unpack the technical, strategic. And competitive implications of this proposal. ---
The Proposed Mandate: What the NZ Government Wants to Achieve
The core of the proposal is straightforward: when a New Zealand consumer turns on a new smart TV, the initial setup wizard or the launcher screen should prominently surface locally produced apps alongside (or instead of) the usual array of Netflix, YouTube. And Amazon Prime icons. According to the government's press release, the objective is to "ensure Kiwi content is equally discoverable" and to support New Zealand's cultural identity in the digital age. This builds on earlier initiatives like the NZ On Air "Local Content on Connected Screens" fund. But now with the force of regulation behind it. In practice, this would require manufacturers-Samsung, LG, Sony, Hisense, and others-to modify their firmware or launcher software to include specific apps in the default row or carousel. The government hasn't specified whether these apps must be preinstalled or merely pinned to the home screen. Both approaches present distinct challenges. Preinstallation would require app stores to distribute the APK or WebOS package, while pinning could be accomplished via configuration pushed through the TV's update channel. The policy is currently in the consultation phase, with submissions open until mid-2025. It draws inspiration from the European Union's Digital Markets Act (DMA). Which mandates gatekeeper platforms like Google and Apple to allow alternative app stores and default choices. However, New Zealand's approach is more targeted: it focuses on a single screen context-the TV-and a specific category of apps (local broadcasters). ---Why Default Visibility Matters for Local Tech Ecosystems
In the world of platform economics, the default is a moat. Research by the University of Chicago's Booth School of Business has shown that default options in software interfaces can influence up to 80% of user choices, even when alternatives are just one click away. For local NZ apps, being buried three swipe layers deep in a "Apps" folder is functionally equivalent to not existing. When Netflix pays TV manufacturers for prime real estate on the home screen, it's not just advertising-it's buying the default. This is especially critical for New Zealand's small but new tech sector. Companies developing apps for local news, weather, tourism, or emergency alerts compete against global behemoths with unlimited marketing budgets. A default placement on the TV launcher would be a zero-cost distribution channel that could boost adoption from thousands to tens of thousands of active users. For developers currently struggling to justify the ROI of smart TV ports, this regulatory change could tip the balance. Consider the alternative: without intervention, the home screen tends to converge on a set of five to six global streaming apps, often dictated by revenue-sharing agreements between TV OEMs and media companies. The NZ government's move effectively forces these OEMs to renegotiate those deals to include local players-or to create an open slot in the launcher UI that can be dynamically populated based on region. ---Technical Challenges: From Set-Top Boxes to Smart TV Operating Systems
The devil is in the implementation details. And smart TV operating systems are a fragmented nightmare. The landscape includes at least six major platforms: Android TV/Google TV, LG webOS, Samsung Tizen, Roku OS, Apple tvOS and a long tail of Linux-based proprietary systems (Panasonic My Home Screen, Sony BRAVIA). Each has a different app store, different developer APIs. And different policies for how the launcher home screen is built. For example, on Android TV, the launcher is controlled by Google's "Android TV Core Services" which manages the channel row and can be modified via a "Recommendations" API, but not arbitrarily replaced. On Samsung Tizen, the launcher is hardcoded in the firmware and only customised via firmware updates-an expensive and slow process. LG webOS allows some customisation through its "webOS Launcher" but only for preapproved partners. Coordinating a consistent "default app row" across these ecosystems would require either a legislative mandate with penalties for non-compliance (like the DMA's fines) or a shared technical specification that OEMs can implement locally. Another challenge is the "guest mode" or "multiuser" support common in modern smart TVs. If a user logs in with a different profile, should the local apps still appear? Should they be removable? The government will need to define a clear baseline: mandatory presence, removable? Or should they be pinned until the user actively uninstalls them? This parallels discussions around browser default search engines-where Microsoft's EU compliance included a "choice screen" but allowed users to bypass it. The same tension will arise here. ---Parallels to the EU's Digital Markets Act and App Store Regulation
The DMA set a precedent for forcing gatekeepers to allow third-party app stores and alternative billing systems. New Zealand's proposal is narrower but no less significant. It essentially applies the DMA's philosophy to the hardware layer: TV manufacturers are gatekeepers of the living room screen. By mandating default local apps, the government is saying that the platform's home screen is a "core platform service" that must serve public interest, not just commercial maximisation. What's different, however, is that the DMA gives users a choice screen to pick defaults (e g., browser, search, assistant). NZ's proposal goes further by proscribing specific apps. This could be legally tricky-why select TVNZ+ over ThreeNow? Why include MΔori+ but not a local independent documentary app? To avoid accusations of picking winners, the government might need to establish a certification framework: apps that meet certain criteria (Kiwi-owned, NZ-focused content, free-to-air) get the default slot. This would require a review body, likely NZ On Air or the Commerce Commission, to maintain a whitelist that evolves with the market. The technical implementation of such a whitelist could use a signed XML file delivered via the TV's system update channel. Each OEM would need to parse the file and update their launcher UI accordingly. This isn't trivial-the update cycle for smart TVs can be 6-12 months, and many TVs never receive updates after the first year. The government would need to mandate ongoing support. Which might force a shift toward more modular launcher designs. ---The Developer Perspective: Opportunities for Local NZ App Builders
For New Zealand's relatively small community of smart TV developers-a niche even within the broader app development world-this policy could be a goldmine. Currently, developing for four TV platforms (Android TV, webOS, Tizen, Roku) to reach a local audience of ~1. 5 million households is a hard sell. The development cost per platform can range from $20,000 to $100,000, depending on feature complexity. With guaranteed visibility, the return on that investment suddenly makes sense. Moreover, the mandate could spur innovation in areas beyond streaming. Imagine local navigation apps (e. And g, AA Maps), weather apps from MetService. Or even interactive public information services-all surfaced on the TV by default. Developers could use standard web technologies (like HbbTV or W3C Web App Manifest) to build once and deploy across multiple TV operating systems, taking advantage of the [web TV API standards](https://developer mozilla org/en-US/docs/Web/API/Media_Session_API) now maturing. However, there's a risk of a "race to the bottom" in engineering quality. If developers rush to meet the certification criteria without proper testing, users may blame the government or the TV brand for a poor experience. The certification framework must include usability guidelines-minimum load times, crash rate thresholds. And accessibility standards. The [RFC 2119](https://datatracker, and ietforg/doc/html/rfc2119) specification for "must", "should". And "may" could serve as a template for writing unambiguous requirements. ---Privacy, Security, and the Risk of Bloating Default Screens
Default apps that can't be removed by the user raise privacy concerns. Local apps may request permissions to access location, viewing history. Or even microphone data (for voice search). If a user never launches the app, why should it retain those permissions? The government must mandate that default apps don't run background services or collect telemetry until first launch-similar to the App Store's "background app refresh" default-off policy. Furthermore, bloatware is a real UX problem. Add too many mandatory icons and the home screen becomes cluttered, degrading the experience for which users paid. The government should limit the default set to a maximum of three or four apps. And allow OEMs to include an "other local apps" folder or carousel that groups all certified apps. This could be implemented via a dynamic list backed by a [JSON Web Token (JWT)](https://datatracker ietf org/doc/html/rfc7519) signed by the regulatory authority, ensuring that only trusted apps appear. Security updates for these default apps also fall into a grey zone. If a TV manufacturer stops providing updates, the local app may become vulnerable. The policy should require that the app distributor (e. And g, TVNZ) provides updates through the TV's standard app store, not through side-loading. This aligns with industry best practices for OTA updates as defined in the [TV Alliance's security recommendations](https://tv-alliance org). ---How This Could Reshape New Zealand's Digital Infrastructure Strategy
Beyond the immediate goal of content discoverability, this proposal fits into a broader vision of digital sovereignty. New Zealand's reliance on global cloud infrastructure (AWS, Azure) and platform monopolies (Google, Apple) has been a growing concern. By securing default visibility on the screen that sits in nearly every home, the government is planting a flag: local digital services should be as accessible as international ones, without requiring a subscription or a vpn. This could catalyse investment in local streaming infrastructure, CDN edge nodes. And app development talent. It also puts pressure on broadcasters to deliver apps that match the performance and UX polish of global competitors. If a default local app loads slowly or crashes, it damages trust in the entire initiative. Engineers at TVNZ, Sky. And MΔori Television are likely already upgrading their app stacks-considering Kotlin Multiplatform, React Native. Or native SDKs for each TV OS. In parallel, the policy creates a rationale for a national app store for TV-similar to what Australia's ABC has explored. A centralised repository of local apps could simplify manufacturing compliance: OEMs would only need to integrate one "NZ Apps" launcher that pulls from this store. The store itself could be a Progressive Web App (PWA), reducing the need for platform-specific approvals. Check out our previous analysis on PWAs vs native TV apps for a deeper technical comparison. ---A Call to Action for the Tech Community
The consultation period is open. And the government has explicitly asked for technical input. Now is the time for New Zealand's technology community-developers, architects, product managers-to submit detailed feedback. We need to address questions like: - What is the minimal viable API surface for a TV manufacturer to support dynamic defaults? - How can we ensure backward compatibility with older TVs that lack update capability? - Should the mandate apply only to new TVs or also to existing ones via software updates? - How do we handle the case of TVs that are region-agnostic (e, and g, imported models)? Without technically informed submissions, the policy risks being watered down into a symbolic recommendation that OEMs can ignore. Or worse, a heavy-handed specification that increases costs without improving discoverability. I urge every engineer reading this to visit the MBIE consultation page and share their insights. The future of local digital infrastructure depends on getting the defaults right. ---Frequently Asked Questions
- Will I be forced to use TVNZ+ even if I never watch it?
No. The proposal would place local apps on the home screen. But you can still uninstall or hide them after initial setup. The goal is visibility, not mandatory usage. - Will this affect my existing smart TV?
Most likely not. The mandate is expected to apply to new TVs sold after a certain date. However, if your TV receives firmware updates, manufacturers might push a launcher update that adds the default apps. - What apps are likely to be included?
TVNZ+, ThreeNow, and MΔori+ are the most probable candidates, given they're free-to-air and publicly funded. Independent NZ streaming services may qualify under a certification process. - How do the technical costs get passed on?
Manufacturers may pass the cost of firmware modifications to consumers (i, and e, a small price increase per TV). Alternatively, the government could subsidise development through the NZ On Air fund. - Is this the same as the EU's "choice screen"?
Similar but not identical. The EU gives users a choice of default browser; NZ mandates specific local apps. NZ's approach is more direct and less user-driven. Which may raise legal debates.
What do you think
If the government requires TV manufacturers to include local apps, should the same principle apply to streaming sticks like Chromecast and Apple TV that operate on separate app ecosystems?
How should the certification process decide which apps are "local" when many streaming services (e g., Netflix) now produce NZ-original content,
.
Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today β