PERSON / ENGINEER / AUTHOR
Partner Product Architect - Microsoft Edge
"The web is not what it promises. The web is what it does."
In June 2015, Alex Russell published a blog post called "Progressive Apps: Escaping Tabs Without Losing Our Soul." He and his wife Frances Berriman had been looking for a word to describe a new class of web applications - ones that loaded fast, worked offline, and felt native without being locked in an app store. They landed on three words: Progressive Web Apps. The term stuck. The movement exploded. The abbreviation PWA is now part of every front-end developer's vocabulary. That is the kind of naming that changes how an entire industry thinks.
But Russell is not a brand strategist or a marketer. He is an engineer who spent 13 years at Google building the plumbing of the modern web, and who now sits at Microsoft as Partner Product Architect on the Edge team and as a Blink API OWNER - the person who says yes or no to new capabilities landing in one of the world's most-used browser engines. The scope of his fingerprints on the web is genuinely hard to overstate.
Service Workers - the technology that makes offline web apps possible - he helped design and deliver. ES6 Promises, ES6 Classes, async/await - Russell was TC39's representative pushing those features through standardization for a decade. Web Components, Push Notifications, Web Bluetooth, Background Sync, Persistent Storage, Project Fugu - the list of web platform capabilities he shepherded into existence reads like a glossary of modern web development.
Before Google, he co-created Dojo Toolkit in 2004, one of the first serious JavaScript UI frameworks at a time when the industry was still arguing about whether JavaScript was a real language. He led Dojo development at Informatica, ran R&D at SitePen, and did rich web UI work at JotSpot. He arrived at Google in 2008 already knowing more about making the web perform than most engineers learn in a career.
What makes Russell unusual in the web standards world is the combination of builder and critic. He can ship the spec and then write 5,000 words explaining why the ecosystem is misusing it. His newsletter, Infrequently Noted, is not comfort reading. It is a sustained argument - backed by CrUX data, device market statistics, and a decade of partner work - that the web development community has spent the last decade optimizing for its own convenience while the majority of the world's internet users got left behind on budget Android devices with slow connections and CPUs that cannot run a modern React app at any acceptable speed.
"If the web is going to succeed, it has to succeed on the dominant form factor, which is mobile today."
- Alex Russell, on the performance inequality gap
Panel 1 of 3 - "Origin Story"
Panel 2 of 3 - "The Build"
Panel 3 of 3 - "The Reckoning"
Co-created Dojo Toolkit, one of the first serious JavaScript UI frameworks, establishing him as a major voice in the emerging web platform community.
Director of R&D at SitePen while continuing to lead Dojo development; built a reputation as both a practitioner and a thinker in the web standards space.
Joined Google as a software engineer on Chrome, Blink, and the web platform - beginning the most productive chapter in his standards career.
Co-authored the Extensible Web Manifesto, reshaping the philosophy of how the web standards community should expose platform primitives. First elected to the W3C Technical Architecture Group.
Published "Progressive Apps: Escaping Tabs Without Losing Our Soul," coining the term "Progressive Web Apps" with Frances Berriman. Appointed as Chrome's first Web Standards Tech Lead.
Led delivery of Service Workers, Push Notifications, Web Components, Web Bluetooth, PWA installability, Background Sync, Persistent Storage, and Project Fugu - as Chrome's Web Standards TL.
Left Google after 13 years. Joined Microsoft as Partner Product Architect on the Edge team and Blink API OWNER - bringing a decade of Chrome perspective to Microsoft's browser.
Continues the annual "Performance Inequality Gap" series, publishing browser antitrust analysis, and advocating through Infrequently Noted for a web that works for the world's majority of users on budget devices.
The web is not what it promises. The web is what it does.
Native ecosystems want to eat your lunch... we are handing our enemies a gift.
Users get a vote. They'll download native apps if websites perform poorly.
Design work happens outside committees.
Every year since 2019, Alex Russell has published a post called "The Performance Inequality Gap." Every year it says roughly the same thing: developers are building for devices they own and networks they live on, while most of the world's internet users are on Android phones costing under $200, on 3G connections, in markets where data is expensive. The gap between what developers test on and what users experience is not a rounding error. It is a different universe.
The 2026 edition of the report is not optimistic. Despite years of tooling improvements - Lighthouse, Core Web Vitals, PageSpeed Insights - fewer than half of web origins pass Core Web Vitals for mobile users. Russell's prescription is blunt: at the global P75 of devices and networks, developers can afford approximately 150KiB of HTML/CSS/fonts and 300-350KiB of JavaScript (gzipped). Most modern React apps ship more than that before they load a single line of application code.
His critique of React in particular - documented in the November 2024 post "If Not React, Then What?" - is not about React being technically wrong. It is about the entire ecosystem defaulting to a framework designed for Facebook's infrastructure, on the assumption that Facebook's constraints apply to everyone. They do not. He spent over 100 partner engagements watching teams remediate performance and accessibility problems that React-based stacks had introduced, and he concluded that the majority of developer-experience gains have been paid for by user-experience losses on the devices most users actually have.
His solution is not a specific framework. It is a culture change - one where performance budgets are enforced, where architectural decisions are validated by prototype bake-offs rather than framework popularity, and where teams ask not "is this fast on my dev machine?" but "is this fast on a 2021 Snapdragon 665 on a 3G connection in Indonesia?"
The second front in Russell's ongoing argument is structural. He believes the web's performance problem cannot be solved by developers alone, because the environment in which developers operate - iOS's restrictions on browser engines, Apple's underfunding of Safari relative to its $22 billion in annual web revenue, the lack of meaningful browser competition on the dominant mobile platform - makes full-stack improvement impossible without regulatory intervention.
His April 2026 post, "The Web Is An Antitrust Wedge," argues that tech press and regulators are misframing the problem when they treat browsers as utilities. Browsers are app stores, he contends - and treating them as such in antitrust law would unlock the same kind of competition for the open web that regulators are trying to mandate for native apps.
He names Open Web Advocacy (OWA) as a concrete way developers can participate in that structural fight, and he consistently connects the abstract regulatory argument back to concrete user outcomes: if developers had a real second browser engine choice on iOS, they could ship apps that worked for users who cannot afford iPhones. The political and technical are not separate arguments for Russell. They are the same argument from different angles.
He holds the argument without apology, even when it makes him unpopular at conferences where the audience is there to learn React. He is not building consensus. He is building a record, and watching the data either vindicate or falsify his predictions year over year. So far, the data keeps showing up for him. The gap is not closing.
Coined "Progressive Web Apps" with Frances Berriman in 2015 - a term that reframed how the industry thinks about web applications vs. native apps.
Led the Service Workers specification and implementation - the primitive that makes offline web apps, background sync, and push notifications possible.
TC39 representative for a decade - pushed Promises, Classes, async/await, and other ES6+ features from proposal through standardization.
Delivered Web Components as a web standard - the platform-native component model that every major framework now interoperates with.
Three-time elected member of the W3C Technical Architecture Group (2013-2019) - the body that reviews new web platform proposals for architectural coherence.
Co-authored the Extensible Web Manifesto (2013) - the document that shifted the web standards philosophy toward exposing low-level primitives over high-level abstractions.
Co-created Dojo Toolkit in 2004 - one of the first serious JavaScript UI frameworks, used at IBM and across enterprise web applications.
Started and led Project Fugu - Google's initiative to close the capability gap between web and native, delivering Web Bluetooth, File System Access, and dozens more APIs.
Publishes the annual "Performance Inequality Gap" - the most-cited annual report on the real-world performance state of the web, tracking what users actually experience vs. what developers build for.
Says what he thinks the data shows, even when the room disagrees.
Cuts through abstractions to the structural and economic root of technical problems.
Left organized religion as part of his intellectual evolution. Applies the same scrutiny to technical dogma.
Succeeded without a CS degree and names luck before perseverance when explaining it.
Advocates for work-life balance and credits his wife Frances with teaching him time management.
Genuinely angry on behalf of the world's internet users who can't afford a Macbook Pro.
The critique is always backed by shipped code - he has never just criticized from outside.
Has been making the same performance argument for a decade and shows no signs of stopping.
His newsletter is called "Infrequently Noted" - a self-deprecating joke about how often he publishes. He publishes quite a lot.
He and Frances Berriman coined "Progressive Web Apps" as a married couple working through ideas together - not in a corporate brainstorm or a standards meeting.
His GitHub handle is "slightlyoff" while his Twitter/X handle is "slightlylate" - a subtle discrepancy that has confused people for years. Both are him.
He succeeded at Google without a formal CS degree, and is notably candid about it - crediting luck before perseverance whenever the topic comes up.
His annual Performance Inequality Gap report is essentially a gift to budget-conscious developers worldwide: it tells you exactly how many kilobytes you can spend to reach the global majority of users.
He calls AI systems "tiny little liars" and "token predictors" - a position he holds with the same evidence-first rigor he applies to browser performance budgets.
The moment "Progressive Web Apps" was named did not happen in a Google conference room with a whiteboard and a product manager. It happened in a conversation between Alex Russell and his wife Frances Berriman. They were trying to describe a class of apps that loaded progressively, felt native, worked offline, and could be installed - without being trapped in an app store. Frances landed on the name. Alex published the blog post. The web development world had a new vocabulary word by morning.
- The naming of PWAs, June 2015Russell has spoken openly about a period of existential questioning in his mid-20s - asking himself whether the work he was doing had moral value and leaving organized religion as part of that intellectual evolution. He connects this directly to why he cares so much about who the web serves. The question he was asking about his own life - "does this matter to people who aren't like me?" - is the same question he now asks about every front-end architecture decision.
- On finding a moral framework for technical workAfter 13 years at Google, Russell moved to Microsoft - a move that surprised people who associated him with Chrome. His explanation was pragmatic: he wanted to keep influencing the Blink engine, which both Chrome and Edge share, and Microsoft gave him a position that let him do that while also working on Edge's distinct platform strategy. He remained a Blink API OWNER - the same technical role - across the company change. The browser stayed the same. The paycheck changed.
- On leaving Google for Microsoft in 2021His feedback on developer conference talks is legendary for its specificity. Russell does not do vague encouragement. He will tell you exactly which claim in your talk contradicts the CrUX data, and he will probably have the percentile already memorized. He attributes his time management and the discipline not to burn himself out doing this to Frances Berriman, who he credits with teaching him how to maintain work-life balance in an industry that does not naturally encourage it.
- On the discipline behind the output"The Web Is An Antitrust Wedge" - Argues that regulators and the tech press are missing the opportunity to recognize browsers as app stores, which would unlock real web competition against mobile duopolists.
"Naked Power" - Addresses Apple and Google's moral failures on content moderation, specifically the Grok scandal, and critiques their monopolistic justifications around security, privacy, and fraud prevention.
"The Performance Inequality Gap, 2026" - Annual report finding fewer than half of web origins pass Core Web Vitals for mobile. Budget for global P75 user: ~150KiB HTML/CSS/fonts + 300-350KiB JS (gzipped).
"11ty Hacks for Fun and Performance" - Deep dive into his own site's optimization techniques using the 11ty static site generator.
"If Not React, Then What?" - Reflection on 100+ partner engagements showing React-based stacks dominate remediation work for performance and accessibility problems.
"Platform Strategy and Its Discontents" - Analysis of how browser platform strategy shapes the web ecosystem and where the leverage points for change actually are.