
Alex Russell
Alex is Partner Program Manager on the Microsoft Edge team and Blink API OWNER. Before joining Edge in 2021, he worked on Chrome’s Web Platform team for a dozen years where he helped design many new features. He served as overall Tech Lead for Chromium’s Project Fugu, lead Chrome’s Standards work, and acted as a platform strategist for the web. He also served as a member of ECMA TC39 for more than a decade and was elected to three terms on the W3C’s Technical Architecture Group.
His technical projects have included Fugu, Progressive Web Apps, Service Workers, and Web Components, along with ES6 features like Classes and Promises. Previously he helped build Google Chrome Frame and led the Dojo Toolkit project. Alex plays for Team Web.
Building Bridges to a Post-SPA Future
React Summit 2026
Upcoming
Building Bridges to a Post-SPA Future

SPAs were always based on contingent logic. For the benefits to materialise, users must spend a great deal of time in the same interface, updating state in-place. This never described the majority of experiences, where very little is persisted across screens and critical user journeys. As the industry moves away from SPAs and the frameworks they popularised, one of the largest hurdles for teams rethinking their approach is retaining the trust of managers who previously signed off on the very SPAs that now feel slow and shabby. Getting management on board with View Transitions isn't just a technical hurdle, it's an organisational journey. This talk boils down the types of evidence and approaches that help senior leaders develop confidence in the new analysis, making the post-React world feel attainable.
Frontend’s Lost Decade and the Performance Inequality Gap
JSNation 2025
32 min
Frontend’s Lost Decade and the Performance Inequality Gap
Top Content

The promise of the web is universal access to services across OSes and devices without gatekeepers, but like all systems, the web isn't what it promises – it's what it does. And today, the web is increasingly exclusionary. The roots of this exclusion are a mismatch between the reality of the hardware and networks users access our services from versus our expectations of those same devices and networks. The trends that put wind into JavaScript's sails on the client side in the early 2010's have long since stopped blowing. So, what now? This talk digs into the network and device reality we must confront, and why our future as web developers depends on what we do here and now.