Is it my imagination or are the developers who write user interfaces in 2024 completely retarded?

Don't know, I don't talk to them. Why so?

Yes

Just the Javascript ones.

It started since some years ago. Low contrast. Plain and flat interface. Simple icons.

you know, UI, UX, and graphical design are not important because being dev is just about writting code and nothing else

I'm a FE dev & designer at my local company and our designs are just terrible. Every time, the designs goes to the CEO and he suggest things to be changed for the worse & a lot of worse. :D

We write user interfaces but we don’t necessarily design them.
I also noticed the new fad with low contrast, 50 shades of grey designs.

@mostr4am yeah, but you have much potential to become a designer one day

@retoor designing might be harder than we frontenders realize but it feels like sometimes we could make a much better job, especially when considering how much time we spend arguing with designers about their designs 😂

@mostr4am ideologically you already have :)

@mostr4am not sure if that pays better but at least you're allowed to hit women

@Lensflare WE frontenders? Wow wow wow.

15 years ago was fun, frontenders kinda start existing and whatever it was, it was never their job, always designer or dev. No idea what they did back in the day. The validation regex for inputs? That they now have to work so hard is karma

@retoor well, I was using the exclusive We. :)

I forgot where I read or watched it, but some languages have two different words for We.

The exclusive We means "Me and some others, but not you".
The inclusive We means "Me and you and possibly some others".

Companies hire UI devs. They need something to do. Turns out, UI dev isn't that hard. Redesign to look busy. Repeat.

@Lensflare there is also sarcastic "we". Like "we" are going to fix this. Really meaning I. Because nobody else is gonna help.

There there is a the pee wee.

@Demolishun my favorite is the false-we: For example when a football fan says that "we won". You haven't won anything, you were sitting in your couch, screaming at your tv.

@Lensflare

https://youtube.com/watch/...

Maybe they have the down syndrome

You think developers are in charge of user interfaces?

They are often just forced to implement the UX/Design departments latest desires.

@jiraTicket beautiful design, horrible UX, no accessibility.

@Lensflare ah in some of those cases I would kinda partially blame the devs for not pushing for accessibility. To some extent I feel that's on us.

I kinda expect the average designer doesn't know as much about keyboard navigation and screen-readers as web devs. So it ends up being our job to educate them and push for accessible solutions.

I just listened to a good podcast where an accessibility expert says they kinda expect devs to spend time under the radar to handle accessibility if the org doesn't care about it

https://syntax.fm/show/836/...

@jiraTicket

sad thought: Imagine being blind and missing out on all this UX.

happy thought: Imagine being blind and missing out on all this UX.

@jiraTicket in my experience devs do push for accessibility.
And that’s the problem.
The UX should be designed already with accessibility in mind.
Adding it as an afterthought after we, the devs, tell it to the designer, often results in bad UX.
Awareness of accessibility is a very essential tool of a designer, not only the devs.

@Lensflare So true!

In my org the designers used to be theoretically aware of stuff like WCAG color contrasts, but often ended up ignoring them when they had an idea that looked great in low contrast.

They were very unaware of screen-readers etc and didn't really take it serious when one developer complained some of their solutions weren't accessible.

But then we hired a new designer that was more into that stuff and started doing presentations on it - the designers took it more seriously. And started adding color contrast checkers to their toolkits, and started asking us devs "will this be accessible" before doing a wild new design :)