5 ms·
I've always found the UI after IE6 / FF2 to look "off", and that's likely because they started using non-native controls, drawing their own instead of relying o
by userbinator 5y ago
I've always found the UI after IE6 / FF2 to look "off", and that's likely because they started using non-native controls, drawing their own instead of relying on the platform UI.
Firefox’s Redesigned Preferences Feel More like the Web
That expresses exactly what's wrong --- the native UI controls are predictable and accessible and styled with the rest of the OS, and as the cascade of dialogs above it (I'm not sure how that's even possible --- getting to "Offline Data" From "Exceptions - Saved Passwords"?) shows, you can actually see that you're controlling the browser and not merely a page inside it (related article: https://news.ycombinator.com/item?id=30697329 https://news.ycombinator.com/item?id=30697329).
Another important change is the introduction of a skeleton screen to make the start feel fast
I've never heard that term before, but whenever I see things like that, I'm reminded of fancy progress bars and such --- the real problem is that you need one in the first place, and instead of fixing the underlying problem of why it's taking so long, you try to hide it...
- CharlesW 5y ago> I've always found the UI after IE6 / FF2 to look "off", and that's likely because they started using non-native controls, drawing their own instead of relying on the platform UI Wow, I think you've identified the probable cause of something I've felt was "wrong" about Firefox for a long time but couldn't pin down. Firefox just "feels" bad on a Mac even in comparison to Chrome, not to mention Safari.
- Tagbert 5y agoStill not enough to make me hold my nose and use Chrome. I’ll stick with Firefox
- nerdponx 5y ago> Firefox’s Redesigned Preferences Feel More like the Web This is such a weird thing to me. Did anyone ever want this? Were users asking for this? Did user studies show that this was somehow desirable or preferable? Did they do a study of Chrome users and find that they were more likely to stick with Firefox if they made this change? Does it significantly reduce code maintenance burden somehow? It seems like the kind of thing where users only "want" it because it's familiar, and it's only familiar because it's already been forced on them everywhere. Basically it's circular reasoning. It's like the meme of hiding a button and then claiming that users never use that feature, so you can justify removing it.
- baal80spam 5y ago> Did anyone ever want this? Were users asking for this? In this day and age, noone cares what actual users want. Instead, corporations tell users what they "want".
- wejick 5y agoI personally love it and think this is better approach than the old small windows. The post exactly explain what I think.
- deleted 5y ago[deleted]
- chefandy 5y agoProduct designers should definitely favor local OS norms in most cases. Using one design for all OSs might be organizationally easier in many ways, inter-OS visual consistency offers little benefit to users and doesn't leverage their familiarity with similar idioms in their environments. > Another important change is the introduction of a skeleton screen to make the start feel fast Yeah. Sometimes you do have to make users wait— e.g. parsing a huge cache to put in a dialog or making shaky network calls— and most designers mental model for addressing that frustration is the slow elevator problem†. Skeletons seemed like a good way to address it. We don't parse screens instantly: we first interpret structure/visual hierarchy so we know where to scan for titles, ordinals, controls, or whatever else we need. Skeletons theoretically let us do that while content loads. More recent research doesn't corroborate claims of silver-bullet efficacy: https://www.researchgate.net/publication/326858669_The_effect_of_skeleton_screens_Users%27_perception_of_speed_and_ease_of_navigation https://www.researchgate.net/publication/326858669_The_effec... † The related anecdote goes something like this: Tenants of an NYC office tower complained of slow elevator service during peak use. The property manager consulted with experts to evaluate the algorithmic efficiency and mechanical components, but it resulted in little improvement. The property manager then turned the exterior elevator doors int mirrors. Most riders were sufficiently emotionally engaged by a life-sized version of themselves long enough to make the wait seem much shorter.
- eek2121 5y agoExcept a browser should load things in the following order: 1) Create Window 2) Create UI (based on native controls for OS) 3) Load drop downs, top level down. 4) If you design your application this way, you won't have to build a skeleton. Mozilla is not using native UI/UX components to build their UI, so they have to go through several extra steps. I'm sure they do this in the name of customizability, but that, IMO, should be optional.
- chefandy 5y agoI was talking about skeletons generally because the commenter to which I replied said they’d never heard the term before.
- 5y ago
- Yaina 5y agoThe problem with modern, native-looking UI surfaces is that they are hard to design and maintain on cross-platform applications. How do you design and implement an interface that feels native across platforms? First there is the easy approach: The common denominator elements. Essentially what you get when creating a Java Application. The UI will probably look kind of native, but also outdated. Think Windows 89-Style Settings. You're also limited in how you can present options because you have so few form elements to play with. The other approach to native is to use modern UI elements. For one thing these are not easy to get. While on macOS Cocoa bindings are at least available, on Windows it is pretty much impossible to get anything but the Windows-89 style form elements. Even if all the bindings were available, which also has to take various Linux Desktop Environments into account, then you had to design for and maintain multiple versions of the same settings menu. So I hope this explains why non-native controls are a sensible approach. You create your own design system that is (mostly) consistent across platforms. Designers only have to design one surface, they can create new patterns if necessary and engineers only have to maintain one implementation. Of course they have to be accessible and they are. I say "mostly consistent" by the way, because Firefox still respects some UI conventions from operating systems. For example it uses system fonts, system font-scales, and changes naming conventions and button orders appropriately. This reduces work but of course it still is work to update and maintain that surface. about:preferences in Firefox has quite become quite messy over the years and is neither loved by designers nor engineers, but it's time and resource intensive to update it.
- userbinator 5y agobut also outdated Bias towards fashion trends is one of the biggest problems in the software industry.
- eek2121 5y agohard disagree here. Let us look at Windows and macOS for a second here, and exclude Linux, because Linux (rather, Linux + your favorite DE) is realistically the issue (due to KDE, GNOME, and a gazillion other types/styles). If you design around a given language for the most recent versions of a native OS, you'll never have issues. Both macOS and Windows include common libraries that map to their respective styles. Microsoft, for example: https://docs.microsoft.com/en-us/windows/apps/design/ https://docs.microsoft.com/en-us/windows/apps/design/ (link on bottom if you want to drill down to code). "What about users that want to customize things?" Give them an alternate path. The browser loads slightly slower (the same as now), and they still get their ability to customize. The rest of us can use the default, faster path.
- mmis1000 5y agoI think it's just the trend, ms also introduce the fullscreen file menu in office 2010/2013. Their menu also changed to more flat and fullscreen ui instead of popup based. The firefox simply matches the trend (and it is actually a little late to the party)
- userbinator 5y agofullscreen file menu What an absolute abomination that was. An insane waste of space and a violently assaulting visual distraction. Especially when you're trying to open a document that the current one is referring to, hiding what you're trying to see with useless space. "Windows is called Windows, not Window."
- WhyNotHugo 5y agoNative controls also responded better. The new web-based pop-ups can take a long while to render if a heavy page is being loaded. So if I try to quit Firefox, the "are you sure you want to quit" popup renders empty until the current page is done. Sure, this happens only on high resource usage, but the previous implementation di not suffer from this.