71–80 of 127 posts
> And remember to always ask, kids: >“Why does this have to be a modal?”
In my experience people don't need to be remembered to ask this. And generally people can't justify why it shouldn't be a modal or why a non-modal solution is better than a modal one.
This is only tangentially related, but one thing I'm absolutely sick of is rounded corners. I don't know why, and I don't know if it makes any sense, but opening a page and seeing literally everything with border-radius makes my blood boil. It feels like they're trying to protect me from sharp corners, as if they're dangerous. Come on, we're all adults here. We can take a few 90 degree angles.
If you have to use a modal element at least allow me to get it out of the way so that I can read the text under it!
My main gripe with modal windows is the name. The first couple times some developer told me that's what she was using, I waited for her to explain what modal meant. But she did not, as if it was standard self-explanatory terminology. Way to name something a word that sounds like it has a standard (even deeper) meaning, but does not. With time, I have just accepted that this is what modal means (I'm going to create a…
It's a term from the UI design world, and it goes way back. A mode is a state where the app accepts certain inputs from you, the user. A new mode means previous buttons and shortcuts are inaccessible, and the same input may produce different results. Either coincidentally or directly related, Vim's modes illustrate the idea well—in contrast to editors where input, motion and shortcuts for extra functions are availabl…
I guess I just have to live with it when I pop in and out of the UI coding world. Just like in Python a .method isn't what the natural word typically means, but just has gotten a domain-specific meaning attached to it in that world.
Earlier quoted context omitted.
Just because you cant see the connection doesnt mean its not there. Adjective, (of a proposition) in which the predicate is affirmed of the subject with some qualification, or which involves the affirmation of possibility, impossibility, necessity, or contingency. Its pretty plain to see how a confirm or error message is applied to that definition no?
Not really. It's a stretch (at least for me) to see the connection between a window that shows you some data, or a toggle, or some arbitrary information and the idea that the window should be called "modal" as if it controls some "mode".
> in which the predicate is affirmed of the subject with some qualification,
E.g. an error with an error message
Or
> or which involves the affirmation of possibility, impossibility, necessity, or contingency.
E.g. an are you sure? dialog preceeding a save.
I was playing with Alibaba Cloud's UI and it's all modals and feels much much nicer to use. I wouldn't use Ali Cloud due to Chinese ownership issues, but I do like their UX.
Earlier quoted context omitted.
I don't love retro design either but that seems irrelevant. To anyone who's familiar with the topic it's immediately clear from the copy that the author understands it. Considering that the target audience is other designers, why does the presentation matter?
> Considering that the target audience is other designers, why does the presentation matter I fail to see the logic here. Good design helps people learn easier. It's not like designers have some unique ability to learn equally well no matter how poor the design is.
It's not like he used gifs or flashing colors.
Now I kinda want gifs and flashing colors.
Edit: To provide a little more substance here - for example in one product of mine that actually has customers - confirmation is done via inline elements that slide into the page.
So you want delete a comment for example. The delete/cancel buttons slide into the box for that comment. No weird context switch for your eyes.