[ozaark]

The key design principle overlooked here is Progressive Disclosure[1], which modals and dialogs can be very good at delivering.

Progressive disclosure retains user focus on a single task as opposed to showing everything at once. Accordions have similar function to modals and dialogs but adding further task controls to an already complex interface isn't always the best solution.

The author goes on to state that even full screen modals are bad, but what difference does the user see? If done well the user should still be able to use the browser back button, escape key, etc to navigate out. In modern applications, pages can transition from one to the next without a "full page load" -is that also bad for some reason?

Think of many popular mobile apps like Instacart, Doordash, etc that allow a user to dive into categories that slide on top of the existing content to give further controls; is that not ok?

Every element in the DOM can be applied inappropriately but that doesn't shift the blame to the elements themselves. One could argue an entire dedicated site that only uses modals based on the misuse of illegible fonts would be about as apropros.

[1] https://www.nngroup.com/articles/progressive-disclosure/

[andreareina]

TFA is not saying all modals are bad, just most. Progressive disclosure is a fine thing, but that doesn't have to mean modals. Most of the time a discreet notification that doesn't interrupt the user's flow is what's appropriate; I think Tidal does a good job here, by highlighting one feature per screen, and if I don't tap on it to see what it is I'm able to go about my way.

Since we're quoting NNGroup, here's their guidance on modals[1] (emphasis mine):

1) Important warnings

2) Critical to continuing the current process

Most modals are unasked for, not relevant to the user's current needs (no matter what the dev/marketing might think), and unwanted. Modal to select filter settings when I've clicked/tapped the 'filter' button? That's a good use.

[1] https://www.nngroup.com/articles/modal-nonmodal-dialog/

[ozaark]

TFA literally says don't use full screen modals, ever. I disagreed with examples of that not being necessarily relevant with the way today's applications can work.

Important from the NNGroup article you linked even demonstrates great modal usage and states "3. Modal dialogs can be used to fragment a complex workflow into simpler steps." and "4. Use modal dialogs to ask for information that, when provided, could significantly lessen users’ work or effort."

That's important - modals are not just intrusive pop-ups as many designers and others in this thread have decided that they are. Again, every element can be used inappropriately but that doesn't mean the elements are to blame.

[andreareina]

You're right about full screen modals, I've seen those done right and "never use x" is rarely right all of the time. And modals can be done well, but 90+% of the time I encounter them, they're not. They're not related to the workflow I'm currently engaged in, they don't save me any time, they don't serve me.

Again, I'm not saying (and I wouldn't characterize TFA as saying) modals per se are bad. But the priors are such that absent any other information, modals are suspect.