> Once you’re ready to test the mobile version of your extension, create a collection on AMO and test it on Firefox for Android Nightly. If you’d prefer to poli

> Once you’re ready to test the mobile version of your extension, create a collection on AMO and test it on Firefox for Android Nightly. If you’d prefer to polish your extension before publishing it on AMO, you can also debug and run the extension with web-ext. I think this mirrors the desktop behavior (now correct me if I'm wrong, I very well might be ;)). Firefox Developer Edition on Desktop has options for sideloading, but otherwise to sideload it needs to be signed. You can however temporarily load an extension to test it if you're a developer in I think any version of Firefox. Their link (https://extensionworkshop.com/documentation/develop/developing-extensions-for-firefox-for-android/#install-and-run-your-extension-in-firefox-for-android https://extensionworkshop.com/documentation/develop/developi...) suggests that Android will work (almost) the same -- you can temporarily load an extension to test it, but it needs to be signed unless you're on nightly. I do think forcing every extension to be signed is a mistake and I wish they'd do away with that policy. But at least on first impression, it looks to me like mobile will be as open as desktop is? Which would be a huge improvement considering how locked down the current Firefox for Android is.