Skip to content

[00]

Why a suite and not one plugin

Seven plugins cost more to build and more to market than one plugin with seven feature tabs. Here is what we get back for that.

Written by
The Subset team
Reading time
2 min
Tags
product

The cheaper way to build Subset would be one plugin with a tab for each feature. It’s also what the WordPress plugin directory rewards, since most of its biggest names are a single install with a long settings page. We build seven separate plugins instead, mostly so that a bug in one of them can’t take the others down with it.

Failures stay in one plugin

WordPress has no way to switch off part of a plugin. When PHP hits a fatal error, WordPress disables the plugin the error came from, and if the error happens early enough it takes the whole site with it. There’s no supervisor process and no per-feature sandbox to catch it.

That makes the plugin boundary the only isolation WordPress offers. If image conversion and cookie consent shared a plugin, a fatal error in the image code on a new PHP version would turn off the consent banner on every site running that version. Tracking scripts the banner was holding back would load for every visitor until someone noticed. As separate plugins, the same error costs you image conversion and nothing else.

A site running all seven has seven places a failure can start, but each one only breaks its own feature.

You load what you installed

A plugin that resizes images, manages consent and handles redirects ships all of that code to every site. A site that only wanted redirects still loads the image and consent code, and there’s no setting to opt out of it.

With separate plugins, a site that installs Redirector gets Redirector’s code and the shared Subset library. Nothing from the other six appears in its admin screens, its database tables or its page weight, and you can confirm that on your own site by looking at what’s installed.

What it costs us

Seven plugins means seven readmes, seven support forums, seven sets of screenshots and seven release processes. It also means seven separate discovery problems. Someone searching the directory for redirects finds Redirector, and nothing in that listing points them to the other six. The bundle needs its own page to explain itself, and most people who arrive through one plugin don’t want the rest.

The cost that shapes the code most is the shared library. Settings storage, the Subset admin menu, and Pro’s licence checks and updates work the same way in every plugin, so they live in one library of about 6,700 lines that each plugin depends on. A change there reaches seven products at once, so it’s a versioned Composer package and each plugin picks up a new release when it’s ready to.