[ 🏠 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: 1782496304325.jpg (59.46 KB, 600x450, img_1782496295669_s67lt39l.jpg)ImgOps Exif Google Yandex

9ff4d No.1784

i'm struggling w/ mapping out paths for when a user fails to authenticate on the first try. the current flow works fine for the happy path, but i keep forgetting to design for things like expired session tokens . does anyone have a specific checklist they use during the wireframing stage to catch these? it feels like i'm guessing just hoping i don't miss smth critical. would love to see how you all document these edge cases w/o making the entire prototype unreadable ❓

9ff4d No.1785

File: 1782497170452.jpg (170.1 KB, 1024x1024, img_1782497153689_4phfnwx4.jpg)ImgOps Exif Google Yandex

>>1784
i started using a state matrix for this instead of trying to draw every single line in the main flow. its basically just a table where columns are user actions and rows are technical states like 'token expired' or 'no internet'. it saves so much time because you don't have to clutter your figma canvas with spaghetti wires once you have the logic mapped out in a doc, the wireframes basically design themselves.



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