I'm currently using Firefox on all devices as my primary browser, but there is a single feature that I've gotten used to in Chrom* browsers on mobile - 'pull down to refresh' - that looks indispensable to me, and I'm planning to move to Brave on mobile just because of that (already replaced Chrome with Brave on Desktop as my secondary browser). Yes, there are add-ons to do that on mobile too, but they are all inconsistent and half-baked. Chrom*'s built-in pull to refresh is very smooth.
I primarily use Firefox on my desktop, but I use Brave on mobile. It seems somewhat easier on the battery than Chrome, which would make sense being as it's blocking content that can be CPU intensive.
You might like it, though. I've used Brave's mobile sync and it works for bookmarks across devices quite well. It's surprisingly simple to set up, too. I don't fret much about forgetting whether I opened a tab on my phone or desktop if I remember to bookmark it.
That said, I still use KDE connect to send links to my primary Firefox instance and vice-versa, but the bookmark sync is in some ways more convenient. I'd imagine they'll eventually synchronize more things, like tabs.
Try Kiwi Browser for Android. Its a Chromium-based browser with built-in ad-block. If you want, you can even install uBlock Origin or any other extensions as it natively supports extensions.
That was my setup, and much prefer integrated blocking and the additional polish and features. The yubikey integration coming is particularly interesting: https://brave.com/ios-yubikey-support/.
Future monetization: that was actually an incentive for me. Having been in the belly of the beast on ad-tech I'm cheering the new ad model Brave proposes for the industry.
If you're not aware how messed up the industry currently is, keep an eye on Ad Fraud Historian on Twitter: https://twitter.com/acfou.
Firefox needs to respect the OS certificate store instead of using its own. Without it client-cert authenticated sites cannot be accessed. IT admins usually have policies on Windows and MacOS that prevent export of client cert+priv key.
OS certificate stores often come with the political baggage of the OS manufacturer. When a Chinese Gov't CA was found to have engaged in fraudulent behavior [0] Google and Firefox were quick to revoke/remove the CA cert from their products. Apple and Microsoft did not do the same, likely because they do not want to upset the Chinese Gov't. (IIRC Iphone users cannot even manually revoke CA's on their own phones.)
Then FireFox has made the deliberate choice of excluding millions of users. There are millions of users who use identity management solutions where user-certs and priv-keys are put into the OS store of their devices.
Using the OS secure-store should be a preference option. The folks who don't want to use the "political baggage" of the OS manufacturer - as you put it - can continue to use their pristine gardens.
I didn't know about this option - thanks. This option basically uses the OS cert store for server certificates, which is one part of the story.
Now, if they also did this for client-certificates then all the folks in companies that use corporate certificate-based single-sign-on can use FireFox!
I’m actually happy that Firefox uses its own store. This means that I can use it for browsing through the corporate proxy without having the corporate CAs installed in my OS. This way I’m always aware which data is inspectable by the company.
It would be nice however if Firefox had an option to use the OS store, including devices like yubikey.
Doing that gives me a weird, inexplicable feeling. I know Firefox blocks stuff, especially if you set tracker blocking to "Strict". It doesn't block all ads so I still want to use uBO... but do I disable Firefox's blocking to avoid doing the same thing twice? Or are there things Firefox handles better than uBO? It's really too much thinking so for now I'm using Edge Chromium with uBO, and that's not a solution :D
