osmandapp / osmandapp/web

Favorite points - usability issues

Open
#1,733 2 comments 0 reactions 1 assignee View on GitHub

@dmpr0 is already working on this.

Since Jul 22, 2026.

Nice to have
Dominant language
MDX
Stars
62
Forks
413
Avg merge
9h 41m
Merged PRs (30d)
81

Description

As someone who has over 10000 favorite points I've been struggling with the Web map since the beginning, but it's also the feature (and the premise of it getting better) that convinced me to pay for OsmAnd.

Obviously the map trying to display over 10k points is way too slow to the point of it being useless. Luckily on the Web view I do not need to see all the folders.

Here's my workflow in general: on Android I want to see all (except few) folders. On Web, I'm mainly working with one or at most few (~5) folders.

When synchronization of visibility status between Android and Web was introduced that really broke my workflow. On Web I would usually hide all folders (clicking one-by-one, which takes like 10 mins of clicking), except few. When this sync was introduced, that option would sync to my phone where I had to spend another ~10 mins clicking all folders to be visible and then syncing it back to to Cloud.

Luckily not long after selecting one folder was introduced on the Web (#629) - such selected folder would not change the visibility status of the points, but it would just show that one folder. This was not ideal, but was good enough. Now it seems that selecting the folder just fades out all other folders. That means that the map is still EXTREMELY slow rendering all 10k points and it's also very cluttered with them in the fade out state. That again broke my only remaining workflow.

Improvements in the Web map I would like to see:

  • option to show/hide one, few or all favorite folders
  • state of what I'm viewing on the map NOT to be synced to Android - this should just be a view not property of the point
  • would be nice to have some performance improvements - but I guess 10k favs is not the usual workflow for most of the users and it's technically hard to achieve.

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.