I’ve been using Firefox for Android as my main mobile browser for a few weeks now. There are a lot of things I like about it. It works well overall. Unlike Chrome, it supports extensions, so I can install (for instance) Privacy Badger and HTTPS Everywhere. The share menu option includes the two most recent apps instead of just one. Things like that.
But there are a few things that I find incredibly frustrating:
- PWAs aren’t as stable as Chrome.
- Auto-fill is inconsistent and interacts badly with scrolling.
- It’s slower than Chrome, though I’ve found that turning off web fonts helps a lot.
- Private mode UI differs only by the color of the search bar, so whenever I use it, I have to double-check whether I’m actually in private mode or not.
Plus I miss a few Chrome UI features that just streamline common actions:
- When clicking on the search bar, if you have a URL in the clipboard, Chrome offers to load that URL. (This is particularly helpful for opening email links in private mode.)
- Auto-fill an entire address form at once
- Clear the last X minutes of history
On the PWA front: These are packaged web applications that can be “installed” locally and used offline, powered by whichever web browser you used to install them. When I switched browsers, I also reinstalled the PWAs I was using on my phone and tablet, switching them from Chrome-powered to Firefox-powered. These amount to a couple of Mastodon instances and Twitter. (I don’t want to install the full Twitter app on my phone so I’ll be less tempted to get caught in infinite scroll.)
On Firefox, Mastodon’s PWA frequently logs me out. Every other day at least. Sometimes it stops being able to load any new statuses, and I have to close the app entirely and re-open it to get back to normal. (Fortunately that’s fast.) Twitter…well, it worked for a couple of days, then it got into a redirect loop where it kept switching between the regular UI and the login screen. I considered reinstalling it through Chrome, but finally decided I was better off without Twitter on my phone anyway.
Despite these issues, I’m going to stick with mobile Firefox for now. We’re entering another period of near-monopoly in web browser engines, and it’s important to keep a viable alternative going to ensure that the future of the web isn’t built on a single stakeholder’s goals.