You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, accessing the settings requires a "long press" on the main clock screen. This was a deliberate design choice so that the clock itself looks clean (i.e. free of distracting buttons/clutter).
However, after watching several users, it's clear that finding the settings is unintuitive -- even with the pop-up explainer.
We want to make the settings easier to find so people can take better advantage of the customization options for the clock. Some options include:
Use onPress instead of onLongPress
Pros: Much easier to access
Cons: People might get frustrated if settings open off of an accidental tap.
Open settings with a swipe gesture (e.g. React Navigation Drawer)
Pros: Nice UX
Cons: Might still be unintuitive to find.
Add a temporary FAB (floating action button). Appears after tapping anywhere on the screen, and fades away after some number of seconds (e.g. 5-10 seconds).
Pros: I think this is the nicest design
Cons: A little more time consuming to implement.
After implementing this feature, the Toast should be removable in favor of the "intuitive" settings access.
The text was updated successfully, but these errors were encountered:
Currently, accessing the settings requires a "long press" on the main clock screen. This was a deliberate design choice so that the clock itself looks clean (i.e. free of distracting buttons/clutter).
However, after watching several users, it's clear that finding the settings is unintuitive -- even with the pop-up explainer.
We want to make the settings easier to find so people can take better advantage of the customization options for the clock. Some options include:
onPress
instead ofonLongPress
After implementing this feature, the Toast should be removable in favor of the "intuitive" settings access.
The text was updated successfully, but these errors were encountered: