Showing results for 
Show  only  | Search instead for 
Did you mean: 

Please listen to the community

Making moves

Volunteers are working hard on translating Firefox, offering user support, and helping users to move from Chrome, only for Mozilla to come and mess things up. People are leaving Firefox because instead of actually improving the browser and listening to your community, you're adding useless features (like Colorways), removing useful features (like FTP support, and abandoning PWA implementation), adding advertisements to the browser (like the recent Turning Red ad), and working with crypto exchanges. And look what happened, Firefox has only 7.48% marketshare. And we can do nothing about it. Because the community is not in control.

I'm really sad to see this happen. I really don't want to use a Chromium browser, but if Mozilla keeps doing what they're doing now, I might have no choice.




Community Manager
Community Manager

Hey @hexandcube ,

Thanks for bringing this up. This community exists because we value community insights and want to connect with our users more...and do so throughout the product development process. So please continue sharing feedback, joining product discussions (we even have active discussions currently hosted by product managers here and here), and submitting ideas for new features you'd like to see added to our products. We look forward to collaborating with you and the rest of the community here at Mozilla Connect.

The community has been disappointed many times in recent years. It doesn't matter how much effort the Mozilla team takes in looking for "improvement" if they don't recognize sometimes their decisions are mistakes and don't revert them timely.

It's been almost 2 years since Firefox for Android lost the ability to install extensions freely. The limited capacity of custom extension installation for Nightly is not a sufficient solution. Nightly is not safe for daily works. For extension compatibility, extension writers are declaring them since decades ago. Extensions should be blocked or disabled in a case by case basis only after some developers are found to abuse the classic mechanism and declare compatibility fraudulently when their extensions don't work. Not this current allowlist desert.

But sadly, after 2 years, user requests are still denied for non-technical reasons.