Earlier quoted context omitted.
Sheriff? I think you mean serif, partner.
I'm assuming they are a victim of autocorrect, pilgrim.
In some languages (e.g., Polish), the word for "serif" is the same as the one for "sheriff".
The end of the nice GTK button
451–460 of 666 posts
Re: The end of the nice GTK button
#452Earlier quoted context omitted.
Borderless buttons to have the right to exist, but you should be very careful with their use. For example, take this UI I made recently: https://mastodon.social/@grishka/107998100334356147 , 2nd screenshot. The button to decline invitation looks like a link (same color) and it's next to a real button. No one would ever get confused by this, it's pretty clear it's clickable. But a black word in a larger font among bla…
I disagree. I had to sit and think for a few minutes as it was extremely unintuitive - my first impressions were that I couldn't decline the invitation at all, and the button was disabled or missing for some reason (I've seen some bad CSS in my career so it no longer surprises me when it goes missing).
The button and link next to each other is a common pattern that has been used for decades at this point. It's core to Google's material design.
I agree that it might not be ideal, but when it is used literally everywhere I do not believe it's that hard to read.
Re: The end of the nice GTK button
#453Going flat seems a bit late. Apple are in some places backtracking and (although slowly) going back to some form of 3D. Have a look at the logic UI evolution. 10.4 was flat, 10.5 partly undoes the madness.
Re: The end of the nice GTK button
#454Earlier quoted context omitted.
> Whenever I see a hamburger menu I silently think "Here someone has given up" Can you explain what you don’t like about hamburger menus?
Is a dumpster of features, you have no idea what you'll find in there. Has someone hidden the zoom buttons in there? How about print? Perhaps that's also where save is, or tab colour? Most things in the hamburger menu are completely unrelated but exist for the removal of context. Button outlines so you have no idea what you can and cannot click on as well, which is mentioned in the fine article, are all modern design…
> Is a dumpster of features, you have no idea what you'll find in there.
I feel the same way about notifications. Both native notifications and notifications via e-mail.
It is no longer easy to find out if something changed or happened in most websites/applications. You must be bombarded with notifications all the time, and god forbid you take an extended break or something goes into your spam folder, because if you snooze you lose.
JIRA for me is the worst in this regard.
Re: The end of the nice GTK button
#455Earlier quoted context omitted.
Just go full-audacity and drown people in drop down menus lol at least I know what to click!
Audacity is a piece that made me learn its hotkeys. Once you do that, it’s pretty nice actually.
It works, I guess. But after I've worked with a proper DAW (Reaper in my case), Audacity felt like a toy
Re: The end of the nice GTK button
#456Earlier quoted context omitted.
> But, take a natively designed application from Windows 2000, and it's extremely easy to understand and use! And, dare I say it, more pleasing to the eye than flashy, animated graphics of today. Coming from that era, I strongly disagree. While I agree with the article, that some elements are harder to spot as interactable, I would still say that they are way more coherent than programs from W2K era and that one just…
> While I agree with the article, that some elements are harder to spot as interactable, I would still say that they are way more coherent than programs from W2K era ... Maybe that's the thing. More coherence might be nicer , yes. But it might also not make UIs easier to use. Maybe sqeezing apps into a tight framework of UI coherence, makes the overall appearance of what's on the screen more appealing but at the same…
> Maybe that's the thing. More coherence might be nicer, yes. But it might also not make UIs easier to use. Maybe sqeezing apps into a tight framework of UI coherence, makes the overall appearance of what's on the screen more appealing but at the same time loose usability.
It's a balancing act and you can screw up in either direction. What's clear is that limiting options and limiting depth is at a certain point really better from a UX standpoint - and I'd say old Windows toolkits are an example. It doesn't even mean there is missing anything, but that it is structured differently.
> Think of special applications like technical ones (Blender) or office (Thunderbird, LibreOffice) and also simple ones like a notepad application. Now try to find a common set of UI elements to use for all of them. What you'll probably get, is an OK notepad but a disturbingly bloated Blender.
Neither of these apps would have a problem with a GUI framework/toolkit per se. It's more an implementation detail of the specific frameworks/toolkits and the apps in question (also consider the time when they were founded).
Re: The end of the nice GTK button
#457I'm going to take a risk here and say that I'm a designer who generally likes flat design. I see a lot of hate here against flat design, and it makes sense. A lot of designers abuse it, making their UIs ambiguous. It's probably true that if flat design was never conceived, UIs would be less confusing on average. But it's clearly possible to do flat design well. iOS is mostly flat, but it's quite beautiful and user fr…
I disagree on iOS. Give an iPhone to someone never having used one before, and I'm sure they won't even be able to unlock it. I almost cringe when I see UX people with iPhones. Yes, it's esthetically pleasing, but please don't take too much inspiration from the way things work.
The first time somebody handed me an unlocked iPhone asking me to send a SMS (she was driving) I wasn't able to do it. I had to ask her where to touch. She was really surprised. I had a few years of experience on Android and 10+ with feature phones.
On the other side, I asked another friend of mine to take a picture with my Android phone a couple of weeks ago and she (an iPhone user) wasn't able to find the camera app. I had to open it for her. It was on the home screen, maybe it's different on the iPhone.
Re: The end of the nice GTK button
#458I'm going to take a risk here and say that I'm a designer who generally likes flat design. I see a lot of hate here against flat design, and it makes sense. A lot of designers abuse it, making their UIs ambiguous. It's probably true that if flat design was never conceived, UIs would be less confusing on average. But it's clearly possible to do flat design well. iOS is mostly flat, but it's quite beautiful and user fr…
Something you much see too often is that a designer tries to copy some design, without understanding why that it had been designed that way in the first place. That is how you got bad flat design. That is how the idea of metaphors got skewed into skeuomorphism — and likewise, how metaphors got swept away by the movement against skeuomorphism.
Maybe most designers are not even designers but only developers, frontend or backend, and the best they (we!) can do is copy something we already used which could come from other non designers. All the reasoning is lost in the process.
Re: The end of the nice GTK button
#459I think the Disney+ app has to be rock bottom of button design - the blue rounded one is selected, the white flat one is not. I always get it the wrong way around, even after several months of making the mistake.
Re: The end of the nice GTK button
#460Earlier quoted context omitted.
This. The devs and designers are all using 4k, 5k displays these days. Trying to use modern apps etc. on just "FHD" (1080p) displays is painful.
Over 2/3 of regular users are still using 1080p[1]. If your design looks bad on FHD then it looks bad to most people. [1] https://store.steampowered.com/hwsurvey/Steam-Hardware-Softw...
>Over 2/3 of regular users
That isn't going to be the case for Apple users though is it. Apple don't have any non retina devices in their lineup now. The only Apple users who will see a low dpi display are those plugging in a low dpi external monitor. They are going to be a minority.