4 ms·
I'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
by jimktrains2 8y ago
I'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 8y agoI was referring to application paradigms, not common UI patterns.
- jimktrains2 8y 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.