Front-end Microservices for Video
Cristóbal Valenzuela, CEO of Runway, on rethinking the primitives of video
This points to a stack shift where browser apps stop building core interaction plumbing themselves and start buying it as reusable infrastructure. In practice, that means a video tool like Runway can spend its engineering time on AI editing and rendering, while using off the shelf pieces for real time collaboration, playback, comments, and other common browser behaviors. That is the same specialization pattern that turned back end software into services and APIs.
-
Runway describes video creation in the browser as a shared document workflow, where versioning, asset sharing, and multiplayer editing are built into the medium. It also draws a clean line between commodity layers and proprietary ones, buying adjacent services where possible while keeping its rendering and model stack in house.
-
The clearest analogy is Figma. Browser based design only broke out once the web could support native feeling performance and live collaboration. WebAssembly helped close the speed gap, and multiplayer in the browser changed who could participate in the workflow, from specialist designers to broader teams.
-
In video, the old workflow is fragmented across tools for review, file transfer, hosting, and editing. Frame.io handles time stamped comments and approvals, Mux abstracts video delivery infrastructure, and Runway aims to collapse more of that chain into one product. That is what front end microservices really means here, modular building blocks below a more integrated user experience.
The next phase is creative software behaving less like installed desktop suites and more like cloud products assembled from specialized services. That lowers the cost to launch new tools, speeds up product iteration, and pushes competition upward toward workflow design, model quality, and distribution rather than raw front end engineering.