Currently, when a user scrolls down a list and selects a specific item to view its details, navigating back causes the list to refresh and reset to the very top.
Ideally, the app should remember the previous scroll position so the user can continue browsing from where they left off. This current behavior disrupts the workflow, especially when dealing with long lists.
Thanks for the clarification and the note about the back buttons!
Yes, this behavior is definitely what I see when using a mobile device, and I can replicate it consistently.
It happens on both Android and iOS (any mobile OS).
It occurs whether I use the AppSheet-provided back button or the OS-provided back gesture/button.
Crucially, this issue only seems to affect the new mobile template/view in AppSheet. The older template did not exhibit this behavior.
What is Happening:
When I have a long list of rows in a table view:
I scroll down the list.
I tap a row to view the details screen.
When I go back (using any back method), the list no longer remains at the scroll position it was at before. It jumps back to the top.
This happens with every page in the app using the new template. All the data shown is fictional, but the behavior is consistent across all list views in this new mobile template, whereas it didn’t occur before.
I will send a video shortly demonstrating exactly what happens.
@Jose_Arteaga I logged a ticket recently whereby even calendar view doesn’t honour going back properly in new mobile framework, perhaps they need to check if related.