If you import your working file with potentially hundreds of additional frames instead of the dedicated testing file, this could make it impossible for testers on mobile devices to take the test. This ensures a clean and lightweight testing file.

Remove any pages, frames, assets, images, and elements not relevant to testing before importing. Duplicate your working Figma file, then use the copy for the prototype that you'll use for testing with Maze. We highly recommend following these tips to optimize your Figma prototypes for Maze, especially if you see that your prototype takes a while to load or is crashing for testers:Ĭreate a dedicated testing file. This might cause importing issues, or make your prototype slow to load and respond for testers. When you import your prototype into Maze, all frames and pages within that file have to be loaded and processed. Optimizing your Figma files and prototypes ensures a light testing experience, and avoids biased data such as give-ups or bounces due to performance issues.īefore publishing your maze live, always confirm that the prototypes within your tests are performing as expected. Files that are too large may lead to loading issues when importing prototypes as well as when testing. Keep in mind that Figma files can become quite large, either because they include multiple pages with lots of additional frames, or because the prototype frames are very large and/or contain high resolution embedded PNGs. On iOS devices, the memory limits implemented by Apple may cause the test to time out and crash completely. Mobile device users in particular can struggle to open the file because of the relatively small amount of memory they have.

This allows you to take advantage of many of their native features, but it also means that Figma has to load your entire file when loading Figma prototypes in Maze. We use Figma's prototype embed feature when loading Figma prototypes so that your prototypes render exactly as they appear in Figma. Why it's important to optimize your Figma files and prototypes

We don't support interactive components yet.

Have at least two screens in your Figma prototype and hotspots on the first screen linking to the second.

If you don't, the prototype preview will not load and testers won't be able to view your prototype in the test.

Set the permissions for your Figma file and prototype to Anyone with the link can view.

This ensures shorter loading times and decreased payload for testers. To take advantage of the fast and efficient testing provided by Maze, we recommend optimizing your Figma prototype before importing it into Maze.