Unintended POI confirmations

[AntonKhorev]

Currently it's easy to confirm a POI without an intent to do so and not notice it. This is likely due to a number of UI decisions in Every Door:

• Poi list changes size when panning the map and might expand under your finger. It's easy to tap them accidentally instead of swiping the map.
• Pois on the list are never in the order you check them. For example, you may walk along the street from north to south, but the pois are not sorted along that direction; also you're likely looking at one side of the street but the list contains pois from both sides. This contributes to clutter in the list
• Poi list contains offscreen pois, the ones that are not currently visible in the map view. This also contributes to clutter in the list.
• Pois in the list get reshuffled constantly as the map view moves, wanted and unwanted pois get mixed together.
• Because of the reasons above you have to scroll the map view even more, since there's only one spot on the list which you can be sure about: the first one. So you end up trying to get the poi you want to edit to the center of the map view. Doing this with every poi leads to many short swipes. These short swipes may become accidental taps on the list and accidental confirmations.
• Confirmation buttons are at the edge of the screen, which makes them easier to touch accidentally just by holding the phone.
• Confirmed unuploaded pois look exactly like confirmed uploaded pois. You can't easily see that the green confirmation mark was made by you a moment ago and not by somebody else.
• Confirmation status is not visible on the map. All poi markers are white. You can't easily see which ones are confirmed, intentionally or not. If you're going to check, you may want to scroll the map, potentially making a false confirmation again.
• Number of changes is buried in the configuration menu. Some editors like Vespucci make this number always visible. Changes to this number indicate changes to the map data.

Example:

https://www.openstreetmap.org/node/4689641387/history

I see that a shop was was closed and another one opened at the same place. In the data I see version 3 which is obsolete. But it was confirmed two days ago. It's very unlikely for a shop to close and reopen that fast. Who confirmed it? Turns out it was me. But I didn't do that. Is it a bug? Then I realize I walked along a different street nearby two days ago and probably accidentally confirmed the shop.

[AntonKhorev]

I think there's also a delay between map scroll and list update, maybe if a lot of data is loaded. Tapping the list then may result in something else confirmed.

One possible fix for all this is displaying the last edited poi on the main screen. Now you have to go to Configuration > Pending uploads and I'm not sure how those are ordered. Are notes listed there before elements?

[Zverik]

Many good points, some of which I encountered myself. I have no idea how to tackle them at the moment, but I'll see what I can do.

Regarding the last question, pending uploads are always sorted by time edited — but notes first, then OSM elements. So yeah, there are timestamps in the app database.

[deevroman]

you can try adding animation/vibration when confirming the poi. But we need to test whether it will be distracting.

Confirmation status is not visible on the map.

In the filter menu, you can hide confirmed POIs. So far, this is the only way to influence.

[AntonKhorev]

In the filter menu, you can hide confirmed POIs. So far, this is the only way to influence.

Usually I want to see confirmed pois too. If a confirmed poi changes I'd want to edit it. Otherwise it will be like StreetComplete where you are not allowed to edit unless a quest is generated.

[AntonKhorev]

I noticed how I made one of unintended confirmations.

There were two pois close to each other, let's call them A and B. A was closer to the map view center and was first in the list. I wanted to confirm A, but I also remembered that B was nearby. Then I'm not exactly sure what happened, but I probably moved the map closer to B. But I probably didn't see B immediately because I decided to confirm A first. So I tapped the place on the screen where A was initially.

After that I made sure that B exists, probably moved the map again, and was going to confirm it when I noticed that it was already confirmed. Apparently the poi list got reordered and B got to the first position. When I was tapping the place where I thought was A, it was already occupied by B. Or maybe the list updated with a delay, and there was A at the moment, but the tap was registered on B.