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?

  • 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

    • 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.

    •  sabreW4K3   ( @sabreW4K3@lemmy.tf ) OP
      link
      fedilink
      English
      29 months ago

      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?

  • A UI refresh is needed? Maybe.

    Material You? Absolutely not. Absolutely not me, and never has been.
    It can have “you” in the name when the UI becomes customizable, and not just dark/light/whatever, but the silliest things everything after Material 1 (the true Material) has brought: rounded corner radiuses and margin sizes.

    but it doesn’t look or feel like a modern browser that was designed for modern Android

    I don’t know but that’s for sure it has become as slow as what people call modern android. It’s literally slower with 0 addons than old firefox with loads of tabs and addons, which I still have in parallel.

    •  sabreW4K3   ( @sabreW4K3@lemmy.tf ) OP
      link
      fedilink
      English
      59 months ago

      But the things you dislike about Material You are the things that my mum loves, the larger tap areas, the ease of reading, etc.

      Take Sync for Lemmy for Example or Auxio, these are beautifully designed Material You apps that look good and function well.

      • Ok, but I’m not your mum. I guess there are multiple demographics with different needs. I want to fit more on my screen, not less, and I don’t want to bring a 22" display with me for that purpose.

        Take Sync for Lemmy for Example or Auxio, these are beautifully designed Material You apps that look good and function well.

        I’m happy that you like them.
        As I said, material you will only deserve it’s name when it will mandate adapting to the user. Until then, it’s just a marketing name, a huge lie.

  • 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?

    • 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.

      •  sabreW4K3   ( @sabreW4K3@lemmy.tf ) OP
        link
        fedilink
        English
        29 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.