[ ๐Ÿ  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: 1762149885934.jpg (138.37 KB, 612x612, img_1762149870183_nx3i8g73.jpg)

936af No.715

Hey there fellow design enthusiasts! So today I want to talk about something that has been driving me nuts recently - designing for omniscience. Ever clicked a button and had a system act all weird with no warning or way to back out, only to find out hours or even days later that it messed everything up? This is what I like to call "designing for omniscience" - when systems assume we're all-knowing beings and just silently go about their business. It's super frustrating, right? But here's the question: how do we design systems that don't make this mistake? What are your thoughts on this? Let's chat!


[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">