Shipping the same extension to Chrome, Firefox, and Edge: three very different reviews

We recently shipped our first browser extension, and getting the same MV3 build approved on Chrome, Firefox, and Edge turned into three very different experiences. Sharing a few notes in case they save someone else some time.

Same code. Three stores. Three completely different review experiences.

Chrome rejected us twice. First for "keyword spam," because our description listed the platforms the extension supports. Then for permissions: we requested tabs but only used chrome.tabs.create. We rewrote the description, dropped the permissions down to just storage, and it passed. (Then I added activeTab for one feature, which is basically the narrower version of the permission they'd just rejected.)

Firefox ran an automated review and approved it almost immediately. The only thing it wanted was an explicit data collection declaration in the manifest.

Edge is its own world. The developer program doesn't accept work or school Microsoft accounts, so I had to register with a personal one. The manifest has to be at the root of the ZIP archive or the submission fails. The review queue is slow, both for the initial submission and for updates.

Same code, and one store treated us like spammers while another barely seemed to notice.

One question for people shipping extensions: do you keep separate manifests and listings for each store, or generate them from a single source? I'd be interested to hear what you've found works best.