mapbox / mapbox/mapbox-navigation-android

Show "<" (less than) in `ManeuverView` similar to `TripProgressView`

Open
#3,982 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

jira-sync-complete needs discussion UI
Dominant language
Kotlin
Stars
651
Forks
321
PR merge metrics
No merged PRs in 30d

Description

I noticed while testing that right before getting a re-route we're displaying `0 ft` as distance remaining 👀

![0_ft_issue](https://user-images.githubusercontent.com/1668582/107708817-22373300-6c92-11eb-9582-6f5f33f9cdcc.png)

We didn't have "zero" values before but @cafesilencio confirmed that we made some modifications for the distance formatter because the minimum distance was always the value of the rounding increment which didn't make sense when approaching the destination. It was inaccurate.

Noting that for the duration remaining we are using `<` so probably is a good idea to do the same for the distance. Also the screenshot above isn't the only place this value shows. It also displays in the trip progress at the bottom of the screen and in the notification 👀

![0_ft_issue_notification](https://user-images.githubusercontent.com/1668582/107709155-c3be8480-6c92-11eb-9f68-2076f379ffb3.png)

Opening this ticket to discuss a one size fits all solution. Would love be consistent across UI components and platforms.

cc @avi-c @d-prukop @1ec5 @cafesilencio @mapbox/navigation-ios @mapbox/navigation-android

Contributor guide

Open the 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.

Research direction

Start by comparing how ManeuverView, TripProgressView, and the notification format zero distance and how duration already displays “<”. Review the related distance-formatting changes and the issue screenshots, then determine whether one consistent behavior can cover all listed UI surfaces and platforms. Done means the agreed representation replaces the misleading “0 ft” consistently.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.