Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. But AI coding agents have none of those needs. An agent writing against the web platform directly can produce a list component in ~20 lines, ship without a package.json, bundler, or transpiler, and use an import map instead. This also eliminates lockfiles and transitive dependency graphs, which matter more with agents because package auditing is the first review step to disappear. The web platform is closing the gap with frameworks faster than ever: custom elements power GitHub, YouTube, Photoshop on the web, SAP UI5, and Adobe Spectrum. React 19 added proper custom element support, signaling frameworks moving toward the platform. For what standards don't cover, lit-html handles templating at a few KB and a simple unidirectional store handles state — neither locks the app in. Custom elements also expose a stable, specified interface (attributes, properties, events, slots) that an agent can drive without versioned documentation, unlike React props that shift between major versions.
Questions this post answers
Why would an AI coding agent prefer native web platform APIs over React or Vue?
Frameworks like React and Vue were designed for human readability, shared conventions, and career value — none of which matter to an agent. An agent writing against the web platform can ship without a package.json, bundler, or transpiler, using an import map instead. It also avoids lockfiles and transitive dependency graphs, which agents tend to expand unchecked. Custom elements expose a stable, specified interface an agent can drive without versioned documentation. Teams shipping agent-generated frontends track the web standards vs. framework tradeoffs on daily.dev.
What is the minimal alternative to a full JS framework when building with web components?
Templating can be handled by lit-html at a few KB, and state management by roughly a hundred lines of unidirectional store code. Neither locks the application in. An import map resolves imports so what the browser loads is what is on disk, eliminating the install step, lockfile, and postinstall scripts entirely. Developers moving toward leaner frontend stacks find the relevant web standards coverage on daily.dev.
Which major sites use custom elements in production?
GitHub, YouTube, Photoshop on the web, SAP UI5, and Adobe Spectrum all use custom elements to carry their interfaces. React 19 added proper custom element support, indicating that major frameworks are moving toward the platform rather than away from it. Developers evaluating custom elements for production use follow adoption signals like these on daily.dev.