I’m facing a frustrating performance issue regarding the visibility of action buttons when using my app on a mobile device versus the desktop browser.
The Setup:
I have an app to control barrel deliveries. In my item list view, I have an action button (“Confirmar Separação”) that confirms I have picked a product. Once this action is clicked, it triggers conditions that should immediately display another action button (“Liberar para Entrega”).
The Problem:
On Desktop (Browser): When I click the action, the next dependent action button appears instantly.
On Mobile / AppSheet Interface Emulator: When I trigger the same action, the app starts syncing/loading, and there is a significant delay of several seconds before the next action button finally shows up.
This delay really hurts the user experience in the field, as workers have to wait around for the screen to update.
Below is a short video demonstrating the seamless behavior on desktop versus the slow response/sync delay on the mobile emulator view.
Has anyone experienced this type of mobile-specific delay with conditional actions? Is there any workaround or best practice to make the mobile UI update as instantly as the desktop version?
I just finished a chat with AppSheet support regarding this issue.
They confirmed that the action button delay on mobile is a known behavior of the legacy framework and recommended using the New Mobile Framework to achieve instant loading.
However, after I demonstrated that the new framework introduces a major bug where applied date filters are completely lost when pressing the back button, the support specialist officially acknowledged the issue. They have now escalated this filter-loss bug with priority to the engineering team for a fix. I will keep you posted here as soon as they reply with a solution!
The engineering team definitively recommends migrating to the New Mobile Framework. They have identified the root cause of the issue you demonstrated before and will be working on a fix.
Before they proceed, they wanted to check: if this specific issue is resolved, will that unblock you to fully adopt the New Mobile Framework, or are there other blockers holding you back?