Latest / Wpfavs - Your favourite WordPress news / Why Lean Plugins Win in 2026
Transcript
- 0:13You, you know, I was looking at a client dashboard yesterday,
- 0:16and er, before I could even see the site health widget, there were four different
- 0:21full width upsell banners, a popup asking me to rate a form plugin,
- 0:25and a notice that my, my database needed optimizing.
- 0:29It is just absurd.
- 0:31It, it really is.
- 0:32As someone who built wpfavs specifically to manage tool collections and eliminate
- 0:38that chaos, it drives me crazy.
- 0:41Plugins used to do one job well.
- 0:43Now every single micro utility wants to be an all in one marketing platform,
- 0:47injecting scripts into every page of the WP admin DOM and bloating the wp options
- 0:53table with persistent transient clutter.
- 0:55Right!
- 0:56And when you look at what is actually succeeding right now,
- 0:59like, look at Melapress with WP Activity Log or FluentCart.
- 1:04They take the exact opposite approach.
- 1:06They focus on executing lean, rock solid core functions without trying to hijack
- 1:12your entire dashboard.
- 1:14Exactly.
- 1:15Users are exhausted by feature creep.
- 1:17They want speed and predictability.
- 1:20When you install a tool, you do not want it dropping thirty background cron jobs and
- 1:25requiring mandatory account registration just to toggle a basic setting.
- 1:29And then, when you deactivate it?
- 1:32Half of them leave megabytes of orphan tables behind in your database.
- 1:35Oh, the lingering uninstaller waste, yeah.
- 1:38That is a massive pain point.
- 1:39But what about the visual side?
- 1:41A lot of developers argue that building these massive, custom React dashboard
- 1:45interfaces is what makes a plugin feel modern in 2026.
- 1:49I think those elaborate custom React builds are often a massive trap.
- 1:53They look flashy in a demo video, sure, but they create huge technical debt.
- 1:58Look at WordPress 7.1.
- 2:00Core is moving the post editor into a full iframe isolation.
- 2:04If your custom admin interface relies on fragile DOM overrides or global window
- 2:09hooks instead of native block and core APIs, guess what happens?
- 2:13It breaks the second a core update drops.
- 2:16Mm, yeah, completely.
- 2:18Brittle design gets exposed real fast when platform architecture shifts underneath
- 2:22it.
- 2:22And that structural stability is becoming even more critical now that AI agents are
- 2:27actually operating inside WordPress.
- 2:29If an AI assistant cannot read your plugin state, the UI gloss does not matter at
- 2:34all.
- 2:35That is the huge shift.
- 2:36Look at what Benjamin Intal did with the Ahentic AI workspace experiment.
- 2:41It manages the whole site, launches pages, installs plugins,
- 2:45but it does it without external servers or proprietary middleware.
- 2:49It relies purely on native WordPress core APIs and clean schemas.
- 2:54Or look at Novamira CLI, letting terminal coding agents like Claude Code or Gemini
- 2:59CLI run shell commands directly against your site.
- 3:02That clean API surface is what makes a plugin future proof for AI discovery and
- 3:07automation.
- 3:08But, okay, let us talk about the economic side of keeping plugins clean and updated,
- 3:12because software does not maintain itself for free.
- 3:15Have you seen Chris Morris's analysis of the plugin directory?
- 3:18I did, yeah.
- 3:19Out of over fifty seven thousand plugins in the index, forty five point six percent
- 3:24have not been updated in over two years.
- 3:26That is essentially abandoned code sitting on live sites.
- 3:29And what caught my eye was the middle tier.
- 3:31In the ten thousand to one hundred thousand active install band,
- 3:35twenty four percent of plugins are abandoned.
- 3:37That is over twelve hundred popular tools running on real production sites with zero
- 3:42active maintainers.
- 3:43Why do you think that middle tier collapses so often?
- 3:45Because of broken monetization models, honestly.
- 3:49Creators launch with a lifetime deal or a super generous freemium tier,
- 3:53get a surge of users, and then two years later they are overwhelmed with support
- 3:57tickets and zero recurring revenue to hire help.
- 4:01To survive in 2026, plugins need sustainable, transparent recurring pricing or
- 4:06modular paid add ons.
- 4:08Otherwise, staleness is almost inevitable.
- 4:11Which brings us to how we actually pick tools today.
- 4:13If you are building a production site right now, what is your single non negotiable
- 4:18test before adding a plugin?
- 4:19Mine is clean database behavior and native API exposure.
- 4:23I check if it uses standard WP options and custom tables properly,
- 4:27and whether it cleans up after itself on uninstall.
- 4:30What about you?
- 4:31For me, it is AI readability and standard core hooks.
- 4:35I inspect what a site looks like to AI assistants and agents.
- 4:39If a plugin buries its data behind proprietary JavaScript rendered admin frames
- 4:44where an agent or parser cannot inspect the schema, it is an automatic pass for me.
- 4:50That is a great filter.
- 4:51Build lean, respect the database, expose clean APIs, and keep it maintained.
- 4:57That is how software wins now.
- 4:59Simple as that.
- 4:59Good chat today, talk soon!