[ 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.)

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

867f9 No.2217

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



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]