I’ve been conducting some intensive performance benchmarks on a complex AppSheet app I’m developing. To simulate a heavy load environment on a standard Android device, my team has been using the latest game builds running in the background.
For anyone who wants to replicate the test conditions, you can (URL Removed by Staff). We found it provides a consistent baseline for our tests.
Our goal is to ensure our AppSheet application remains responsive and fluid even when the system’s resources are being heavily utilized. We’re providing this feedback in case the AppSheet team finds it useful for future optimization.
Observed Issues Under Load
When running our AppSheet app concurrently with the game, we’ve noted the following performance dips:
UI Rendering: A noticeable lag in rendering complex views and dashboards within the app.
Data Sync: Sync operations take approximately 15-20% longer to complete.
Expression Evaluation: Delays in real-time calculations, especially with complex virtual columns.
Battery Impact: A more significant battery drain than expected from the AppSheet process alone.
Test Environment Details
We believe a robust app should handle these conditions gracefully. Here are the specifics of our testing setup:
Device: Google Pixel / Samsung Galaxy (tested on both)
We are wondering if anyone else has conducted similar stress tests on their AppSheet creations. Are there any known best practices for optimizing app performance on devices under heavy graphical and processing loads from other applications?
Any feedback or suggestions would be greatly appreciated. Thanks
This is more so a test of the device’s capability to handle multiple resource heavy processes.
When the device is being taxed in the way it sounds here, you SHOULD expect app and battery performance to suffer. This is not an indication of any kind of failure of the AppSheet app.
What you HAVE proven is that Appsheet still performs well under a device load!
That’s a really insightful way to stress-test an AppSheet setup, and your findings make a lot of sense under that kind of heavy load. The UI lag, sync delays, and battery impact feel expected, but it’s still great data for optimization and real-world reliability. Curious to see if others notice similar behavior or have tuning tricks to share.