Image Selection Sensitivity

[CodeWeav3r]

On the mobile app (iOS) my partner and I frequently find ourselves scrolling through the timeline and accidently selecting batches of photos. It seems like the sensitivity or timing for image selection needs adjusted. Is there a setting for this or can it be improved in a future release? I am migrating from Synology Photos to Immich and the sensitivity for image selections is very noticeable and can be frustrating when just wanting to scroll through photos.

[CodeWeav3r]

I also think this has to do with the default behavior of selection in the timeline. For iOS photos, holding a photo seems to take roughly 1000ms for a photo to be selected and the image options menu to come up; it doesn't go into selection mode whereas Immich it seems like 500ms to start selecting.

Maybe there should be a different default behavior in the timeline view that doesn't go right into selection mode or the ability to adjust the time required to begin selection mode.

[timonrieger]

checking in on this 😄

[CodeWeav3r]

Yeah, 1s might be a bit long for an action to start.

When I was timing it in Apple photos app it seemed like roughly 500ms for the animation to begin and then 1s when the context menu fully appeared. Again, it doesn't go straight into selection mode and start selecting a bunch of photos when that was not the intent.

Maybe the default action needs to change or 500ms to begin image selection animation and 1s for actual multi-image selection to take effect.

[timonrieger]

okay, i think i now what you mean, Apple has a two step process: after 500ms you get the haptic feedback and the immich "pops up", after another ~300ms you actually see the action sheet.
Also Apple uses the dedicated "select" button to enable multi-select, which then has no long-press constraints

[CodeWeav3r]

Exactly! That is the difference and that messes with the user experience.

Maybe implementing a dedicated select button to enable multi-select mode and changing the image press behavior would be a better solution as it would align closer to native app.

[timonrieger]

Maybe implementing a dedicated select button to enable multi-select mode

That's for sure more work and I am not sure what the maintainers think about this. Don't want to waste on this if it gets rejected. What would be the minimal improvement that would satisfy your UX?

[CodeWeav3r]

I think user experience would be more seamless if matching the native photo app selection/press behavior, but I get not wanting to waste time on it if the developers are not on that page.

Maybe keep haptic feedback at 500ms and increase animation time of photo selection would be a compromise. If press is aborted before animation is complete do not select photo(s). Not sure how that will look or feel but that might work.

[urbanrider]

I have noticed the same issue. Often accidentally select a batch of photos while scrolling.