4 ms·
The biggest disappointment is that the “unchecked” state to trigger the checkbox is a low-contrast circle with tiny “READ” text inside it. Poor discoverability,
by wgx 4y ago
The biggest disappointment is that the “unchecked” state to trigger the checkbox is a low-contrast circle with tiny “READ” text inside it. Poor discoverability, poor accessibility, very un-satisfying.
This person is clearly a talented designer and animator, but this is a bad piece of UI and would deliver a bad UX.
- Kerrick 4y agoAs a user of this app, I disagree. During app onboarding, you _create_ the unchecked checkbox by typing the name yourself. And usually you're only building a single habit at a time, so you already know what the text will be before you reopen the app to mark the habit as done. This article doesn't describe a good checkbox to place in a list of preferences in just any old app. It describes a _destination_ checkbox, to be checked once per day, that is supposed to gamify habit-building and make tracking that habit's progress _add_ to the experience, rather than feel like an additional chore.
- someweirdperson 4y agoA checkbox is a thing to toggle off/on to select a state. As I understand your description of the app it toggles itself off and the user toggles it on. That's not a checkbox but a button. If the user can toggle it off that's more like an undo-operation, still not a checkbox. Of course in the sense of "checked as done for the day" it is a "check"box. But it is a little unexpected without contex when reading about a "checkbox".
- deleted 4y ago[deleted]
- astrange 4y agoIf the app implements VoiceOver and other accessibility options then it's fine to look like whatever you want without them.