Recommended Posts

yeah and not to mention the very distinct "keyhole" design.

and chrome's UI looks like it's from the windows xp luna days rather then windows 7/2008 aero or mac osx aqua era

Just more and more ridicolous. Among all the things firefox could have copied from chrome, they took its fugly UI. very well done

To be fair it looked like that in all versions of Firefox before Firefox 4. Firefox 3 had "native" buttons with some custom back-forward ones with the keyhole design.

I prefer "native" to system design anyday. see the bug for some example I provided. if you don't wanna dig through the mess compare openoffice ('system' styled) to anything like IE9/windows live essentials, Fx, WMP, etc.....

I prefer "native" to system design anyday. see the bug for some example I provided. if you don't wanna dig through the mess compare openoffice to anything like IE9/windows live essentials, Fx, WMP, etc.....

Not sure what the correct term even is, but all previous versions of Firefox had that button design. I'm not sure why they would waste so much time designing and implementing all these new designs just to revert back to the old days.

Nothing in Vista/7 even uses this button design so it is really odd.

Don't worry Mozilla is making Firefox ugly in an attempt to get Chrome users back.

LOL.

To be honest though, I've always found Firefox to be somewhat ugly up until Fx4, and even then it was just okay.

Even though I don't care for the resemblance to Chrome I'm just glad they're putting more resources into the UI other than just mockups.

Some people swear blind that IE9 is the prettiest, some say Opera ... to a reasonable extent UI and UX is a personal preference. Personally, I've already applied a stylish to remove button backgrounds (except on hover), because I fail to see the need for them. It's just extra lines.

Just because Chrome does something isn't a reason *not* to do it. Following others blindly is never a good approach, but this is not evidence of that.

Also, the UX build is a testing ground, not a *if it's in here, it'll be in a future release (unchanged, or even at all)*.

Some people swear blind that IE9 is the prettiest, some say Opera ... to a reasonable extent UI and UX is a personal preference. Personally, I've already applied a stylish to remove button backgrounds (except on hover), because I fail to see the need for them. It's just extra lines.

Just because Chrome does something isn't a reason *not* to do it. Following others blindly is never a good approach, but this is not evidence of that.

Also, the UX build is a testing ground, not a *if it's in here, it'll be in a future release (at all, or just unchanged)*.

Some people fail to realize that Chrome didn't invent borderless buttons.

Not sure if you're implying I think they did? Cause that's certainly not what I'm implying, nor would it matter. (But it's a fair point at anyone who thinks they did).

That's not what I meant. I was simply agreeing with you in a way, I probably shouldn't have quoted. It seems a lot of people complain that Mozilla is using borderless buttons. All version of Firefox prior to Firefox 4 had them, then they got changed in Firefox 4, now apparently they want them back. I've read so many complaints that Firefox is copying Chrome in this aspect, but it simply isn't the case.

I dont like the curved tabs either but the last screenshot on that website I think is REALLY sharp.

But mockups... We all know what happens with them. So many things were trashed for Fx4, including some things that actually made it in the nightlies.

I wish they would come up with one decent design and stick with it, at least for a year.

http://people.mozilla.com/~shorlander/ux-presentation/ux-presentation.html does look interesting.

With the massive caveat that they are mockups, and that doesn't mean Firefox will look like that ... the full screen views make a lot of sense, and the OSX menu design is fairly novel. Not sure about the 'flowing' tabs, but just because Chrome has them doesn't mean they're a bad design. Certainly to many they are more attractive than box tabs.

But mockups... We all know what happens with them. So many things were trashed for Fx4, including some things that actually made it in the nightlies.

I wish they would come up with one decent design and stick with it, at least for a year.

Product design just doesn't work like that, unfortunately. You find issues during implementation, or you find a better way to do something, or time constraints prevent you from coding it. It would be *nice*, and often the closer you can stick to mockups, the better, but it's rare to stick to a design over the course of several months of coding (especially in a rapidly changing market).

And indeed, with regular code releases, it doesn't often make sense to hold back new UI work just so you can do it all at once (for one, that would likely be a development nightmare).

^I understand changes are needed when it goes from mockups to actual implementation but at the moment it seems they're changing the design depending on their mood and they're not small changes so it can be implemented properly, either.

From the 4.0 mockups to the final release of Fx4 I thought they did a pretty good job of implementing what they set out to do and they're already scrapping most of it which I think is a shame.

^I understand changes are needed when it goes from mockups to actual implementation but at the moment it seems they're changing the design depending on their mood and they're not small changes so it can be implemented properly, either.

From the 4.0 mockups to the final release of Fx4 I thought they did a pretty good job of implementing what they set out to do and they're already scrapping most of it which I think is a shame.

I wouldn't say they are 'scrapping' it, really - tweaking and refining it, more like. Design work is a lot of iteration, and to have gone from Fx 3.6 to the new design seen above would be far too disruptive to the code and user experiences - so what happens are steps on a long road. Fx4 did make a variety of very good changes to the UI, but even Fx4's original designs were somewhat more radical than we got (e.g. no home tab yet, and other stuff on http://areweprettyyet.com).

In any case, yeah I agree that it would be nice to settle on a single design for a long period of time ... but it'll never happen, and rarely happens in any software, especially not browsers. (I would argue Firefox's previous feeling of more stable design was born more out of slow release schedules, than intent.)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      86
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!