Why WordPress Plugins Die: Feature Creep, AI, and Onboarding
The hosts break down why so many WordPress plugins get abandoned, arguing that feature creep and unsustainable freemium models are killing maintainability. They also debate the future of onboarding and plugin architecture, from polished setup wizards to native AI-ready endpoints and zero-middleware workflows.
Chapter 1
Reliability Over Feature Creep The Onboarding and UX Revolution
Nick d
So, um, last time we were talking about how site owners end up accumulating all these abandoned utility plugins. But if you look at it from the developer side, the, the numbers that came out in that WP Goldmine report are just staggering.
Ido
Wait, which, which specific stat are you looking at?
Nick d
The, the whole dataset. They analyzed fifty seven thousand three hundred and eighty three plugins on the WordPress Org directory, and in the ten thousand to one hundred thousand active install tier, twenty four percent of them haven't been updated in over two years.
Ben cohen
Twenty four percent!
Nick d
Yeah! That's, that's twelve hundred and nine popular plugins with real user bases that are just sitting there with no maintainer. Even in the hundred thousand to one million band, it sits at ten point two percent abandoned. Tools like Limit Login Attempts or Layout Grid Block, just left on the vine.
Ido
And, and the trap people fall into is thinking those plugins died because they ran out of features, right? But it's actually the exact opposite. It is feature creep that exhausts the maintainers until they just throw up their hands and walk away.
Nick d
Mm, completely. When I was building WPfavs, that was the big lesson. Site builders do not want an all in one monster plugin that injects twenty options pages into wp admin and bloats the DOM footprint. They want predictable, single purpose tools that do one job cleanly and get out of the way.
Ido
Okay, but, but Nick, you still have to onboard the user! Look at tools like FluentCart or Melapress that are actually growing right now. They don't just dump you into a settings page. They ship polished three step visual setup wizards, interactive guides, native block editor integration, so you know exactly what the plugin is doing from minute one.
Ben cohen
Wait, wait, I, I have to jump in here, Ido. A setup wizard? In 2026?
Ido
Yes! A clean visual wizard!
Ben cohen
No way. Nobody building sites today wants to click through a seven step modal wizard to toggle checkboxes. Site owners expect AI agents to configure plugin settings quietly in the background without manual wizard steps at all. The entire concept of manual UI onboarding is rapidly becoming obsolete.
Nick d
Well, um, let's not jump ahead to full automation before the basic code is even reliable, Ben. Whether it's a wizard or a background config, if the core execution is messy, people notice real fast.
Chapter 2
Sustainable Business Models and Native AI Architecture
Ido
That actually ties right into why so many of these mid tier plugins die in the first place. That ten point two percent abandonment rate in the hundred thousand plus tier comes directly from legacy freemium models where creators gave away massive feature sets for free without a sustainable revenue path.
Nick d
Right. If you don't have recurring subscription income or serious commercial backing, like what we see highlighted around community initiatives like The WP Awards 2026, you simply cannot sustain years of security patches and updates. The math doesn't work.
Ben cohen
And, and if we're talking about long term sustainability, we have to talk about how plugins are actually architected for the next five years. Look at what Benjamin Intal demonstrated with the Ahentic AI workspace experiment, or what Novamira CLI is doing right now.
Ido
The zero middleware approach, right?
Ben cohen
Exactly! Zero external servers, no third party Model Context Protocol bridges needed. Just WordPress, native PHP execution, and direct core APIs. Ahentic can understand the entire website structure, launch pages, and install plugins using nothing but native WordPress endpoints.
Ido
Which means any coding agent, whether it's Claude Code or Gemini CLI or Codex, can execute commands against the site securely through native channels.
Ben cohen
So my thesis is simple: if you are launching a WordPress product in 2026 and you don't expose native, AI readable endpoints right out of the box, your product is instantly obsolete. You are building for 2018.
Nick d
I, I, I really have to push back hard on that, Ben.
Ben cohen
How can you push back on that?
Nick d
Because rock solid core execution, squeaky clean code, and zero external dependencies will always outlast hyped up AI integrations. Every time WordPress core APIs shift or an AI protocol gets rewritten, those fragile AI wrappers break. A plugin that does its core job with total reliability will be standing long after the hype cycles wash out.
Ido
Hmm. Sounds like we have two very different visions for what keeps a plugin alive in 2026. Clean utility on one side, AI native hooks on the other.
Ben cohen
We will see which ones are still updated two years from now.
Nick d
Fair enough! Good chatting, folks.