Improve OpenStreetMap edits upload #7402

New issue

Open

opened 2024-02-17 00:40:40 +00:00 by biodranik · 0 comments

biodranik commented

2024-02-17 00:40:40 +00:00

(Migrated from github.com)

The issue is more critical for Android, but iOS implementation will also benefit from it.

ATM OM uploads edits when it's moved into the background/switched to another app.

The main Android issue is that the system may kill or suspend the app and break the upload, which leads to changesets without comments [TODO: insert existing issues here] or failed uploads [list issues here]

The important UX issue is that users don't understand when/how their edits are uploaded.

Another issue is about privacy [reference it here]. Although single edits are not uploaded immediately, but later, in batches, a bigger delay may be needed to dissociate a person from recently visited places.

Here are some ideas on how to implement it:

Random delay is not needed for many users. Many OSMers and non-geeky users would love to see their changes uploaded immediately and will complain about any delay.

Random upload delay is needed for those who care about privacy.

Any upload delay is needed to batch changes and don't DDOS OpenStreetMap.org servers (yes, we are thinking about the future now, with millions of active OM users worldwide). Remember that OpenStreetMap.org is not a powerful corporation with many resources to scale and protect servers.

Showing (and then hiding on successful upload) a foreground service notification while the app is active is annoying.

For most users, the default master branch batching approach should be enough, when changes are uploaded when OM goes into the background. Meaning that a notification appearing when OM goes into the background would be helpful to see that everything was uploaded smoothly or failed.
On success, a notification may report success for a second and disappear. On failure, it may stay there and handle different errors differently.
It would be great to show more detail about failed edits on tap.

For privacy mode an (off by default) checkbox may be introduced in settings (should we make a Privacy section there?):
"Delays OSM edits upload for a random amount of time".
A timer can be displayed in the notification in this case, with "tap to upload immediately" functionality.

Originally posted by @biodranik in organicmaps/organicmaps#6119 (comment)

The issue is more critical for Android, but iOS implementation will also benefit from it. ATM OM uploads edits when it's moved into the background/switched to another app. The main Android issue is that the system may kill or suspend the app and break the upload, which leads to changesets without comments [TODO: insert existing issues here] or failed uploads [list issues here] The important UX issue is that users don't understand when/how their edits are uploaded. Another issue is about privacy [reference it here]. Although single edits are not uploaded immediately, but later, in batches, a bigger delay may be needed to dissociate a person from recently visited places. Here are some ideas on how to implement it: Random delay is not needed for many users. Many OSMers and non-geeky users would love to see their changes uploaded immediately and will complain about any delay. Random upload delay is needed for those who care about privacy. Any upload delay is needed to batch changes and don't DDOS OpenStreetMap.org servers (yes, we are thinking about the future now, with millions of active OM users worldwide). Remember that OpenStreetMap.org is not a powerful corporation with many resources to scale and protect servers. Showing (and then hiding on successful upload) a foreground service notification while the app is active is annoying. For most users, the default master branch batching approach should be enough, when changes are uploaded when OM goes into the background. Meaning that a notification appearing when OM goes into the background would be helpful to see that everything was uploaded smoothly or failed. On success, a notification may report success for a second and disappear. On failure, it may stay there and handle different errors differently. It would be great to show more detail about failed edits on tap. For privacy mode an (off by default) checkbox may be introduced in settings (should we make a Privacy section there?): "Delays OSM edits upload for a random amount of time". A timer can be displayed in the notification in this case, with "tap to upload immediately" functionality. _Originally posted by @biodranik in https://git.omaps.dev/organicmaps/organicmaps/issues/6119#issuecomment-1742190113_

👍 2

This repo is archived. You cannot comment on issues.