alexbbrown
commented
1 year ago Open alexbbrown opened 1 year ago
alexbbrown
commented
1 year ago alexbbrown
commented
1 year ago Example for the above link https://user-images.githubusercontent.com/2532344/203177998-0b5c8cb3-d284-4aaa-bf83-b1bc82f29058.mov
I was browsing a toot with a video in and saw "record not found" modal with OK button.
When I think about modals in apps, they should tend to abide by a few principles
1) it should be clear that they are in response to a specific user action or app state 2) they should provide the user with an understanding of what failed and ideally what action to take next 3) in general modals should only be presented when we need to use it to make a choice-if a modal only contains OK, then we could consider to skip it or replace it with less intrusive UI
considering these principles, in this case:
It was not clear what action or app state this message was in response to.
It is unclear what, if anything, the user should do or understand in response to this message. No choice is given, and it's unclear if OK with remedy the error or simply accept it.
It does not contain any verbs useful for the user OR nouns or identifiers such as record id or url useful to a developer. The noun "record" is unfamiliar in this context. Does it mean "toot" or "user" or "video"?
I imagine it was a failure to load the video. In which case, perhaps the text should read "could not load video", whcih would associate it with a user action (tapping the video) and provide meaning for the user (you aren't going to get to watch this).
the word Record sounds like private API vocab.
Perhaps no message at all is necessary? Or maybe the UI element which would display the successful output could display the failure message inline. Eg the video could have a red X instead of the content.
https://tenforward.social/@elight/109377638625617639