Prepare your Figma file

A few settings in Figma avoid most surprises when publishing.

1. Share by link

Your testers see the prototype through Figma. It must therefore be accessible by link: in Figma, click Share, then set access to “Anyone with the link” and “can view”. This setting applies to the Figma file: making only the prototype public isn’t enough. Figma then only shows the prototype’s current state, not the version frozen at publishing, and your testers see a blank screen.

Until the first session arrives, DASHUND checks this setting and warns you on the Dashboard if Figma asks testers to log in. A password-protected file is accepted, but your testers will see Figma’s password screen: best avoided, unless the test is very confidential.

2. Set a flow starting point

In Figma’s Prototype mode, every flow starts with a starting screen. The plugin offers you the file’s flows: without a starting point, there’s nothing to publish.

3. Connect the screens with interactions

DASHUND keeps the starting screen and every screen and overlay that can be reached from it through the prototype’s interactions. A screen that isn’t connected to anything isn’t imported.

4. Choose the prototype’s device

The frame chosen in the Figma prototype settings (phone, tablet, desktop) is the one your testers will see. Screens taller than the device screen scroll normally.

What DASHUND changes in your file

Just one thing: when publishing, the plugin creates a named version in the file’s version history. That’s the one all your testers will see, even if you keep changing the design afterwards. No layer is changed.