▲ | hombre_fatal 21 hours ago | ||||||||||||||||
I don't get "as a backend engineer" comments like these. OP is doing a basic analysis on what kind of solutions exist for a typical UX edge-case. They even provide the simple solution that most people use (margin-bottom). And for fun they go on to see if they can solve it without the minor drawback of the simple solution. We've got to stop acting like it's a badge of honor to avoid UX consideration. We might not be people who implement UIs, we use UIs all day and should be able to muster up a few opinions about how a UX interaction should work. | |||||||||||||||||
▲ | andrei_says_ 15 minutes ago | parent | next [-] | ||||||||||||||||
As a full-stack engineer who also studies UX, most UI solutions span from a desire for originality, aesthetics, etc. and not improved experience. Which is what I loved about this article - it demonstrates a sizeable effort resulting in a UI implementation that is just not much better than having callouts / figures in the text- and then admits it. | |||||||||||||||||
▲ | NanoYohaneTSU 16 hours ago | parent | prev | next [-] | ||||||||||||||||
The issue is that UI/UX is in a terrible place. Your comments would be valid if this was 15 years ago. UX is in the gutter with extra clicks and terrible workflows in almost every website. UI is a catastrophe of mobile first, but not really, but sort of kind of we want power users but we need regular users, and all our UI kits look like total ass that is incompatible with so many other things. This website is a great example. The webpage doesn't load instantly and instead forces the user to wait for text to appear. Great UX engineering guys, make the user wait! | |||||||||||||||||
| |||||||||||||||||
▲ | xnickb 17 hours ago | parent | prev [-] | ||||||||||||||||
Looking at the UI of modern apps and websites, I think we're too late with this. What the mass user finds "intuitive" is already formed and it's in a horrible place and it's hard to go back. | |||||||||||||||||
|