Filmin

Filmin

From Angular to React

Changing the engine mid-flight.

When I joined, the TV app was built in Angular and tied to an older project, with years of special cases for televisions that disagreed with each other. Today it's fully React — and we got there without ever stopping releases.

Role
Migration
Period
2024 — 2025
Stack
Migration · Refactor · Build tooling
100%React today
0Release freezes
1Codebase at the end

The problem

A rewrite nobody could pause for

The comfortable way to change frameworks is to stop everything and do only that. A streaming service can't: new features, device certifications and fixes all keep their own calendar. So the migration had to happen inside our normal release rhythm, or not at all.

The approach

Sequence over speed

First we untangled the app from the older project so it could stand on its own. Then we moved it piece by piece, with both frameworks living in the same build until the last Angular view was gone. Every piece that crossed over left some of its special cases behind.

The result

Quietly done

Angular is gone. One React codebase ships to every television at once, and the energy we used to spend keeping two worlds alive now goes into the product.

My partPlanning and doing the migration
AlongsideFeature work that never stopped
RhythmRelease by release, no freeze
Built withReact, with Angular beside it until the end