The Netherlands' most popular mystery format. One app. No room for error on broadcast night.

Wie is de Mol? is one of the Netherlands' most popular and longest-running reality formats. Every episode triggers a surge of viewer engagement: theories, discussions, and in-app interactions that spike precisely when the broadcast airs. The app is not a companion feature; it is a core part of how fans experience the show.

The technical challenge is similar to Eurovision: predictable, concentrated peak load with zero tolerance for failure during broadcast. The backend architecture developed for Wie is de Mol? became the foundation Elements later used for the Eurovision Song Contest app.

A broadcast-synced fan experience

The app allows viewers to track suspects, build theories, and follow the narrative across the season. Content updates are timed to the broadcast, keeping the app in sync with what is happening on screen. This requires the same kind of scenario-driven backend logic used in live voting apps: states that change at specific moments, driven by a show timeline rather than user action.

A scalable backend built for television peaks

When an episode airs, the backend sees a sharp traffic spike within minutes. The architecture was designed to absorb these peaks without pre-provisioning for peak capacity year-round. The patterns developed here, event-driven autoscaling, decoupled content and interaction layers, broadcast-synced state management, were refined and reused in the Eurovision Song Contest infrastructure.

Native iOS and Android

The app is built natively on both platforms. For an entertainment app where performance and responsiveness are part of the experience, native development ensures the app feels right at every moment, including the frantic seconds after a plot twist.

Why native, and why a decoupled backend?

The same reasoning as Eurovision: an app that is central to how millions of people experience a live broadcast cannot afford abstraction layers between user actions and the response. Native on the client, decoupled on the backend, with broadcast-state management sitting independently from the content layer.

Elements has worked with AVROTROS across multiple formats such as 'EenVandaag app','Opgelicht app', 'Radar app' and 'Mindfuck app', building deep familiarity with the constraints of broadcast-synced app development. Each season brings new content and feature requests, handled by a stable team that understands both the technical requirements and the production workflow.