Hi everyone,
I’ve been building a performance-tracking tool in Adalo, and while the experience in the desktop previewer is perfect, I’ve run into a recurring issue with the native mobile builds that I can’t quite isolate.
I’ve noticed that when a device is under high resource pressure—specifically when I’m running heavy background data updates or testing high-performance script executors—the app’s UI occasionally fails to render specific components. For example, my custom navigation icons and the “Submit” buttons intermittently disappear or become unresponsive to taps. While I was discussing these environmental bottlenecks with some developers who recently helped me when I had to visit this site to optimize my backend executors over at the arceusx community, I noticed that the mobile OS seems to throttle the app’s main thread when other high-load processes are active.
Has anyone else noticed that Adalo apps become “sluggish” or start dropping UI assets on mobile if there are other high-performance tasks running in the background? I’m also seeing occasional “Database Error” popups during these spikes, even though the connection is stable, which suggests a possible timeout in how the app handles API requests under heavy local load.
I’m trying to figure out if there’s a specific way to prioritize the app’s rendering thread or if I should be looking into a more aggressive caching strategy for my collection data to ensure UI consistency. If you’ve dealt with stabilizing the mobile experience for users who might be multitasking—or have tips on preventing these silent asset failures during heavy background processing—I’d really value your thoughts!
Thanks in advance for the help!