this post was submitted on 21 Oct 2023
56 points (88.9% liked)

Firefox

17301 readers
165 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

The UI for Fenix is dated. Some things need a little bit of love and others just don't make sense at all, like when you paste a URL, you can't see the URL or the Paste and Paste & Go options because the system pop up gets in the way.

Material Design and by extension Android moved away from pop ups and toasts and adopted elements like bottom sheets.

The custom share sheet is a nuisance and there's not even a way to get to the native share sheet.

Firefox for Android works, but it doesn't look or feel like a modern browser that was designed for modern Android.

So being that Android design has evolved so much since Fenix last got a lick of paint, I'm wondering, has anyone heard of anything in the works? Seen any commits or mockups? Screenshots? A mention on Matrix or the mailing lists?

all 22 comments
sorted by: hot top controversial new old
[–] [email protected] 21 points 11 months ago (2 children)

tbh i just want tablet mode

[–] Carighan 7 points 11 months ago (1 children)

Aye. At least give me keyboard shortcuts!

[–] [email protected] 1 points 11 months ago

Mouse middle button support (╯°□°)╯︵ ┻━┻

[–] dantheclamman 2 points 11 months ago

I've given up hope. The burden of maintaining the engine has left them with no bandwidth to pursue any major UI-related improvements. Check the comments on the "Idea" I posted to Mozilla Connect

[–] [email protected] 16 points 11 months ago (2 children)

Those custom/unusual UI elements are probably there for backwards compatibility. Firefox's latest android release supports Android 5.0, whereas Chrome's latest release supports Android 7.0

A lot of new Android UI elements are simply missing from the older versions, especially 5.0, so Firefox re-implements them itself AFAICT. Because of this I can't see Firefox updating the look/feel of their app, more custom components will just have worse performance on older devices as time goes on

[–] [email protected] 4 points 11 months ago

This is not right, the material libraries are a part of AndroidX, which has the current minimum SDK version 14 (Android 4.0.1), and will soon move to minimum SDK version 19 (Android 4.4). Compose, which is completely feasible to build the UI for Firefox for Android, has the minimum SDK version 21 (Android 5.0) iirc.

If I had to guess, I'd say that the Firefox for Android simply has not prioritized adopting Material You.

[–] [email protected] 2 points 11 months ago (1 children)

That's super interesting. One of my friends on mastodon is still using Android 7, so the necessity for backwards compatibility is definitely a thing. An unfortunate thing but a thing nonetheless. That said, doesn't Android itself provide the backwards compatibility enabling designers and developers to focus on modern apps? Otherwise wouldn't everything just look like a throwback?

[–] Vash63 4 points 11 months ago

Google does this via Play Services, but I wouldn't be surprised if the same devices they're worried about compatibility with don't have Google Play either.

[–] [email protected] 8 points 11 months ago* (last edited 11 months ago) (1 children)

I just want a black/oled theme

[–] [email protected] 3 points 11 months ago (1 children)

Saw someone open a PR with this fully implemented a couple of months ago.

Goddamned PM faffed about "UI research necessary before we make changes", linked them to a bugzilla post closed in favor of a JIRA ticket only internal users could view...

And then closed the PR, denying the change. And we wonder why Mozilla has been struggling so much lately.

[–] [email protected] 0 points 11 months ago

I'm confused, what type of research is required by Mozilla to implement an OLED friendly theme in Firefox? I don't like them myself, but it doesn't seem like something that needs masses of research hours.

[–] [email protected] 6 points 11 months ago (2 children)

You can read about why they have the current share sheet instead of the native one in this GitHub issue. There doesn't seem to be activity on the issue, but with the expanded functionality of the share sheet in ?Android 14? maybe the decision can be re-evaluated.

As for the design, I don't really see the issue. Could you share screenshots to explain the issues?

[–] [email protected] 4 points 11 months ago (1 children)

The share sheet definitely needs to be revisited. Look at what's possible now.

[–] [email protected] 1 points 11 months ago

Sure, you could make a new issue to start the discussion again!

[–] [email protected] 3 points 11 months ago

Issues like this one

[–] teejay 6 points 11 months ago

Can we please get bookmarks to remember your most recently used folder? Whenever I want to open a bookmark, I'm forced to start at the root folder and navigate around to find the folder and bookmark I want. If I just used a bookmark from some subfolder of my bookmarks, then I go to open a new one, the bookmark folder should be the last one I used. Instead it always starts at root.

It's incredibly annoying. All other browsers (including Firefox on iOS) get this right. There have been multiple requests / bugs filed for this for years, but so far nothing.