Skip to content
Tutorials Center
My learning

Topics

Lesson 34 of 36 ยท Projects and Practice

Project: Mobile Onboarding Flow

Design a three-screen mobile onboarding flow in Figma with components, variables, a prototype and an accessibility check, step by step.

In this project you design the first minute of a fictional app, "Leaf", a habit tracker. The goal is a short onboarding flow: a welcome screen, a goal-picker screen and a ready screen. You will use almost everything from this chapter: components, variants, variables, prototyping and a final quality check.

Figma cannot run on this site, so you will do the design in Figma yourself. The code blocks are labelled JavaScript stand-ins that check your measurements, as a replacement for eyeballing. Menu names may differ slightly between Figma versions.

The brief

  • Product: Leaf, a habit tracker for people who want to build one small habit at a time.
  • Platform: iPhone, frame 390 by 844.
  • Flow: Welcome -> Pick a goal -> You are ready -> (Home, not designed).
  • Constraints: a single primary action per screen, one illustration or icon style, light and dark mode, touch targets of at least 44 by 44, and body text at 4.5:1 contrast or higher.

Step 1: set up the file

  1. Create a file named "Leaf โ€“ Onboarding" with pages Cover, Foundations, Components, Screens.
  2. On Foundations, create variable collections:
    • Primitive: green-500 #16A34A, green-100 #DCFCE7, gray-900 #0F172A, gray-600 #475569, white #FFFFFF, gray-950 #020617, green-400 #4ADE80.
    • Semantic (modes Light and Dark): surface/default, text/primary, text/muted, action/primary, action/on-primary.
    • Spacing (numbers): space/1=4, space/2=8, space/3=12, space/4=16, space/6=24, space/8=32; radius/md=12, radius/full=999.
  3. Make text styles: Display 32/40 bold, Title 24/32 semibold, Body 16/24 regular, Caption 13/18 regular.

Step 2: check contrast first

Before drawing, confirm your color pairs. The checker uses the same formula as in Building a Design System.

JS Stand-in: contrast check for the Leaf palette

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

No output.

White on green-500 fails in Light mode (about 3.3:1). Darken the Light action color to green-700 #15803D and run the check again; keep dark text on the lighter green in Dark mode, as the sample does.

Step 3: build the components

Create these components on the Components page, all with auto layout and variable-bound fills and spacing:

  1. Button with variants Style = Primary | Secondary and State = Default | Pressed | Disabled. Text property Label. Height 52, horizontal padding space/6, radius radius/full.
  2. Goal card: icon (instance swap), title text, description text, and variants Selected = False | True. Selected has a 2 px primary border and a green-100 fill.
  3. Progress dots: component with a variant Step = 1 | 2 | 3.
  4. Status bar and home indicator placeholders so screens look realistic.

Step 4: lay out the screens

Create three 390 by 844 frames named 01 Welcome, 02 Goal, 03 Ready. Use auto layout in a vertical stack with padding space/6 and gap space/4.

  • Welcome: a large illustration area (an original simple shape composition), Display title "One small habit at a time", Body subtitle, a primary Button "Get started" pinned at the bottom with a secondary "I already have an account".
  • Goal: Title "What do you want to build?", four Goal cards (Move, Read, Sleep, Focus), progress dots at Step 2, and a primary Button "Continue" (Disabled until a goal is picked).
  • Ready: a check illustration, Title "You are all set", a Body line that repeats the chosen goal, and a primary Button "Start my first day".

Pin the buttons to the bottom by setting the content area to Fill container vertically so the Button stays at the bottom of the stack.

Step 5: check touch targets and the 8 pt grid

Use the stand-in to verify frame measurements. Fill the elements array from Dev Mode or the Design panel.

JS Stand-in: touch target and grid check

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

No output.

Fix flagged items: enlarge the close icon's hit area to 44 by 44 with transparent padding, and give the text link a 44 pt tall frame.

Step 6: prototype

  1. On 01 Welcome, select "Get started" and add On tap -> Navigate to 02 Goal with Smart animate or Push (right to left), 300 ms, ease out. Mark 01 Welcome as the flow starting point named "Onboarding".
  2. On the Goal screen, put interactions inside the Goal card component with Selected variants (on tap changes to selected). To keep one selection only, use a variable selectedGoal (String) set on tap, and bind each card's Selected variant to the condition. Enable Continue when selectedGoal is not empty by showing the Primary Disabled variant otherwise.
  3. Add Back to a back arrow.
  4. From Ready, Start button -> Open link or a placeholder Home frame.

Simulate the logic first to be sure the states make sense.

JS Stand-in: simulate the goal picker logic

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

No output.

Step 7: dark mode and review

Duplicate the three screens and set the frame mode to Dark. Everything bound to variables should flip. Anything that does not flip has a hard-coded color: fix it. Then:

  • Run an accessibility plugin or manually check order, labels and contrast.
  • Test the prototype on a phone with the Figma mobile app.
  • Share the prototype link and gather three comments from a friend.

Stretch goals

  • Add a localization mode (String variables) for Spanish.
  • Add an empty-state and an error state for the goal list.
  • Add motion: a check mark drawing in on the Ready screen.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the minimum recommended touch target size on iOS?

    Apple's guidance is a minimum of 44 by 44 points.
  2. 2. Why check contrast before building components?

    Color tokens are used everywhere, so errors multiply.
  3. 3. How do you get dark mode screens from the same design?

    Variables with Light and Dark modes switch values per frame.
  4. 4. Where should the 'Selected' behavior of goal cards live?

    Interactive components carry their behavior to all instances.

Summary

  • A small project can use the whole toolkit: variables, components, variants, auto layout and a prototype.
  • Check contrast, grid and touch targets early and again at the end.
  • Put behavior inside components and use a variable for shared state.
  • Dark mode is a variable mode, not a redesign.

Next: Project: Responsive Landing Page