3 ms·
I remember reading a book about UX years ago, and one of the fundamental principles there was the discoverability and the intuitive use, which boiled down to st
by alentred 3y ago
I remember reading a book about UX years ago, and one of the fundamental principles there was the discoverability and the intuitive use, which boiled down to sticking to conventions that are rooted in everyone's experience. Stuff like using check boxes and radio buttons properly, having the "OK" and "Cancel" buttons in their regular places (and not a "Maybe later"), using unambiguous confirmations (unlike the "Are you sure you do not want to not unsubscribe?"), sticking to the same navigation patterns users see in most other apps.
Now, I don't subscribe to it in full. There needs to be room for innovation. To my taste, it was quite boring when all software looked literally the same. Nevertheless, I agree there needs to be some reason too. Some short time ago every new app looked like a new game where you needed go through a tutorial to learn the basics. That was probably too much.
But, I don't know, as of late it feels like this iteration comes to and end, the apps start being intuitive again and reuse some patterns. The sidebars, user menus, etc. all in the same place. Mostly.
So, yay discoverability and intuitive use. But that doesn't mean we can't innovate in UX, while keeping it intuitive. Just not the "Maybe later" abusive way, please.
- jeroenhd 3y agoThere's nothing wrong with innovation, of course. A lot of controls needed to change to work well on touch interfaces, like the sliding toggles iOS use(d), and the large, connected touch areas that have replaced the small labels and click targets that computers used to have. There's no reason to abandon the toggle button/checkbox distinction, though. They're still used distinctively, there are common practices to indicate those distinctions that go back decades, and I don't see any need to unify these controls.