Open Bug 1927985 Opened 1 year ago Updated 1 year ago

Feature request: Install and update Firefox on Android without google play

Categories

(Firefox for Android :: General, enhancement)

Firefox 131
All
Android
enhancement

Tracking

()

People

(Reporter: post+mozilla, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0

Steps to reproduce:

Currently, it seems that to install Firefox on Android and get automatic updates, I have to use play store. That is bad news, since using play store requires creating a Google account, and doing that requires accepting Google's terms of service, which contain a lot of clauses related to data sharing and processing that are antithetical to the values of Firefox, Mozilla, and many of its users. Play store is also a centralized component manifesting Google's control over the Android ecosystem.

The only alternative I am aware of is to use F-Droid to install Fennec, which however can lag behind the official release quite a bit, leading to severe security risks.

So, we are in the unfortunate situation where Mozilla is actively pushing people towards either creating and using a Google account, or using an outdated browser. Needless to say, this is a pretty bad situation.

It would be great if Mozilla could provide a way to install and update Firefox that is compatible with the Mozilla values of an open, decentralized internet that puts people first. I don't know what is the best way to achieve this, but it cannot involve play store for obvious reasons. One option may be for Mozilla to host their own F-Droid repository, which could then offer timely updates.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Turns out there is a third option, that hopefully provides timely updates without google play: https://f-droid.org/de/packages/de.marmaro.krt.ffupdater/. However, I don't have any long-term experience with that option yet.

Still, getting something official from Mozilla would be a much better solution. :)

Severity: -- → N/A
You need to log in before you can comment on or make changes to this bug.