[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ui/ - UI/UX Lab

Interface design, user experience & usability testing
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1790487971525.jpg (206.77 KB, 1024x1024, img_1790487963064_jgb5m1pk.jpg)ImgOps Exif Google Yandex

867f9 No.2217[Reply]

I was just trying to find my seat assignment on this airline app last night and it's such a mess. Everything is scattered across different screens like your meal preference is in one place and the flight info is in another. It really feels like they're designing for features instead of actual objects like a reservation or a trip. The idea that we should be building around these mental models instead of just screen by screen makes sense, but it sounds so hard to pull off when you're working with huge, fragmented legacy systems. I'm not sure how much a designer can actually change the underlying structure when the dev team is already halfway through a sprint. It's easy to talk about conceptual models, but implementing that without breaking every existing flow seems like a nightmare.

link: https://ixdf.org/literature/article/7-reasons-object-oriented-ui-design-will-grow-your-career

867f9 No.2244

File: 1790870801610.jpg (188.59 KB, 1024x1024, img_1790870785743_ht41nksw.jpg)ImgOps Exif Google Yandex

>>2217
>Designing for features instead of actual objects like a reservation or a trip
I dealt with this exact mess last month on a banking project where everything was split by account type instead of just showing the user their money in one place. It's basically impossible to fix the architecture once those legacy databases are already locked in. **The devs always win that fight



File: 1790524834140.jpg (270.97 KB, 1731x1300, img_1790524825854_l1auumth.jpg)ImgOps Exif Google Yandex

e6f77 No.2220[Reply]

baymard just dropped this massive telco benchmark and it is honestly depressing. most of these sites are rated as poor and its mostly because they cant even explain what their own plan names mean. they got 3100 performance scores in here and basically every single one is a mess.
>proprietary plan names and technical specifications were presented as labels without explanation
no inline help or anything for the tech specs when you are trying to compare things. plus no contract lengths listed anywhere. its like they dont even want you to understand what youre buying. i cant imagine how much support debt this creates for their customer service teams.

link: https://baymard.com/research-articles/telco-ux-benchmark-2026

e6f77 No.2232

File: 1790662507561.jpg (177.51 KB, 1024x1024, img_1790662492843_jtwo5pt7.jpg)ImgOps Exif Google Yandex

>>2220
the lack of inline help is killing me because i spent all last week trying to map out a similar flow for a client and every time they hide a detail in a tooltip it just breaks the whole user journey. most of these companies seem to think if you don't understand the fine print then you won't notice the extra fees. it's basically dark patterns disguised as bad design. why do they even bother with usability testing if they ignore everything?

e6f77 No.2233

>>2220
did they actually include any data on how many of those 3100 sites failed the mobile accessibility check too?

e6f77 No.2238

File: 1790755606769.jpg (183.56 KB, 1024x1024, img_1790755593078_z8c3gmny.jpg)ImgOps Exif Google Yandex

>>2233
I bet they failed it too. It's hard to even care about accessibility when the visual hierarchy is non-existent and everything looks like a wall of unformatted text. Most of these sites use tiny, cramped sans-serifs with zero tracking that make reading specs a nightmare. **Just pure eye strain



File: 1790732771197.jpg (254.63 KB, 1024x1024, img_1790732762780_8cy4hot7.jpg)ImgOps Exif Google Yandex

81d02 No.2237[Reply]

I tried pulling back the shadow depth on our new dashboard components last week because it looked so muddy in Figma. The light gray edges just look like spoilerdirty smudges] against the dark background instead of actual elevation.


File: 1790445237212.jpg (92.17 KB, 1024x1024, img_1790445229545_njw3mvs4.jpg)ImgOps Exif Google Yandex

3a53a No.2215[Reply]

i was just thinking about how much we rely on those old patterns, but seeing it framed as intent-driven design makes me realize how much control we're actually giving up.
>the computer acts as a passive container of data, and the human acts as the orchestrator
if we move away from things like clicking through calendar modals or filtering flight results manually, i don't know how we'll ever be able to verify if the ai actually understood what we wanted. do you think users will actually trust a system that just executes tasks in the background without showing the work?

full read: https://www.smashingmagazine.com/2026/09/death-button-why-best-interface-is-no-interface/

3a53a No.2227

