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.
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.