Comment

Comment on Why you shouldn't use Brave Browser

I used Brave on mobile for a full week about a year or so ago at the suggestion of a coworker before realizing it gave me nothing over Firefox and added the bizarre crypto angle to everything.

This was during my (thankfully brief) crypto interest phase and I tried to see if I could accumulate any of the BAT coins the browser would give you for viewing ads…that never worked somehow so I accumulated zero, which was certainly one thing that led to me getting fed up with it and going back to Firefox.

Beyond that, the interface was weird, it was prone to crashes, and it was generally a hassle. 100% flash-in-the-pan cash-grab effort.

source

Sort:hotnew top

Gestrid@lemmy.ca ⁨1⁩ ⁨year⁩ ago
You can actually turn off all the crypto stuff, thankfully.

As for the crashes, I never experienced that in the past year that I’ve been using Brave. (I recently switched to Firefox not because of this article but because of Google’s recent proposal.)

source
atx_aquarian@lemmy.world ⁨1⁩ ⁨year⁩ ago
Funny the different experiences we have. I switched from FF to Brave only on mobile because FF mobile doesn’t correctly interface to Android clipboard for scrolling screenshots. (I think that’s because they assume everyone uses Samsung, which brings its own, but I’m on real Android and loving the experience over Samsung’s bloaty mc bloatface experience.)

That was only one feature that I rarely use, but, once I tried to switch back to FF, I realized it had some other problems on mobile. Perhaps it’s one of my plugins, but every other scroll-up motion is ignored. The only reason I have plugins is to give me dark mode on accessibility-challenged sites, and that ability to do that with plugins was initially FF mobile’s edge over others, but now I have native dark mode built into Brave.

I still prefer FF on desktop, and I want it to win on mobile, especially for its reading mode that I don’t think any other browser comes close to implementing.

source