The Opera extension dev website page left me very confused, as it has a very long and extensive deployment requirements and review processes, but it left me without a single hint what are the benefits of putting the working hours to making your extension complient, or making the extension in the first place. Excluding branding/marketing purposes do I miss something or it expects devs to just making improvement to some commercial software, for free, motivated by some inconvenience/lacking feature in personal use and encouraged to making them public by guidline made from a long list of extra requirements/paperwork making it eligible to be graciously considered by the company benefiting from that act of public service? If this bold strategy is actually the plan and it works - I don't recall being outsmarded that hard in my entire adult life, make sure to give the author a raise.

]]>https://forums.opera.com/topic/83489/extension-developementRSS for NodeWed, 22 Jul 2026 17:59:56 GMTMon, 03 Mar 2025 22:47:00 GMT60@SpectralFlux Since Opera accepts most Chrome extensions, there are actually only a couple of reasons to make an extension specifically for Opera. As Opera's UI is not like Chrome's, any sort of a sidebar would need to be designed for Opera.

]]>https://forums.opera.com/post/379600https://forums.opera.com/post/379600Mon, 03 Mar 2025 22:56:33 GMT