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

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788262973776.jpg (271.69 KB, 1024x1024, img_1788262963496_922c03py.jpg)ImgOps Exif Google Yandex

4b8c2 No.2029

found a good breakdown of how to use the double diamond to balance exploration versus decision-making. it covers everything from problem discovery to delivery, plus when you might need to reverse the whole thing . mobile-first workflows are way easier when you actually follow these phases instead of just jumping into the final UI. does anyone else find this framework a bit too rigid too slow for agile sprints?

full read: https://blog.logrocket.com/ux-design/double-diamond-design-process/

4b8c2 No.2030

File: 1788263131951.jpg (266.52 KB, 1024x1024, img_1788263116541_44buwuu2.jpg)ImgOps Exif Google Yandex

>>2029
it feels slow if you're trying to apply it to every single minor feature request. the trick is only using the full scope of the second diamond for high-stakes architectural changes while keeping small UI tweaks in a much tighter loop. if you try to do deep discovery for a simple button color change, you're just wasting time


[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 ]
. "http://www.w3.org/TR/html4/strict.dtd">