Empora for WooCommerce

Open the plugins page of a working WooCommerce store and count the rows.

Each row is an update cycle, a licence to renew and an author who may or may not still be maintaining the thing. Any one can break a checkout.

That is the tax on a platform whose greatest strength is that anybody can extend it.

A store that has been trading for a while is carrying a mixture nobody chose on purpose. It arrived one decision at a time, and every one of those decisions was reasonable on the day it was made.

Consolidating some of that into one product sounds obvious, right up to the point where you have to ship it.

A WooCommerce product lives in two worlds at once.

The free half is distributed through WordPress.org, which has its own review rules and its own settled idea of what a plugin is allowed to do inside somebody's store. The premium half is sold through CodeCanyon, which has different rules again.

WordPress.org does not distribute premium plugins.

So a premium edition cannot receive an update through the channel every WordPress user already trusts, which means it needs an updater of its own before it can ship a single fix. That constraint is the reason this product has a backend rather than only a plugin.

Empora is a Turborepo monorepo. Three things come out of it.

A WordPress plugin, carrying a React admin of 35+ modules that runs inside wp-admin rather than as a settings page which grew one tab at a time.

Then a marketing and dashboard web application, wrapped with Capacitor for Android.

A Laravel 11 backend handling auth, Stripe billing, licence activation and the self-hosted updater the premium edition depends on.

The proposition is one install, one update cycle and one place where the settings live.

The monorepo is what lets those three agree with each other. A licence issued by the backend, checked by the plugin and displayed in the dashboard is one concept held in one place rather than three implementations quietly drifting apart.

Now what it costs.

A monorepo means a single version bump touches PHP, React and Laravel at once. The arrangement that makes a release coherent also makes every release larger than it looks from the outside.

PHP and TypeScript are two ecosystems. Maintaining both means switching context several times a day, and the switch costs more than either language does on its own.

Two channels mean two rule sets.

A change that satisfies one reviewer is not automatically acceptable to the other, and finding that out happens at submission rather than at build time, which is the worst possible moment to learn it.

The self-hosted updater is a server that has to answer every time somebody's store checks for a version.

That is the single place in this product where being unavailable is not a private problem. Everything else here degrades quietly; the updater fails in front of a customer.

Licence activation is a boundary somebody will try to walk around. Every mechanism that makes that harder also makes a legitimate install slightly more irritating, and the balance between the two is a judgement rather than a setting.

No iOS. There is no Apple Developer account behind this work, so the mobile half of Empora is Android.

Empora is still in progress. What is written above is what exists today, and this page says nothing about what comes next, because a roadmap on a portfolio is a promise nobody signed.