The iPad is obviously not as powerful as a desktop so you can expect things to be slower.
In the script workspace make sure to look at your scripts with the "ios compatibility" toggled on so that you can see if you are using script steps that are not supported in FM Go,
thank you for you r time. this lag causes crashes and makes manually writing data faster.
Performance also depends on what you're trying to do - lots of unstored calls or summary fields, complex relationships, portals, graphics, etc will chew up bandwidth. You want any iOS layouts to be as lean as possible.
Thank you for your posts.
At what point does it crash? What actions were you taking when it crashed? Were you running a script? Does the crash occur on a specific layout? How many tables are in the database? How many objects are on the layout? Do you have layouts specifically designed for iOS devices?
Any other information you can provide may be helpful in narrowing down possible causes.
Thanks for your post. I ran into a similar issue with an iPad app and repeated the steps to make it crash on the desktop using the script debugger in FileMaker Advanced. In my case managed to narrow it down to a set field that was using a calculation that had a bug in it.
If a script is causing the problem you can put multiple comments steps into the script. This will allow you to step through the script so you can isolate the problem. Are you using layouts that are optimized for an iPad? I suspect you are using the same layout that you use on a PC. How big if the file and are you opening the file on a layout that has a lot of objects, portals, calcs, conditional formatting, and container fields?