Default geopoint: show accuracy threshold while accuracy is being refined
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Currently, the "Location will be saved at N m" message is only shown before a location is first captured. I think it should stay visible always to the user knows when automatic capture will happen.
---
### Checklist
- **Does it need UI/UX design?**
- [ ] Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
- [ ] No
- **Does it need API design?**
- [ ] Yes. Specify the endpoints, methods, or data structures needed.
- [ ] No
- **Does it need design around state flow?**
- [ ] Yes. Outline the state flow requirements.
- [ ] No
- **Does it need a test plan?**
- [ ] Yes. Add the test plan as a comment in this task or attach the document.
- [ ] No
---
### User Stories
- **As a** data collector,
**I want** to see the target accuracy,
**so that** I can be patient while the accuracy improves or give up if I have waited a long time and not reached the target.
---
### Design
- **Figma**: [Insert URL]
- **Design Docs**: [Insert URL]
---
### Dependencies
-
---
### Additional Notes
-
---
### Related Issues
-
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the UI that displays the "Location will be saved at N m" message and inspect how location capture and accuracy refinement affect its visibility. Done means the target accuracy remains visible while accuracy improves and until automatic capture occurs; add or update relevant UI tests if they exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100