March 25, 2025

Deployment Time: 12:00 PM PST

Features & enhancements

Item Description
Preview release of the new mobile framework

AppSheet’s new mobile framework:

- Improves the overall mobile experience with a more responsive app, enhanced stability, and modernized user experience
- Unifies the mobile app experience with the desktop experience


The new mobile framework is turned off by default.



For more information and to learn how to turn on the new mobile framework, see:

- Community announcement
- About the new mobile framework

Bug fixes

None

Rollout changes

None

Preview announcements

Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.

  • No new preview features were released today.

In addition, the AppSheet preview program lets app creators try out new app features that are not yet fully supported. For more details and to opt-in, see AppSheet preview program.

9 Likes

Looks great!

Thank the team for so much. Thank you for putting in so much effort. I’m truly very happy.

Hi @lizlynch ,

My app users have been facing an issue with the Android app since March 20th.

The problem occurs in a form that contains multiple page headers and an inline reference form. When users navigate to the next page and attempt to enter a value in the first text-type column, the app automatically moves to the previous page. Sometimes, this happens unpredictably.

This is not an app development issue but rather an APK-related issue. We are experiencing the same problem when accessing the inline form.

Please help me resolve this issue. I have already reported it to support.

Hi, can you tell me the detail about the new mobile framework? Does it affects the performance? If so, what are the changes ?

@saravana_ni - Checking with the team about your issue. You might want to contact Support. I’ll let you know if I learn anything.

@Andre8287823 - See About the new mobile framework. This should answer your questions.

1 Like

Okay, thanks

@saravana_ni - Definitely reach out to Support to troubleshoot your issue. But one thing that was suggested that you might try is to turn on the new mobile framework and see if the problem persists. Apologies for the inconvenience this is causing!

Just curious if this updated framework will also enable other features down the road like Notice Banner of some sort?

Splash page is nice but would be nice to have a notice banner that could just slide a 1/4 down to announce/Remind users of something (App hasn’t sync in 30min, please sync soon or Reports Uploading in progress Please Don’t close the App!) XD

Our flight crews always need a Nudge/reminder when they land and need to complete various reports

Thank you for everything it’s been game changing.

1 Like

I am creating a service booking app for my customers, but i am new to the appsheet with lack of knowledge about programming language. please help me to get more information that how to create a service booking app to public and our customers.

@FlyingRacoon I’ll note this down as a feature request!

2 Likes

@lizlynch I will try with new mobile framework. Thanks for Suggestion.

My users are reporting missing map pins when zooming in and out on the app, not sure if it’s a geocoding limit thing (we didn’t have this problem on the older UI version)

Maybe it’s a coding thing that streamlines seen data on the screen and not the surrounding geocoded locations?


All addresses are geocoded ones from googlemaps, eg. JXJ7+8HR Keaau, Hawaii, USA

I sort of read somewhere where Im forcing google to reverse code them back into latlong anyway?
should i just change all my addresses to latlong?


Context

  1. app has over 6000 locations
  2. user can open locations in groups of 10-40 each, can open multiple locations at once, but usually limited to 2-3 groups of the same area

i have resolved this problem by just hard converting every compound google address to a latlong() value. (maybe something i should have done since the beginning, but never ran into map display problems until now)

might be something to look into for other apps that use compound google addresses (geocoded?) as their map pin indicator, and not latlong()

"Hi @saravana_ni,
Thanks for reporting this issue in detail. It does sound like an APK-related bug rather than your app logic. Since you’ve already reported it to support, I’d recommend keeping an eye on updates or patches that might be rolled out soon. In the meantime, you could try testing the app on a different APK build or device version to confirm whether the behavior is consistent. Sharing logs or screen recordings with support might also speed up resolution.