Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We use too many damn modals (2018)

modalzmodalzmodalz.com

Post reply on HN
Print view View original

81–90 of 127 posts

Re: We use too many damn modals (2018)

#81

Post by winrid »

justanotherc wrote: post #40
kinkrtyavimoodh wrote: post #14

Earlier quoted context omitted.

The irony of a website with a deliberately terrible and gimmicky UI complaining about a functional UI model that has worked for decades.

That's kind of what I thought too. Our app is very Modal heavy (including modal inception), but I can't think of any case where the suggested alternatives would actually be better. And that's backed up by the fact that our users regularly tell us how easy and awesome it is to navigate through it.

It's one of those things that when you prototype a design without them you really feel the difference.

Re: We use too many damn modals (2018)

#83

Post by jevgeni »

kinkrtyavimoodh wrote: post #14
ameyv wrote: post #4

I don't want to complain, website is harder to read with all that 8 bitsh font type...Maybe normal post with one example for each idea would be good enough.

The irony of a website with a deliberately terrible and gimmicky UI complaining about a functional UI model that has worked for decades.

“Worked” isn’t exactly right. “Was popular” is better imo.

Re: We use too many damn modals (2018)

#84

Post by davedx »

Hah! I often have the experience that indeed a modal should actually have been a new page, but I was too lazy to build the thing so I went with the modal. Then later the modal needs more options or fields, and I end up having to convert it to a new page anyway... lesson mostly learned now. Agree with the article.

Re: We use too many damn modals (2018)

#85

Post by imtringued »

Eclipse uses modals in the worst possible way. Usually you want to copy the name of a type or variable into a modal but you are already into two layers of modals. You will have to close all of them and lose progress. Using more than one layer of modals is always bad design.

Re: We use too many damn modals (2018)

#86

Post by prox »

bedatadriven wrote: post #27

I was just about to share this our designer, who is always talking me down from modals, when I reached the bottom and discovered that our designer is in fact the author. I seriously can't say enough for this message. Adrian helped us redesign our app 2 years ago, dispatching many many modals in the process, and delivering a huge increase in usability that our customers and users very much do care about.

I implore everyone to read the fundamental book : about face

This book argues about a lot of UI topics, and with a lot of detail. It’s the bible of UI design imo.

Re: We use too many damn modals (2018)

#87

Post by the_other »

systemvoltage wrote: post #39
tasty_freeze wrote: post #34

Earlier quoted context omitted.

If my obese doctor tells me I need to lose weight, I have two choices. Either I can weigh his advice, or I can ignore him and cluck that his comment is really rich considering he is overweight himself. I think the first option is helpful; the second option is boringly obvious and not helpful. As for the style, I found it to be entertaining and helped make a possibly dry topic seem a little less like a lecture and mor…

That's a bad analogy. The reason why you trust your obese doctor for weight loss advice is not because their body shape, but because of the credentials (Doctor). Replace a doctor with a random stranger (which is what this website is, I don't know the person giving advice about the modals) on the street who is obese and tries to tell you with authoritative voice - "Hey! Listen, you're fat and this is how to lose weigh…

The depth and clarity of the advice and the effort put into presenting it work as solid credentials in this case. The author is clearly a “doctor” of design.

Look how well those those graphics get their message across, whilst also matching the style of the text. That takes a real steady hand (both literately and figuratively).

Re: We use too many damn modals (2018)

#88

Post by bryanrasmussen »

aylmao wrote: post #9

I remember reading somewhere that most (modal) dialogs are just lazy design. It's easier to have a dialog component and throw whatever notice or controls in there. It's a predictable and flexible canvas. Your password is incorrect? Error dialog. Easier to design and build that a warning state on the text-boxes and a message close to the login button. Writing a post? Editor dialog. It's easier to design and build than…

>I remember reading somewhere that most (modal) dialogs are just lazy design

If they are lazy design does that mean they are quick design, especially if you find a problem that needs solving in the middle of getting ready for the launch of your MVP it might be easier to do a modal.

Of course this would lead to legacy design that needs fixing over time, and legacy code to support the quick and dirty design decisions.

Re: We use too many damn modals (2018)

#89

Post by andreareina »

ozaark wrote: post #52

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 f…

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/

Re: We use too many damn modals (2018)

#90

Post by tobr »

grumple wrote: post #22
elcomet wrote: post #19

Earlier quoted context omitted.

Maybe it's lazy but the important question should be: is it good design? I don't think it is, as it hides some information from the main page. But I think it can be done well and be useful, as said at the end of the article. After all, OS use a lot of modals.

The more important question: do the people paying you care if it’s good design? Because the people who have paid me thus far in my career have not cared.

This is a good point, and often the reality - it’s unfortunate that it is being downvoted. But it’s a defeatist stance. It’s a central part of the designer’s job to contend that human factors are important, and explain what the effects of shortcuts and poor user experience are on the value of the product and the well-being of its users.

If you’re lucky your client hired you because they, too, care and believe design to be important, but that’s far from a given.

Post reply on HN