Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA] Haptic Notification (vibration, sound) when Scanning Successfully #1873

Open
Kaz-ookid opened this issue May 17, 2024 · 0 comments
Open
Labels

Comments

@Kaz-ookid
Copy link
Contributor

Kaz-ookid commented May 17, 2024

Actual Behavior

When scanning, we either get two toasts : One for successful scan, one for unsuccessful scans. Usually, unsuccessful scans happen when trying to scan an already scanned code.

The issue

A common issue happening when scanning (Roll Calls attendees, LAO joining, Witnesses additions...) is that the notification toasts are not enough for us to figure out if the scan was successful or not and we often spend more time than needed scanning. Also, if you scan multiple people in a row, some old toasts will overwrite the newest until they are gone and prevent us from knowing the scanning state in real time.

Enhancement Concept

Add haptic notifications when a successful scan happens. A simple way is by adding phone vibration, or a sound, or both (I would say that phone vibration should be always the case, and sound could be optional). It would then be important to make sure that failed scans do not trigger those haptic notifications, so we can link those only with a successful scan.

@Kaz-ookid Kaz-ookid changed the title Haptic Notification (vibration, sound) when Scanning Successfully [IDEA] Haptic Notification (vibration, sound) when Scanning Successfully May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant