New Mobile Framework Issue

[Rurrea]

I switched my apps to the new mobile framwork, but I’m having issues with my save and back buttons. The behavior of these two buttons are much different than before.

First, in the old version, I can be in a table view and when I click a row to enter detailed view, from that point, pressing back takes me back to the beginning of the table instead of the spot I was last at. It’s a hassle having to look for where I was within the table to continue searching.

Second, after pressing save button in form, it does not allow me to return to table using a back button.

i would like to remain in the new mobile framework, how can I adjust the above problem.

[amyplin]

Thanks for reporting these issues!

For your first issue - pressing back button takes me back to the beginning of the table - we are actively working on being able to maintain scroll position in the new mobile framework, that should be available within the next coupe of weeks.

For your second issue - pressing the save button does not return to the table using a back button - can you send a screenshot of what you're seeing here?

[PauloExpert]

You're definitely not the only one noticing these quirks with the new AppSheet mobile framework—it comes with UI improvements, but also some behavior changes that can affect navigation flow.

Let’s address both issues you're facing and go over possible solutions to help you stay in the new framework:

1. "Back" Button in Detail View Doesn’t Retain Scroll Position in Table View

Issue:

You open a row from a long table list > view details > press back > the table resets to the top.

What changed:

In the new framework, navigation between views doesn’t preserve scroll position like before. Instead, it reloads the entire table.

Possible workaround options:

Use a Deck View instead of a Table View: Deck views tend to perform a little better in navigation flow, and in some cases AppSheet retains scroll position better here.

Split long tables into smaller filtered views. For example, if the table is a list of "Jobs," you could break it into:

“Today’s Jobs”

“Pending Jobs”

“Completed Jobs”

This reduces the need to scroll far and makes the user experience snappier.

Add a quick "Go Back" Action: If you're using grouped actions or deep links, you can sometimes craft a custom "Return to Section" action to mimic better navigation (more below).

2. Save Button in Form Doesn’t Return to Table View

Issue:

You complete a form and press "Save" — but there's no way to go back easily or automatically to the original table/list.

Fix:

Use a Form Saved Event Action to redirect the user back to a specific view.

Steps:

1. Go to Behavior > Actions

2. Create a new action:

For a record of this table: (The table your form is using)

Do this: App: go to another view within this app

Target:

LINKTOVIEW("Your Table View Name")

3. Go to UX > Views > Your Form View

4. Set the Event Actions > Form Saved to the new action you just created

Now, when the user presses Save, they’ll be automatically redirected to the table (or whatever view you prefer).

Optional Tip: Deep Links to Preserve Flow

If you’re dealing with a multi-level flow (like Dashboard > Detail > Edit), you can create custom navigation using deep links that guide users back to a specific context. Let me know if you'd like help building these links for your views