Front-end is dead in the sense that hand-crafting pages is ending.
But long live front-end engineering with AI as the translator of intent into code. The craft shifted from implementing pages to designing systems that let pages be generated reliably. From making, to enabling making. That’s the argument from The Death of Front-end Development and Front-end Composability, brought down to a choice.
For PMs and strategic product designers, the door is open. Keep waiting for engineering bandwidth, or spend two hours this week building something.
For front-end developers and UX/UI designers, the job is forking.
- Path 1: Own the composability domain. Own primitives, workflows, and guardrails. Less direct making, more leverage, with AI-powered control over the design system. Craft knowledge becomes context for setting constraints and embedding taste into the product. This is going to be the new default UI work.
- Path 2: The highly crafted experience. Polished consumer products still need custom rendering, intricate interactions, and performance tuning. AI-generated interfaces still need humans evaluating and improving every line. This is a specialist niche of AI evals for now, not yet the default experience.
Both builders and implementers need each other. Product leaders without composability get chaos. Designers and developers without business context, clear intent, and a correct direction become isolated and irrelevant.
I sit on the first path most days, and I still need the second. In the cybersecurity products I work on, the system has to let an agent assemble an asset, vulnerability, and remediation flow without inventing a new table every time. The moments that decide whether an operator trusts the alert still need a human who has watched that job. Path 1 without path 2 is a consistent product nobody believes. Path 2 without path 1 is a beautiful screen the next agent will contradict.
The builders finally got their tools. Not perfect tools. Chaotic, non-deterministic, sometimes maddening tools. But enough to change who gets to create.
If you haven’t tried Claude Code or something like it, start today. Not because your job is at risk. Because you’re missing the most interesting shift in how software gets made.
Start with a problem you understand, and test what you build with every person who would validate the value.
The real unlock isn’t the tool. It’s the mindset: you’re not learning to code. You’re learning to direct systems that code for you.
With AI, the implementation barrier for digital interfaces is gone. You still have to know what to ask.
Also in February: The Death of Front-end Development · Throwing Away the Prototype · Front-end Composability
Continues in March with Design Leadership Has Evolved.
Daniel Arevalo is Product Experience Lead at Omny Security. He builds AI-native tools and writes about design, product leadership, and what it means to direct systems that execute at a speed humans never had before.