Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 36 ยท Prototyping and Interactions

Prototyping Basics

Learn how to connect Figma frames into a clickable prototype: the Prototype tab, flow starting points, connections and how to present and test.

A static design shows what a screen looks like. A prototype shows how it behaves. In Figma you connect frames with interactions so that clicking a button moves to another screen, a menu opens, or a card expands. Anyone with the link can click through it in a browser or on a phone, without writing code.

Prototyping is not coding, but it rewards the same thinking: states, transitions and paths. This lesson covers the building blocks.

Figma cannot run on this site, so there is no live prototype here. The code examples are labelled JavaScript stand-ins that model flows as graphs and let you check them. They are not Figma's engine.

The Prototype tab

At the top of the right panel there are tabs for Design, Prototype (and in Dev Mode, Inspect). Switching to Prototype changes the canvas: frames show small connection handles, and the panel lists interactions, flows and device settings.

To connect two frames:

  1. Select the layer that should respond (a button, a row, or the whole frame).
  2. Click the + next to Interactions or drag the circular handle that appears on its right edge.
  3. Drop it on the destination frame.
  4. Choose a trigger (for example On click), an action (Navigate to) and an animation (Instant or Smart animate).

A blue arrow now links the layer to the frame. Selecting the arrow shows its settings.

Flow starting points

A flow is a named path through your design, such as "Checkout" or "Onboarding". Mark the first frame by clicking the + next to Flow starting point in the Prototype tab. Figma shows a play icon above the frame. You can have several flows in one file, and the Present menu lets viewers choose.

Name flows after user goals, not screens: "Create account" is more useful than "Flow 1".

Device and background settings

Select a frame with nothing else selected to see its prototype settings:

  • Device: choose a phone, tablet, desktop or custom size. This only controls the frame shown during presentation.
  • Background: the color around your frame in the player.
  • Show device frame / hide: affects only the presentation.

These do not change the design itself, so they are safe to adjust at any time.

Presenting and testing

Click the Present button (a play icon at the top right) to open the prototype in a new tab. Use the keyboard, click hotspots, and press R to restart. Enable Show hotspot hints to see clickable areas; a tap anywhere else flashes the hotspots to guide testers. Share the link with teammates, or open the Figma mobile app to try the design on a real phone, which is the best test for touch targets.

flowchart LR
    A["Welcome"] -->|"Get started"| B["Sign up"]
    A -->|"Log in"| C["Log in"]
    B -->|"Create account"| D["Home"]
    C -->|"Continue"| D
    D -->|"Profile icon"| E["Profile"]
    E -->|"Back"| D

A flow is a directed graph: frames are nodes, interactions are edges.

Thinking of a prototype as a graph

Every prototype is a graph, which means you can check it for common mistakes: unreachable screens, dead ends where users get stuck, or loops with no exit. The stand-in below checks a flow's reachability.

JS Stand-in: check a prototype flow for dead ends

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Orphan is a frame no one can reach, and Settings has no exit, so a tester would be stuck. In Figma the usual fix is to add a Back interaction.

The Back action and history

Back returns to the previous frame in the history of the session, not to a fixed frame. That is the right choice for a back arrow, because the same screen can be reached from several places. If you wire "Back" as Navigate to a specific frame, the user will end up in the wrong place after arriving from another route.

A long page can use Scroll to to jump to a section when a nav link is clicked, rather than moving to another frame. Use it for landing pages with anchor links.

Planning flows before connecting

Wiring a large prototype is easier after you list frames and links on paper. The stand-in below turns a simple text list into a connection summary and counts how many interactions you need.

JS Stand-in: plan interactions from a list

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Good habits

  • Prototype only the flows you need to test. A 40-screen prototype that nobody walks through wastes time.
  • Use component variants with interactions for repeated behaviors (toggles, tabs), so you wire them once.
  • Always test on the target device size. A hover-only idea does not work on a phone.
  • Keep frame names unique; the Present menu and the Back history are easier to follow.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where do you create interactions between frames?

    Interactions are created in the Prototype tab of the right panel.
  2. 2. What does a flow starting point do?

    A flow starting point defines where a named path through the prototype begins.
  3. 3. A back arrow should use which action?

    Back returns to the previous frame in the session history, even if it was reached from different places.
  4. 4. A frame that no interaction leads to is called...

    Unreachable frames cannot be visited in the prototype.

Summary

  • Prototypes connect frames with interactions made of a trigger, an action and an animation.
  • Flow starting points name each path; present it with the Present button or the mobile app.
  • Treat a prototype as a graph and check for unreachable frames and dead ends.
  • Use Back for back arrows, and test on the real device size.

Next: Triggers and Actions