Testing responsive designs in prototype in Figma - Dashboard Guide

Dashboard Mode - Testing responsive designs in prototype

Goal

How to test if a dashboard prototype adapts well to different screen sizes using Figma's responsive design features.

Sample Data

Screen Size	Width (px)	Height (px)	Expected Layout
Mobile	375	667	Single column, stacked cards
Tablet	768	1024	Two columns, cards side by side
Desktop	1440	900	Three columns, full dashboard
Large Desktop	1920	1080	Three columns with extra spacing
Small Desktop	1024	768	Two columns, compact layout

Dashboard Components

• KPI Cards: Show total sales, total customers, and average order value. Use auto layout with constraints to resize horizontally.
• Bar Chart: Monthly sales by region. Set to resize width with container.
• Filter Panel: Region and date slicers pinned to top-left, collapsible on small screens.
• Navigation Menu: Horizontal on desktop, hamburger menu on mobile.

Responsive Settings: Use Figma constraints and auto layout to make components adapt. For example, KPI cards stack vertically on mobile but align horizontally on desktop.

Dashboard Layout (ASCII Art)

+-----------------------------+
| Filter Panel    | Nav Menu   |
+-----------------------------+
| KPI Card 1 | KPI Card 2 | KPI Card 3 |
+-------------------------------------+
|           Bar Chart                 |
+-------------------------------------+

Responsive changes:
- Mobile: Filter Panel collapses, Nav Menu becomes hamburger
- KPI Cards stack vertically
- Bar Chart resizes to full width

Interactivity

Filters update the bar chart and KPI cards dynamically. On mobile, filter panel can be toggled to show or hide. Navigation menu changes layout based on screen size. Prototype uses Figma's device frames to preview responsiveness.

Self Check

Try resizing the prototype frame to tablet size (768x1024). Which components change layout? What happens to the navigation menu and filter panel?

Key Result

A Figma prototype dashboard that adapts layout and navigation for mobile, tablet, and desktop screen sizes using responsive design features.

Practice

1. What is the main purpose of testing responsive designs in a Figma prototype?

easy

A. To add more colors and fonts to the design

B. To ensure the design adapts well to different screen sizes and devices

C. To create static images for presentations

D. To export the design as a PDF file

Solution

1. Step 1: Understand responsive design goals

   Responsive design means the layout changes smoothly on different screen sizes.

2. Step 2: Identify prototype testing purpose

   Testing ensures the prototype looks and works well on phones, tablets, and desktops.

3. Final Answer:

   To ensure the design adapts well to different screen sizes and devices -> Option B

4. Quick Check:

   Responsive design = adapt to devices [OK]

Hint: Responsive means design fits all screen sizes [OK]

Common Mistakes:

• Confusing responsive testing with adding colors
• Thinking prototypes are only for static images
• Believing exporting files is the main goal

2. Which Figma feature helps you test how your prototype looks on different devices without manually resizing?

easy

A. Device presets in prototype mode

B. Pen tool for drawing shapes

C. Text styles for fonts

D. Export options for images

Solution

1. Step 1: Identify prototype mode features

   Figma prototype mode includes device presets like iPhone, iPad, desktop.

2. Step 2: Understand device presets use

   These presets simulate screen sizes automatically without manual resizing.

3. Final Answer:

   Device presets in prototype mode -> Option A

4. Quick Check:

   Device presets = auto screen size test [OK]

Hint: Use device presets to avoid manual resizing [OK]

Common Mistakes:

• Confusing pen tool with prototype testing
• Thinking text styles affect responsiveness
• Believing export options help test layouts

3. In a Figma prototype, if a frame uses Auto Layout with horizontal direction and fixed width, what happens when you preview on a smaller screen?

medium

A. The prototype shows an error and stops

B. The content automatically stacks vertically

C. The frame resizes to fit the screen width

D. The content overflows and may be cut off

Solution

1. Step 1: Understand Auto Layout with fixed width

   Fixed width means the frame size does not change with screen size.

2. Step 2: Predict behavior on smaller screen

   Since width is fixed, content won't shrink or stack, causing overflow.

3. Final Answer:

   The content overflows and may be cut off -> Option D

4. Quick Check:

   Fixed width + small screen = overflow [OK]

Hint: Fixed width frames don't resize on small screens [OK]

Common Mistakes:

• Assuming Auto Layout always stacks content
• Thinking fixed width frames resize automatically
• Believing prototype crashes on overflow

4. You notice your prototype frame does not resize on mobile preview despite using constraints. What is the likely cause?

medium

A. The frame has a fixed width set instead of 'Fill container' constraint

B. Auto Layout is not enabled on the frame

C. You forgot to add interactions in prototype mode

D. The prototype is set to desktop device preset

Solution

1. Step 1: Check constraints settings

   Fixed width prevents resizing; 'Fill container' allows flexible width.

2. Step 2: Understand effect on mobile preview

   Fixed width frames stay same size, ignoring smaller screen width.

3. Final Answer:

   The frame has a fixed width set instead of 'Fill container' constraint -> Option A

4. Quick Check:

   Fixed width blocks resizing [OK]

Hint: Use 'Fill container' for responsive width [OK]

Common Mistakes:

• Thinking Auto Layout alone fixes resizing
• Confusing interactions with resizing issues
• Ignoring device preset impact on resizing

5. You want your Figma prototype to adapt fluidly on all devices, stacking elements vertically on narrow screens and horizontally on wide screens. Which combination helps achieve this?

hard

A. Use only constraints without Auto Layout and rely on device presets

B. Set fixed widths on all frames and manually resize for each device preset

C. Use Auto Layout with horizontal direction and add a component variant for vertical layout triggered by screen width

D. Create separate prototypes for each device size without responsive features

Solution

1. Step 1: Understand layout direction control

   Auto Layout direction controls stacking horizontally or vertically.

2. Step 2: Use component variants for responsiveness

   Variants can switch layouts based on screen width or user interaction.

3. Step 3: Combine Auto Layout and variants for fluid design

   This allows dynamic switching between horizontal and vertical stacking as screen size changes.

4. Final Answer:

   Use Auto Layout with horizontal direction and add a component variant for vertical layout triggered by screen width -> Option C

5. Quick Check:

   Auto Layout + variants = fluid responsive design [OK]

Hint: Combine Auto Layout and variants for flexible layouts [OK]

Common Mistakes:

• Relying only on fixed widths and manual resizing
• Ignoring Auto Layout's power for stacking
• Creating multiple prototypes instead of responsive design