![]() ![]() I'd love some pushback here if there's something I'm missing. ![]() ![]() And with Android's fused provider, who knows what the underlying stack is doing. It's not actionable and I find it oddly technical and distracting. The unit should probably be "min" instead of "m" because we use "m" for meters. Time elapsed, I don't love, but I do think it's very useful for folks to know how long they've been waiting. And maybe instead of Point, we say Geopoint to match the launch button? Not sure whether that's useful but it would provide relief to my untrained users if they are stuck with a coarser accuracy that just won't auto save.įor Good, "Point will be auto-saved at 1m" feels clearer. So I would love to see (with better wording):Ī message "You have to wait for a location fix before saving is possible" which disappears once there's a fix.Ī button "you can save now with accuracy (progress bar)" as soon as saving is possible.Ī message "This point will auto-save at xxx m accuracy (also indicated on progress bar)".Ī message "Accuracy has not improved in the last xxx seconds, save now?". Some untrained users on my end get confused as to when they can save (as soon as there's accuracy shown), when it would auto-save (when good enough), and when they can hit save to cut off a timing out GPS fix at the given (not good but also not further improving) accuracy. ![]() Bonus if the progress bar changes colour (accessibility - eh) from red for too low to orange to green for "good enough" (as per default or form defined accuracy constraint). I would totally wait to get a better "high score" if you showed me those made up percentages. Something like a progress bar for accuracy? Like "location accuracy quality" ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |