3 ms·
This has been so frustrating. My company has two Chrome extensions, one of which we've been able to migrate and are just finishing up, and one of which we are b
by gnicholas 4y ago
This has been so frustrating. My company has two Chrome extensions, one of which we've been able to migrate and are just finishing up, and one of which we are blocked on because we're waiting on a dependency to be sorted out.
Of course, we're not just on Chrome — we're also on Firefox. But our migrated extension doesn't work on Firefox, since they haven't fully figured out their transition plan. We're left with a gigantic mess that will be confusing to users (because our Chrome MV3 has significant changes to our freemium model, which made sense to implement during the manifest changeover). We'll have to explain to our FF users that they still have the old version, but the new version is only on Chrome. But for our other extension, everyone's on the old version. What a mess.
- CatWChainsaw 4y agoI thought Firefox had no MV3 plans. Why does that extension require a transition?
- gnicholas 4y agoThe issue is that when the MV3 transition was announced, we decided to revamp our freemium structure. We've now completed that for our MV3 extension, but that only runs on Chrome. Our Firefox version is still running the MV2 extension, which is perfectly functional but which uses our old freemium model. We are going to have to explain to our Firefox users why the freemium structure (free use on X websites forever) differs from the freemium structure described on our Chrome extension, website, etc. (free use on all websites for Y days).