Last week I asked people to participate in some group design thinking around a specific design pattern: email settings. This was the premise:
Imagine there are three events that can happen in a web app that could trigger an email. We want to allow the user to decide whether or not they receive emails when those events happen.
I looked through all the responses and these are the ones I thought were the most interesting and effective. This is not a comprehensive list. To see all responses, look through the comment thread on the original post.
Note: I don’t care about the browser compatibly of these. That’s a different problem. There is always a way to get a design to work. That part should happen after the best possible solution is found.
It’s essentially the same as a checkbox (on or off), but the styling and ingrained text may make things more clear:
This one uses a table layout:
And iconography:
These take one step back and first ask the user if they want to be emailed at all. If they don’t they shouldn’t need to make any individual choices. At it’s simplest, it’s like this:
A bit fancier:
The more choices there are, the more it makes sense to have an option to check all / uncheck all:
Or just having a clickable “Never” option:
These are intentionally verbose, forcing a user to read and comprehend before altering.
This forced interaction would likely leave little doubt to the user as to what’s going to happen:
I said I’d pick three of what I thought the most interesting and success were, so I figured I’d pick them from different categories. Blake Pemberton, Frank Spin, and John. I’ll email about the access.
Great job, everyone.
UI Pattern Ideas: Email Settings is a post from CSS-Tricks
Article published by Chris Coyier