Hello, I have a problem I don’t know if it is from Appgyver or from my PC. When I started using Appgyver everything was going smooth however now after having spent about two weeks on it and configured about 20 pages the system is very slow and it takes too long to save and sometimes I need to press many times on save to be able to save. Please I would like to know if Appgyver has a maximum capacity if yes what is it?
Thank you.
It is true that Appgyver can run a bit slower as your app’s complexity increases. It also may be determined (to an extent) by the “power” of your development computer. Pages almost certainly play a role. We try to use as few pages as possible, but with 10-15, saving can take 2-5 seconds on average to save, and very rarely, 5-7 seconds.
Hi!
No maximum capacity per se, but there are certain patterns you should avoid to keep your app performing best you can:
- Use replace page instead of open page whenever it makes sense
- Check all your data variables and remove the looping logic unless it’s absolutely necessary
- Don’t run logic more than necessary in general, especially loops are dangerous since on mobile all pages that have been opened below the current page or are open in another tab are active and their logic is running
- For long lists, use recyclerview.
3 Likes
Hi, Mevi. Replace Page vs. Open Page? Just learning about this. Is there reason or benefit to using one over the other? Replace Page is not in the core logic stack, so I never knew it existed before now.
Are there specific use cases? “Whenever it makes sense” doesn’t really say much as to whether to use Replace Page as the go-to or secondary option.
Thank you.
So, if you have page A, page B (which you open from page A) and page C (which you open from page C), use open page from B to C whenever you want to (on mobile) keep page B running and ready in the background, and available to navigate back to from page C. If you don’t need to keep page B running and don’t need to navigate natively back to page B, you can use replace page from B to C. If you make a custom navigation bar (and don’t need to keep page B running) you can also use replace page. On web I don’t know if there’s a real difference, because on web the navigation stack doesn’t exist in a similar way 
Use case where I use replace page:
I have a list page (page A) for orders. From page A, I open a details page (page B) which shows the information of one order. From page B, I can navigate forward/backward in the list of orders, that is, I use replace page to replace B with another version of page B (different page parameter id). That way when the user wants to go back to the list, they press the native back button and it goes straight to page A instead of having to go through X amount of page B’s, and also any logic on page B does not remain running for the earlier instances opened in between.
1 Like
Hello Mevi,
I am still facing the same problem the app is very slow and now I am not even able to see my build, the system keeps loading. please here is my id: 200902 if you can check what is the problem. Please I need a response as soon as possible.
Thank you
Hello,
Thank you for your reply.
I have tried to continue working on my project but the same message appears " Failed to save application data" please see the screenshot.
Please it would be very helpful if one of your team could assist me 10 or 15 minutes by Teamviewer to see what is the exact problem and understand if I can follow working on my project with Appgyver or I need to change the App.
Thank you.
Just saw this. Thank you, Mevi. This makes sense for me. It’s almost like storing a cache of data from the previous page, versus loading the page with “fresh” data and discarding the previous data.
1 Like