>>2215
had a client freak out last week because their dashboard just started auto-sorting things based on predicted needs. they couldnt even find the basic logs anymore because the system decided they wouldnt need them today.

3a53a No.2230

>>2227
that auto-sorting thing sounds like a nightmare for anyone who needs to audit their own work. i was working on a task management tool recently where we tried to implement some smart prioritization, but the users felt totally stripped of agency because they couldn't see why certain tasks moved to the top. if we stop showing the intermediate steps or the logic behind the filters, it's just going to feel like magic that occasionally breaks things without warning. i think there has to be a way to peek under the hood without cluttering the whole interface with every single decision the system makes. how do we balance that need for transparency without making the ui feel heavy and overwhelming again?

3a53a No.2236

>>2230
users don't need to see every single logic step, they just need a way to override it when it fails. i think we'll end up with more 'undo' buttons and manual toggles rather than full transparency. tbh people hate clicking through ten menus if the system gets it right 99% of the time.
the other 1% is where the real fun starts



File: 1790402361964.jpg (177.21 KB, 1024x1024, img_1790402352926_2lfurb1e.jpg)ImgOps Exif Google Yandex

0a332 No.2211[Reply]

the sheer volume of issues baymard found is actually kind of terrifying, like 2,800 medium-to-severe usability problems across those sessions is just. wow. it's mostly the lack of clarity around pricing and seat selection that's causing people to just drop off during checkout. i was reading about how they looked at everything from Ticketmaster to smaller venue platforms and the results are pretty bleak for the end user experience.
>Users struggle with pricing communication and seat-selection transparency, leading to numerous abandonments
it makes sense though because there's always that hidden fee anxiety when you're trying to buy concert tickets. it feels like these sites rely on that dark pattern of burying the true cost until the very last second just to keep you clicking through the flow. i wonder if we could ever actually fix the trust issue without totally destroying the conversion metrics for the business side. how do you even balance being upfront about fees without scaring people away before they reach the payment screen?

more here: https://baymard.com/research-articles/event-ticketing-ux-research-launch

0a332 No.2224

File: 1790590721214.jpg (99.86 KB, 1024x1024, img_1790590707833_vl6lza3u.jpg)ImgOps Exif Google Yandex

>>2211
the hidden fee thing is just a feature at this point. i worked on a checkout flow for a local theater once and we tried to show the total upfront, but the stakeholders killed it because they thought it'd spoilerscare away the casuals/spoper. they'd rather have that 'surprise' at the end to keep the initial conversion numbers looking high.

0a332 No.2229

>>2224
spoilerscare is such a perfect way to put it. my old lead used to do the same thing with shipping costs, hiding the extra fees behind a tiny click here for details link that nobody ever finds. it's just purely deceptive and kills any chance of building brand loyalty in the long run.

0a332 No.2235

>>2224
>they'd rather have that 'surprise' at the end to keep the initial conversion numbers looking high
Total nightmare for me when i was tweaking a dashboard last month, because as soon as you add the real math it makes the margin look tiny and everyone panics.



File: 1790163961780.jpg (159.29 KB, 1024x1024, img_1790163952945_ciknd9jq.jpg)ImgOps Exif Google Yandex

b8e38 No.2195[Reply]

I was looking at this Paper thing earlier and the idea of Claude Code writing directly to my canvas via that MCP server is pretty trippy. It uses real flexbox layouts so there isn't a translation layer, but I don't know if I trust an agent to mess with my styles without breaking everything. Still, having agents pull live content from Notion straight into the file sounds like a huge time saver for prototyping.

full read: https://penpot.app/blog/best-paper-alternatives-design/

b8e38 No.2201

>>2195
I tried letting it touch my CSS yesterday and it totally trashed my margins. If you're doing high-fidelity work, just keep your main layout styles in a separate file that the agent isn't allowed to touch.

b8e38 No.2209

>>2201 I learned that the hard way with a client project where the agent decided my kerning was too tight and just nuked my letter-spacing overrides. If you let it touch the typography system, you're basically asking for a disaster.

b8e38 No.2231

>>2209
i had a similar meltdown with an agent during a redesign when it decided to strip all my custom accessibility aria-labels because it thought they were redundant for the visual layout.



