I’ve been developing an app in Adalo, and I’ve noticed that the longer the app runs, the slower it becomes. This happens only a published test version. It almost feels like a memory leak—maybe data isn’t being cleared properly?
Has anyone else experienced this? If so, did you find any solutions or optimizations that helped improve performance?
I’d really appreciate any insights or troubleshooting tips! Thanks in advance.
I have found this previously, it would happen when clicking through on a nested custom list. The list itself would run slower than the rest of the app, I was fine accepting this as it was the only way I could show the information I needed.
Coming back out of the list, I would find a decrease in app speed across the rest of the screens.
Closing the app and reopening was the only way to stop it.
I didn’t find a fix although I’ve moved over to a standard Adalo list (still nested) and I’ve barely noticed it happening.
Thankfully all the recent performance improvements that Adalo have also helped.
Unfortunately It is quite difficult to debug such things as our capabilities are quite limited.
As @diegozane mentioned, sometimes slowness can be caused by certain list configurations. In my experience this could depend on the list themselves and amount of data as well.
Also I suspect that app performance may depend on the screens flow. If you are creating “Loops” and use Link To (E.g. Home → Screen A → Home → Screen A → …), all previous screens are stored in memory and continue consuming resources.
What is worse, lists on these previous screens may continue refreshing (I am not sure about this, it was definitely the case few years ago, but now maybe Adalo optimised that). Also animated components and timers may continue working.
So if you can use “Link Back”, that will “clean up” the screen you’re leaving, therefore saving memory & improving speed.
Thanks for the feedback. I already have “link back” on almost all screens. I uploaded a video to Gdrive (https://drive.google.com/file/d/1XlPFhy_9jvG4pKTJQpVA_iGuYLCalyo4/view?usp=sharing) so you can see what I mean by the app is slow. Its almost unusable at this stage. I already changed most lists to simple lists and reduced items, grouped them, avoided nested lists etc. If you have any idea on how to improve the app I would be forever grateful.
I have the same issue. I only use a simple list with pagination (component from NoCode Monkey). The transition from list screen to list detail screen is fast only for the first record. The next list item when clicked freezes for 3 to 5 of seconds before it goes to the list item Details screen. The “back” transition from Details screen to List screen is fast.
I know there are works being done to speed up native apps but this is a “show-stopper” I cannot launch the app with the current state of performance. I currently have only 500 test user records that I filter the displayed list from. I am expecting about 2k to 3k users when the app is launched. I have been doing load tests so that there will be no surprises when the app is in market. Its a good thing I did as everything works great with 20 user records!
Here are the videos for comparison:
Native iOS
The above issue becomes worse with displayed list size…up to 8 seconds for a filtered list size of 100. I therefore only try to show about 50 items filtered. This same effect can be seen in both iOS & Android.
PWA PWA however works lightning fast
Any pointers would be welcome but I think I have already plucked the low hanging fruit…simple list, filter records, uncomplicated details screen, back button.
I converted an MP4 to GIF. The app, both PWA & Native is nowhere jerky as shown
I just looked over the video…I wish the list in my app could have these screen transitions. However I have observed that there are some parts where the items are slow to load. I have them too all over my app but I have a bigger fish to fry. You can see my post above with videos. I just hope the the native apps can be a quick as the PWA. I do understand your concerns