Re:Firefox Android Build that caused issues is working as in...
by panpanna on Wednesday August 26, 2020 @08:04AM
(#24281632)
You don't actually use the bar that often, so having it at the bottom doesn't improve much. In fact, it will mostly be in the way.
Bookmarks on the other hand are used often and the new updates requires 3 clicks to get to them (previously 1).
So this is a classic case of UX designer not knowing how people use his software and just doing changes he thinks are cool.
Maybe if you have a large phone or short fingers but beside this bottom bar there are only disadvantages in the new UI, like no bookmarks in the new-tab-page. Or the additional movements/tapping you have to make to open a new tab. It's like the designers never even used the previous FF.
> and the browser is much faster
Maybe if you mainly visit shitty javascript-bloat-sites like twitter or reddit but for me there isn't much difference in loading times. The small initial pageload-speedup is lost by the time I need to scroll over all the new advertisements I previously never had to deal with thanks to uMatrix.
> but it lost some features
not just "some features". It lost _everything_ that made it better than chrome. Now there is just no reason for mobile FF to exist anymore.
> A small but vocal number of users complained
How did you measure that? I see mostly complaints and a few people who are happy because of the bottom URL bar.