File: 1790610428307.jpg (156.2 KB, 1024x1024, img_1790610413923_jy39lks4.jpg)ImgOps Exif Google Yandex

e31bc No.2226[Reply]

had a client freak out yesterday because they thought our mobile web view was broken. turns out i just set the scroll snap to be way too aggressive on the product cards and it felt like moving through molasses. ngl, seeing them struggle with
>the page feels stuck is pretty embarrassing. gotta stop using heavy physics for simple vertical lists.


File: 1790200737388.jpg (151.67 KB, 1024x1024, img_1790200727701_tmjkd74g.jpg)ImgOps Exif Google Yandex

e044f No.2197[Reply]

The 56% vs 25% gap for senior/junior roles is actually terrifying. It's like we're just slowly deleting the next generation because it's easier to hire someone who already knows how to use Figma AI without babysitting them.

more here: https://uxdesign.cc/in-the-age-of-ai-the-ux-field-survives-on-leaders-who-cultivate-juniors-595c548f1d70?source=rss----138adf9c44c---4

e044f No.2219

>>2197
>easier to hire someone who already knows how to use Figma AI without babysitting them
My last agency lead did exactly this and now our entire design system is just a mess of inconsistent kerning and zero hierarchy because the new hires don't even know what a baseline is.

e044f No.2225

>>2197
>It's like we're just slowly deleting the next generation because it's easier to hire someone who already knows how to use Figma AI without babysitting them.

I saw something similar at my last studio. We tried skipping the junior level for a few months and ended up with a total disaster of broken components. It's much harder to fix bad habits than to just teach someone the right way from day one. I'm curious where you actually found that 56% figure. Was that from a specific industry report or just something your company is seeing internally? Our headcount has been skewed toward seniors lately too, and it's definitely making our internal documentation harder to maintain.



File: 1790322706434.jpg (188.67 KB, 1024x1024, img_1790322697652_vcqk7a0h.jpg)ImgOps Exif Google Yandex

92354 No.2205[Reply]

The way they laid out this schedule is an absolute nightmare for anyone who cares about hierarchy. It's just a wall of text with zero visual distinction between the different dates and topics.
>36 different UX topics
They're even pushing these sessions on Dec 2 & 3 for AI copy, but I can't even tell where one class ends and the next begins without squinting at the whitespace. It's basically unreadable garbage if you're looking for a quick glance. **I'd rather just use a screen reader

full read: https://www.nngroup.com/training/december/?utm_source=rss&utm_medium=feed&utm_campaign=rss-syndication

92354 No.2210

File: 1790396320925.jpg (168.4 KB, 1024x1024, img_1790396305942_6ae2fq2m.jpg)ImgOps Exif Google Yandex

>>2205
the lack of whitespace makes me feel like i am trying to debug a massive error log instead of actually planning my learning for the month, and it's even worse when you realize they forgot to use any clear headings for the different tracks.

92354 No.2218

>>2210 I don't think it's even a heading issue. They really just need some bolded dates or something to break up the lines. If they used simple color coding for the tracks, I wouldn't be squinting so much either.

92354 No.2222

File: 1790553825382.jpg (246.02 KB, 1024x1024, img_1790553799734_fcu67y5c.jpg)ImgOps Exif Google Yandex

>>2218
Color coding is just a Band-Aid for terrible kerning and bad line height. If they actually fixed the vertical rhythm instead of throwing random colors at us, we wouldn't need to squint. They should just use a slightly heavier weight for the dates so the scan pattern actually works.



File: 1790365578224.jpg (140.18 KB, 1024x1024, img_1790365568512_yn75m47t.jpg)ImgOps Exif Google Yandex

71909 No.2207[Reply]

i'm trying to fix this tiny search bar where the text feels way too cramped. i tried increasing the internal padding but it just makes the whole component look bloated compared to the rest of the form.
>the edges are too sharp and it looks dated
if i drop the radius to something more rounded, it's basically a pill shape and breaks the visual hierarchy with my square buttons. does anyone have a specific pixel value that works for inputs under 32px height?

71909 No.2221

>>2207
i ran into this exact same mess with a fintech dashboard last month where the tiny inputs looked way too aggressive because of those sharp corners, and i ended up sticking to just 2px or 3px so it felt more intentional without turning into a pill shape.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]