Are there some transitions in Adalo that are more performant because they don’t keep DOM elements in the background?
My app is unbearably slow at times and I’ve noticed that on some screens where I use a modal or push model, due to the animation style, it seems like the screen I animate from is still rendered in the background - I have a hypothesis this causes lag and uses up resources.
Has anyone else noticed that transitioning to new screens using a particular animation style performs more efficiently?
It would be amazing if Adalo devs themselves could provide some insights to this and have it as a resource in their docs.
I’ve spent a few hours testing to try isolate my performance issues and here is what I’ve found:
If I start on the first level of my app and navigate around everything is performant
If I click on a list and navigate to a details page, then go back to the first level things start to slow down
The more details pages I click on, the app starts to slow down
I broke my details page into multiple pages, so there is a second level sub details page. When I navigate to these pages and go back to home, the app starts to crawl
It appears the more pages I visit the slower the app gets, like it’s not releasing resources from page to page.
Note: these performance issues are on the iOS app. I do NOT have these issues in the Adalo previewer.
P.s. I’ve read most of the performance topics in the forums and been trying many of the suggestions, but generally am just getting the sense (have a hypothesis) that data and possibly images are being cached as I navigate around the app (so it loads faster) but it’s actually slowing things down because those resources are never released.