Random taps are still processed

[anthony25]

When I click other items or list simultaneously. adalo still process all of them. I wish adalo to only process the first clicked/tapped item and the user need to wait until all actions on that item is finished. Sometimes when things are slow. After the user clicked the first chosen item. The user start to randomly tap. Then when actions from the 1st item is finished user may thought that it normally proceed unknowing that those random taps are just waiting to be load. Then you’ll be surprised that you are in another screen or have loaded other uneccersary things. Making user experience poor. I need help on how to manage this. Thank you in advance

[primedev06]

i dont understand this

can i see praqctical examples ?

[joe]

@anthony25

When I click other items or list simultaneously. adalo still process all of them. I wish adalo to only process the first clicked/tapped item and the user need to wait until all actions on that item is finished. Sometimes when things are slow. After the user clicked the first chosen item. The user start to randomly tap. Then when actions from the 1st item is finished user may thought that it normally proceed unknowing that those random taps are just waiting to be load. Then you’ll be surprised that you are in another screen or have loaded other uneccersary things. Making user experience poor. I need help on how to manage this. Thank you in advance

I’ve also noticed this recurring issue when interacting with items in a list on Adalo, especially on slower or non-flagship devices.

When a user clicks/taps an item, it sometimes takes a few seconds to load the associated action (e.g., navigating to a new screen, fetching data, or updating a record). If the user clicks another item before the first action completes, Adalo processes both taps; leading to unintended behavior/lags.

Why is this a problem?

• Users expect only one action to process at a time.
• When the app lags, users often tap other list items repeatedly, thinking the app is unresponsive.
• Once the first action completes, all queued taps suddenly trigger, causing unexpected navigation, multiple record updates, or unwanted data loads.
• This significantly degrades the user experience, making the app feel slow, buggy, and unpredictable.

Proposed Fix:

Adalo should ignore new taps until the first action is completed. Instead of processing all queued taps, the system should lock interactions until the initial action is finished.

This is an urgent usability issue that impacts real-world user experience. A fix would make Adalo apps feel smoother and more reliable, especially on lower-end devices.

Would love to hear if the team is aware of this issue or if there’s a recommended best practice to prevent it. Thanks in advance!

@james.crennan, I hope you are able to get this fixed. Good job on the progress you are making with Adalo and making it more robust.