3 ms·
On the other hand, if you're offering something that breaks with an established paradigm -- i.e. first-time viewers don't know what to expect, a short storyboar
by networkimprov 7y ago
On the other hand, if you're offering something that breaks with an established paradigm -- i.e. first-time viewers don't know what to expect, a short storyboard to clarify your model might be invaluable, and worth fussing over.
- onion2k 7y agoThis is the "don't waste time" part - on-boarding users with things they already know is wasting time, so don't do that. Teach users the new and exciting bits they don't know yet.
- jimktrains2 7y agoI'd venture to say that breaking UI paradigms shouldn't be taken lightly. Your application is not special to me, the user. I don't want to have to learn how to use the interface of dozens of different applications because they all thought they were special snowflakes and could break established paradigms.
- networkimprov 7y agoI was referring to application paradigms, not common UI patterns.
- jimktrains2 7y agoWhat's the distinction? If a user is surprised by what happens when they interact with the UI, the UI has failed. If we're talking about an application that requires a lot of outside knowledge (e.g. GIS (Geographic Information Systems (mapping)), accounting, video editing), you're not going to be able to "teach" the user what they need to know in the UI or some short videos. In one case on-boarding is a symptom of a bad UI, in the other it's more-or-less useless.