How I Run A/B Tests in a Chrome Extension (Without Re-Releasing to the Store)
A/B testing for Chrome extensions without store re-releases: remote config, kill switches, variant pinning, GA4 tracking, and an open-source MV3 library.
Alexey Belozerov, creator of PerfectPixel, describes his approach to A/B testing in Chrome extensions without needing a full re-release to the store. Due to extensions' long update cycles and moderation processes, asynchronous management of experiments is crucial. The remote configuration is a JSON file on a remote server, with experiments that can be activated or pinned based on data and winning variants.
The framework includes entities like the A/B testing client, experiments, and a resolver to assign users to experiment branches. Data storage is achieved via chrome.storage.local, which survives updates and keeps user-specific data. The library is open-sourced under the MIT license on npm.
Written by urgent.news from HackerNoon's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
