Importing a prototype assumes interaction of testers with the prototype through the built-in Figma display mechanism, allowing almost unrestricted use of Figma's features.
How Testing Figma Prototypes in Wynde Works
Optimizing the Prototype
Figma prototypes consume a lot of RAM if they are not optimized. This can result in some testers being unable to open the prototype and complete the task, especially if they’re using mobile devices.
We have prepared a few simple recommendations to minimize these issues. By following these recommendations, we estimate that problems occur in less than 1% of respondents on PCs and 1-3% on mobile devices.
Restrictions
All prototypes are displayed exactly as they are in Figma, but there are a few technical restrictions:
Changes made to the prototype within Figma are reflected in real-time during testing. However, it's crucial to re-import the prototype after making any changes to the file. Failing to do so may lead to irreversible issues in the report.
We recommend making all necessary changes to the prototype before inviting respondents to the test.
💡 Please note: When re-importing the prototype after making changes, ensure you do this within the same block by removing the prototype itself, not deleting the block. Otherwise, any responses associated with that block will be lost along with it.
Figma allows adding videos inside prototypes, but currently, this feature is not supported for testing in Wynde.
Reports may display incorrectly when you enable a device frame in your prototype. If the frame is necessary for testing, enable it during testing and disable it when analyzing results.
All other features are available with no restrictions, but it is important to understand how to analyze results. We strongly recommend that the person assembling the prototype reads the article on prototype testing mechanics.