Thank so much for the insights into scenarios you're familiar with, @Tino_Kreutzer and @Florian_May. @Tino_Kreutzer I apologize for not following up about a call. I figured you'd have your hands full! Plus, this thread has captured a lot of valuable information so would be great to keep the conversation here as we get close.
That's really great to hear. Let's see what you think of our first round of improvements and whether you think there's more necessary. I agree that the protocol you described is probably not needed anymore in general.
We've added a progress bar as suggested:
It has 5 steps each representing 20% of the bar:
- No location available: Trying to get location. Please wait. (this 20% is always filled when the dialog opens)
- Worse than unacceptable threshold (default 100m): Unacceptable accuracy. Please wait.
- Between unacceptable threshold and 5m before capture threshold: Poor accuracy. Please wait.
- 5m before capture threshold to capture threshold: Improving accuracy. Please wait.
- Currently the dialog closes when the bar is filled
This is now available in beta. To enable the new experience, please go to Settings > Experimental. You'll then need a form with a geopoint question in it such as the All Widgets form from the demo server. We look forward to your feedback!
One question we have is whether 100m feels like a good default for the unacceptable threshold. It corresponds to approximately a city block. There may be cases in which that is useful enough so we do want to make it configurable. However in the contexts and with the devices we’re familiar with we would expect that getting a better accuracy would be necessary and relatively quick.