Default design patterns I find myself repeating.
The other notes will be added soon.
Arrow keys to advance →
by Jan-Christoph Borchardt
I designed most of ownCloud
am active in the unhosted web apps & remotestorage movement
And you might have heard aboutTerms of Service; Didn’t Read
Let’s get started. Here’s a familiar scenario: You’re working on your things …
Then a popup appears out of nowhere, which you of course not read and then click away.
NOOOOOOOOO! Your work is lost and you don’t even know what happened.
Instead of asking questions no one listens to, offer undo.
Gmail does that with undo send.
ownCloud lets you undo file deletions.
Lying is a central part of keeping the user experience smooth.
What’s the purpose of double password input? Prevent error … by introducing more potential for error?
Apple does it right.
The new windows as a great new in-field toggle.
Another basic example.
You scroll down a list which already doesn’t use pagination (which is good) and then this appears: A button to load more.
What do they think I’m going to do? I’ll probably click it. Why do I need to do this?
Just do it automatically instead of giving me that work.
And beware of just adding a setting. If there are too many settings, people don’t find the right one anymore.
Right click nowadays is hard to discover.
Especially on these things.
Objects near each other are perceived as a group.
But this can also be negative, when destructive controls are placed next to the natural control.
Choice of words can be alienating.