Missing directional context for user when using maps

Open
#639 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Review the map view and linked dependency #561 first, then compare the requested behavior with the provided Figma design. Confirm how the location dot, heading availability, and accuracy radius should appear, and verify that the directional indicator and radius are shown only when supported.

Written by the indexing model from the issue text.

Description

front-end
Description

When viewing the map, there is currently no indication of which direction the user is facing (heading). This creates spatial disorientation, forcing users to walk in a direction just to see which way their location dot moves on the screen. Computers lack the sensors for this, and not all phones have them either. The indicator should appear whenever it is available.

This refers to the last image (blue beam)
Image

The user would also see the accuracy radius, like you do with google maps.

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 [user type],
    I want [functionality],
    so that [benefit].

Design

Dependencies
Dominant language
TypeScript
Stars
38
Forks
24
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/web-forms

All issues in getodk/web-forms

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.