Overview
We use Figma's prototype embed feature when loading Figma prototypes so that your prototypes render exactly as they appear in Figma. This allows you to take advantage of many of their native features, but it also means that you may encounter issues when loading particularly large Figma prototypes or files in Maze.
Mobile device users in particular can struggle to open tests associated with large Figma files or prototypes because of the relatively small amount of memory they have. On iOS devices, the memory limits implemented by Apple may cause the test to time out and crash completely or you may be returned to the welcome screen repeatedly.
Importing a file containing large frames or too many frames could severely impact loading times, and cause issues when importing and testing. Figma has to use up memory to render frames; the bigger and more numerous the frames, the more memory Figma needs. Very tall frames in particular can trigger performance trouble for testers as iOS limits the size of images that it will display and Figma frames count as images for this limit.
If your Figma file contains large frames or too many frames, you'll see the following warning before importing your prototype:
Large frames: Files with large or too many frames may load slowly or time out during testing. Consider limiting your frames.
Solution
If you're seeing this warning, before importing we recommend limiting the number as well as the height/width of your frames and scrollable containers, so that they're still representative of the design you’re trying to test but require Figma less memory to load them.
Tall, scrollable frames are often necessary to test a design, but we recommend making them only as large as necessary to successfully test the UX you’re exploring. For example, a frame that is 375 × 10,000 px is large enough to trigger iOS' built-in memory limits on older iPhones and your test may crash as a result.
Sizing down your prototype to match the scope of your test makes the creation of a test a lot smoother.