Allow images to be sortable when using Image Picker and multiple images

When adding images to an Image Picker (connected to a Photos list field) the order of images change randomly.

It doesn’t keep the order in which the images have been uploaded.

I let the team know about this. I believe this is somewhat the same behaviour as uploading rows in batch. There’s no guarantee that they will be processed in the same order. I understand with images, there’s even a greater chance that you rely on it being in the right order to display in a carousel later.

1 Like

Thanks hope to get a fix or workaround soon. Users intentionally select pictures in order, then post them but then Glide take any random order.

2 Likes

Can you please change this post to Feature Requests ?

Isn’t more a glitch/bug? Pretty much on any app the order of uploaded items is respected, but not the case here. It make sense to be part of the existing “files upload” feature

Can’t speak for the team, but they told this should be treated as a Feature Request, specifically for the ability to rearrange items before submitting.

I don’t think I would consider this a bug.

Take the use case of sharing multiple images to a friend in a chat app, let’s say WhatsApp. You open the pictures app, select a few images, tap share, select Whatsapp and the friend, and then confirm. How do you define “order”? The order in which you tapped the pictures? The timestamp of the pictures? From most recent to oldest, or from oldest to most recent? In alphabetical order based on the random file name allocated to the file?

When I upload group pictures in a chat app or email, I always feel the order is somewhat randomly subjective.

1 Like

Agree.
If order is important, then force users to upload one at a time.

1 Like

I don’t believe we should force constraints of our platform (Glide) on our users.

I have a use case where I have to maintain a second column just to have users upload a primary photo, because the multiple images column cannot be used to sort images into any relative array, and also can’t be used in a collection to reliably display a specific photo. I’m separately doing the miracle method in a totally different UI to allow specific images to be chosen and shared, which is less of a problem but requires another table, another UI, maintenance overhead, and overall a clunky experience.

I’m going to work around the display issue by building a stronger image carousel via Rich Text and CSS, but it would be nice if there was a better interface for images overall, including selecting a primary photo and order of images.

Exactly the primary photo is the main case. Imagine a property listing: user spends time selecting the best picture first, worst picture last. After uploading they swap.

It is even very evident as everything looks “fine” while they upload, but after few seconds the user sees them swapping in front of his eyes.