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
Problem: Field work in Kenya showed that many people had rather old and slow Android smartphones that usually wouldn't react instantly when clicking a button. That became quite a problem when adding points, because people would push the "Add point" button again and again until finally a registered point was displayed on the map. By then however, they would have pushed so often that multiple points appeared, sometimes in far away locations.
Possible solutions:
Haptic feedback: Short vibration when pressing a button, especially the 'Add point' button.
Instant visual feedback: "Please wait" message or some loading icon displaying as the very first thing when pressing a button before the point registration classes are even called.
Both together would be great, too.
The text was updated successfully, but these errors were encountered:
I suspect that the issue here isn't so much about the devices, but rather that they're no visual or other feedback when "Add point" is clicked. #2908 should also help here.
gino-m
changed the title
Haptic feedback / wait message when pressing buttons
[Draw area] Haptic feedback / wait message when pressing "Add point"
Feb 19, 2025
gino-m
changed the title
[Draw area] Haptic feedback / wait message when pressing "Add point"
[Draw area task] Haptic feedback / wait message when pressing "Add point"
Feb 19, 2025
Problem: Field work in Kenya showed that many people had rather old and slow Android smartphones that usually wouldn't react instantly when clicking a button. That became quite a problem when adding points, because people would push the "Add point" button again and again until finally a registered point was displayed on the map. By then however, they would have pushed so often that multiple points appeared, sometimes in far away locations.
Possible solutions:
Both together would be great, too.
The text was updated successfully, but these errors were encountered: