Answered
We have built some rather long and detailed apps and now that we have them built they are way too slow to be practical. Has anyone out there had issues with the apps being to slow? Is it the size of the field or the complexity of the field conditions that make it lag? Any suggestions? We were hoping to build an inspection app that allowed us to quote what was needed for repairs while conducting the inspection. Any solutions for that problem?
0
Comments
Please sign in to leave a comment.
Hi Michelle,
Slowdown tends to be a combination of large amounts of reference data and the device more than anything else. That said, having lots of fields on one screen, with lots of conditions, can also cause some slowness.
What I'd probably recommend for what you're trying to do is using something like this: https://help.gocanvas.com/hc/en-us/community/posts/360000466967-Grouping-forms, which involves automatically creating a dispatch. So you could take the data from the inspection part to pre-populate the data in the quote, which would technically be in a different app, but they wouldn't have to fill in any additional data if they didn't want to, just submit. Two different apps, but hooked together.
The other thing I'd look at (which may not apply in this case, but is a good practice) is the Mobile Client Version Report (which can be found in Account > Reports). You can make sure everyone is up to date with the latest version of the GoCanvas App (check versions here: https://help.gocanvas.com/hc/en-us/articles/115006822148-What-is-the-current-version-of-GoCanvas-for-my-device-). Users should also make sure their OS is as updated as possible.
I have a recent app that is fully dynamic, in that all questions are driven by reference data and screen and field conditions to only show questions related to a specific site. It has 1,350 field conditionals, 1,350+ reference data linked fields, and 15 conditional screens. The reference data file is 10,000+ rows long. Overall it takes <20 seconds to load initially, but once loaded the interactions between fields and screens is reasonable at a second or two for transition.
I split the reference data on region to cut it to 2,000 rows, but the time improvement was just a couple seconds, which led me to conclude that in my case it's mostly the field conditionals that cause the lag, and only initial load. I've notified users of the delay for this app, and it is usable for our purposes.
I'm curious whether your lag is just the initial load, or lag on transitions between screens and fields?