Bird
Raised Fist0
Figmabi_tool~8 mins

Interactive components in Figma - Dashboard Guide

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Dashboard Mode - Interactive components
Dashboard Goal

Understand how interactive components like filters and slicers help explore sales data by region and product category.

Sample Data
Date Region Product Category Sales Amount
2024-01-15 North Electronics 1000
2024-01-20 South Furniture 1500
2024-02-05 East Electronics 1200
2024-02-10 West Furniture 1300
2024-03-01 North Furniture 1100
2024-03-05 South Electronics 1400
Dashboard Components
  • KPI Card: Total Sales
    Formula: SUM of Sales Amount
    Result: 7500
  • Bar Chart: Sales by Region
    Shows total sales for each region from the filtered data.
  • Pie Chart: Sales by Product Category
    Shows sales distribution by product category.
  • Table: Detailed Sales Data
    Shows rows filtered by selected region and category.
  • Filter: Region Selector
    Dropdown to select one or multiple regions.
  • Filter: Product Category Selector
    Dropdown to select one or multiple product categories.
Dashboard Layout
+----------------------+-----------------------+
|      Total Sales      |   Region Filter       |
|      (KPI Card)       |  (Dropdown Selector)  |
+----------------------+-----------------------+
|  Sales by Region Bar Chart                  |
|  (Horizontal Bar Chart)                     |
+--------------------------------------------+
|  Product Category Filter | Sales by Category |
|  (Dropdown Selector)     | (Pie Chart)       |
+--------------------------+------------------+
|               Detailed Sales Table          |
+--------------------------------------------+
Interactivity

The Region Filter and Product Category Filter let users pick which data to see.

When a user selects a region or category, the KPI Card, Bar Chart, Pie Chart, and Sales Table update to show only data matching those selections.

This helps users explore sales performance by different areas and product types easily.

Self Check

If you select Region = North in the Region Filter, which components update and what changes?

  • KPI Card: Shows total sales only for North region (1000 + 1100 = 2100).
  • Bar Chart: Bars update to show sales only for North region.
  • Pie Chart: Shows sales distribution by product category only for North region.
  • Sales Table: Shows only rows where Region is North.
Key Result
Interactive sales dashboard with filters for region and product category updating KPIs, charts, and tables.

Practice

(1/5)
1. What is the main purpose of interactive components in Figma?
easy
A. To make designs respond to user actions like clicks and hovers
B. To create static images for presentations
C. To export designs as PDFs
D. To write code for apps

Solution

  1. Step 1: Understand interactive components

    Interactive components allow designers to add user interactions like clicks and hovers to their designs.
  2. Step 2: Identify the purpose

    The main goal is to make designs feel real by responding to user actions, not just static images or exports.
  3. Final Answer:

    To make designs respond to user actions like clicks and hovers -> Option A
  4. Quick Check:

    Interactive components = respond to clicks and hovers [OK]
Hint: Interactive means user can click or hover [OK]
Common Mistakes:
  • Confusing interactive components with static images
  • Thinking interactive components are for exporting files
  • Assuming interactive components involve coding
2. Which of the following is the correct way to create different states of a component in Figma?
easy
A. Duplicate the frame and rename it
B. Use multiple separate components without variants
C. Create variants inside a single component set
D. Add layers inside the component without variants

Solution

  1. Step 1: Recall how to create states

    Figma uses variants inside a component set to represent different states like hover or clicked.
  2. Step 2: Identify the correct method

    Creating variants inside a single component set is the proper way to manage multiple states efficiently.
  3. Final Answer:

    Create variants inside a single component set -> Option C
  4. Quick Check:

    Variants = different states in one component [OK]
Hint: Variants group states inside one component [OK]
Common Mistakes:
  • Using separate components instead of variants
  • Duplicating frames without linking states
  • Adding layers but not creating variants
3. Given a component with two variants: Default and Hover. If you connect the Default variant's 'While hovering' interaction to the Hover variant, what happens when you preview and hover over the component?
medium
A. The component disappears
B. Nothing happens because interactions are not set
C. The component switches to Default variant permanently
D. The component changes to the Hover variant while the mouse is over it

Solution

  1. Step 1: Understand the interaction setup

    The 'While hovering' interaction triggers a change from Default to Hover variant when the mouse is over the component.
  2. Step 2: Predict the preview behavior

    When previewing, hovering causes the component to switch to the Hover variant temporarily.
  3. Final Answer:

    The component changes to the Hover variant while the mouse is over it -> Option D
  4. Quick Check:

    Hover interaction = switch to Hover variant [OK]
Hint: Hover triggers variant change on mouse over [OK]
Common Mistakes:
  • Thinking interaction does nothing without clicks
  • Assuming variant switches permanently
  • Believing component disappears on hover
4. You created two variants named 'Default' and 'Clicked' but when you prototype, clicking the component does not switch variants. What is the most likely error?
medium
A. You forgot to add an interaction linking 'Default' to 'Clicked' on click
B. Variants must have different names to work
C. You need to duplicate the component instead of using variants
D. Figma does not support click interactions

Solution

  1. Step 1: Check interaction setup

    Variants alone do not switch automatically; you must add an interaction in Prototype linking 'Default' to 'Clicked' on click.
  2. Step 2: Identify the missing step

    Without this interaction, clicking does nothing, causing the problem.
  3. Final Answer:

    You forgot to add an interaction linking 'Default' to 'Clicked' on click -> Option A
  4. Quick Check:

    Missing interaction = no variant switch [OK]
Hint: Add click interaction to switch variants [OK]
Common Mistakes:
  • Assuming variant names cause issues
  • Duplicating components instead of using variants
  • Believing Figma lacks click support
5. You want to create a button with three states: Default, Hover, and Clicked. How should you set up the interactive component to handle all user actions smoothly?
hard
A. Create three separate components and link them manually in Prototype
B. Create three variants and add interactions: Default to Hover on 'While hovering', Hover to Default on 'Mouse leave', Default to Clicked on 'On click', and Clicked back to Default on 'After delay'
C. Use one variant and change colors manually during preview
D. Create two variants only and ignore the Clicked state

Solution

  1. Step 1: Plan variants for all states

    Create three variants named Default, Hover, and Clicked to represent each button state.
  2. Step 2: Add interactions for smooth transitions

    Link Default to Hover on 'While hovering', Hover back to Default on 'Mouse leave', Default to Clicked on 'On click', and Clicked back to Default on 'After delay' to simulate button behavior.
  3. Final Answer:

    Create three variants and add interactions: Default to Hover on 'While hovering', Hover to Default on 'Mouse leave', Default to Clicked on 'On click', and Clicked back to Default on 'After delay' -> Option B
  4. Quick Check:

    Variants + interactions = smooth multi-state button [OK]
Hint: Use variants plus interactions for all states [OK]
Common Mistakes:
  • Using separate components instead of variants
  • Not adding reverse interactions for hover
  • Ignoring the Clicked state