Prepare your Figma file

urTRACE follows the structure of your file, so a little tidiness up front keeps the imported prototype faithful to what you designed.

• One frame per screen. Build each screen as its own Figma frame - frames are what urTRACE brings in as testable screens.
• Use a clear naming scheme. Name your frames, layers and components descriptively - names carry all the way through to your results, so a click on "Add to cart" is reported as exactly that, not "Frame 42".
• Wire the navigation. On tap → Navigate to connections, overlays and menus, Back/Close, and component variants (Change to) all carry over and work for testers.
• Design at real size, with common fonts. Work at the true device size; Google Fonts and system fonts come through faithfully (self-hosted by urTRACE, so testers' browsers never talk to Google). Keep each icon grouped and give each text size its own layer.
• Know the one gap. Logic built on Figma Variables - conditionals, counters, typed text - and drag/smart-animate interactions aren't exposed by Figma's API, so they can't transfer. That's what urTRACE Variables and Paths exist to replace.