Latest / Wpfavs - Your favourite WordPress news / Why WordPress Plugins Die: Feature Creep, AI, and Onboarding

Transcript

Why WordPress Plugins Die: Feature Creep, AI, and Onboarding · Wpfavs - Your favourite WordPress news

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