Two hands holding a phone with the Stitch Please! home screen

Case study · Ongoing hobby project

Stitch Please!

A mobile-first companion for crochet and knitting projects, from finding a pattern to the very last row.

My role
Solo project: concept, IA, design system & UI
Emphasis on
Variables, design tokens and UI
Tools
Figma (variables & components)
Timeline
Hobby project, ongoing

Overview

One place for every row, stitch and colour change

Crafters (such as myself) juggle paper notes, bookmarked PDFs and their own memory to keep track of where they are in a project. Stitch Please! brings it all together: pattern storage, project progress and material planning in one place, built around the rhythm of how people actually craft.

It is for anyone who picks up a hook or needles, from someone crocheting their first beanie to an experienced knitter running five projects at once. Beginners get clear guidance through setup, experts get fast access to tracking and their pattern library.

4
pillars: tracking, patterns, materials, sharing
3
main sections: Home, Projects, Patterns
128
variables in 4 collections, so light and dark switch with one mode

The process

I started from the craft itself: how people track their projects today and which apps already help. From there I defined the core problem and four pillars, built the information architecture and a design system, and designed the screens on top of it.

Double diamond: Discover and Define lead to the four pillars, Develop and Deliver lead to the design system and screens 01020304 DISCOVERDEFINEDEVELOPDELIVER divergeconvergedivergeconverge Four pillarsDesign system

01 · Discover

  • App concept
  • Best-practice research
  • Existing app review

02 · Define

  • Core problem
  • Four pillars
  • Target users

03 · Develop

  • Sitemap & IA
  • User flows
  • Variables & tokens

04 · Deliver

  • Components
  • Light & dark via modes
  • Start new project flow

Discover

Starting from the craft

Before designing any screens, I looked at how crafters keep track of their work today, and at the apps they already use: row counters, chart makers and pattern libraries.

Research

Four steps from idea to pillars

  1. 01

    App concept

    Defining who the app is for and what it should do, from the first pattern to the finished piece.

  2. 02

    Best practices

    Collecting counters, chart tools and pattern apps on one board to see what works.

  3. 03

    Finding the gaps

    Projects, patterns and yarn live in separate tools, so crafters keep switching.

  4. 04

    Four pillars

    Turning the findings into four focus areas for the app.

Best practices

What existing craft apps do well

Counter apps make tapping fast and visible, and chart makers show patterns as clear grids. But most of them do only one thing, so crafters still jump between several tools.

Moodboard of existing craft apps: row counter apps, stitch chart makers, a smartwatch counter and pattern library screens

Key insight

Crafters don't need another social feed. They need one place that remembers exactly where they are.

Define

From scattered notes to one companion

The research pointed to one core problem and four areas the app has to cover. Everything else, including sharing, stays deliberately light.

Problem

Crafters juggle paper notes, bookmarked PDFs and memory to know where they are in a project.

Patterns, progress and materials live in different places, so every session starts with finding your place again.

Rebrief

“How might we help crafters go from a pattern to a finished project in one app, tracking every row, stitch and colour change along the way?”

The four pillars

Four pillars, one for each part of a project

01

Project tracking

The heart of the app: a tap counter for rows, tiles and rounds, colour-change alerts, notes and photos.

02

Pattern management

A personal library: import PDFs, paste URLs (e.g. Ravelry) or write patterns from scratch.

03

Material planning

Scoped to the project: the app tells you how much yarn this piece needs. No stash management.

04

Light sharing

Export a project or pattern as a link or image. No social feed, just simple sharing.

Develop

Structure first, then a system

I mapped the sitemap and the main user flows before drawing screens, then built a design system with Figma variables and design tokens so every screen could be assembled from the same parts, in light and dark mode.

Information architecture

Home, Projects and Patterns sit in the bottom navigation. Each one opens into its own detail screens, and a new project can start from Home or straight from a saved pattern.

  • Home / dashboard
  • New projectbasics & materials
  • Import or create patternpreview, materials, sizes
  • Project createdsummary, then back to Projects
  • Projects
  • Project detailprogress at a glance
  • Log progressrows, notes, photos
  • Summary & donetoday's progress, archive
  • Patterns
  • Pattern detailmaterials, sizes, stitch chart
  • Start project from pattern

User flows

Two flows that carry the app

Starting a project is broken into short, focused steps. Daily tracking is built for speed: resume from Home, log rows, save, and come back tomorrow.

Start new project

  1. Home
  2. New project
  3. Craft type
  4. Materials
  5. Schedule
  6. Notes & summary
  7. Project created

Daily tracking

  1. Home
  2. Resume project
  3. Log rows & colours
  4. Save for today
  5. Summary
  6. Mark as done
  7. Archive

Design system

One system, light and dark

Colours, type, spacing, roundings and icons are set up as variables and tokens. Pink carries actions, orange marks what is in progress, and the neutrals switch between the light and dark themes.

Colour

  • Primary · pink
  • Primary · orange
  • Neutral
  • Success
  • Danger

Typography

Aa Kalnia

Headings · title font token (text/font-family/title)

Aa Inter

Body · body font token (text/font-family/body)

Variables & tokens

I set up 128 variables in four collections. Primitive tokens hold the raw values. Semantic tokens give them a job, like text/primary or action/primary, and they have modes: Light and Dark for colour, Mobile and Desktop for type. Components only use semantic tokens, so switching a mode restyles every screen.

Primitive (global)

68 raw values

1 mode

Colour ramps: pink, yellow, neutral, green, red
Spacing 2–32 px
Rounding 2–24 px
Font family, weight, size, line height

Semantic colours (alias)

31 colour roles

LightDark

Background, Surface, Text, Border, Status, Action, State, Shadow

Semantic typography

28 type tokens

MobileDesktop

H1–H3, Lead, Base, Small, Caption: family, weight, size, line height

Components

Bound to semantic tokens

Buttons with active, pressed and inactive states, project cards, row counter, inputs, bottom navigation

Screens

Switch by mode

Set a frame to Light or Dark (or Mobile or Desktop) and every token resolves to its new value.

EXAMPLE color/pink/500 #FF4FB3 Color/action/primary “Start new project” button

In Dark mode the same role points to color/pink/300.

Semantic colours

Each colour role has a Light and a Dark value that points back to a primitive. This is what lets the app switch between light and dark mode without a second set of screens.

Semantic tokenLight modeDark mode
Color/Background/defaultcolor/neutral/0color/neutral/1000
Color/Surface/defaultcolor/neutral/100color/neutral/800
Color/text/primarycolor/neutral/900color/neutral/0
Color/text/primary 2color/pink/600color/pink/100
Color/text/secondarycolor/neutral/600color/neutral/200
Color/border/defaultcolor/neutral/200color/neutral/700
Color/action/primarycolor/pink/500color/pink/300
Color/action/secondarycolor/yellow/300color/yellow/600
Color/status/successcolor/green/500color/green/300
Color/status/errorcolor/red/500color/red/300

Scales

Spacing, rounding and type, all as tokens

Spacing and corner radius come from fixed number scales, and the text styles read their size and line height from the Semantic Typography collection, which has a Mobile and a Desktop mode.

Spacing

  • spacing/502 px
  • spacing/1004 px
  • spacing/2008 px
  • spacing/25012 px
  • spacing/30016 px
  • spacing/40024 px
  • spacing/50032 px

Rounding

  • 100 · 2px
  • 200 · 4px
  • 300 · 8px
  • 400 · 16px
  • 500 · 24px

Typography modes

TOKENMOBILEDESKTOP
H1 · Kalnia Bold32 / 4040 / 48
H2 · Kalnia Bold24 / 3232 / 40
H3 · Kalnia20 / 2824 / 32
Lead · Inter Medium18 / 2824 / 32
Base · Inter Medium16 / 2416 / 24
Small · Inter Medium14 / 2014 / 20
Caption · Inter Medium12 / 1612 / 16

Prototype logic

A variable that really counts rows

A separate Conditions collection holds one number variable, currentRow. The + and − buttons of the row counter use Set variable actions, and the counter text is bound to the variable, so in the prototype the number actually goes up and down.

On tap  +  →  set currentRow = currentRow + 1
On tap  −  →  set currentRow = currentRow − 1
Row counter component: 6 of 15 rows, with minus and plus buttons and a 45% progress bar

Components

Every component is a variant set with its states built in: active, pressed and disabled buttons; late, in-progress and done projects; default and chosen options. Their colours come from semantic tokens, so the same components work in light and dark mode.

Buttons: primary and secondary “Start new project” buttons, each in active, pressed and disabled states Pattern source picker in default and chosen states: From Library, Paste URL, Upload PDF and Write Manually Pattern queue item in late, in-progress and done states Project card in active and inactive states, and the yarn option with an Add yarn button Bottom navigation in light mode, with the Home, Projects and Patterns tab each active Bottom navigation in dark mode, with the Home, Projects and Patterns tab each active

Deliver

A calm companion for busy hands

The final screens put the current project first and keep every action one tap away, so crafters can put the phone down mid-row and pick up exactly where they stopped.

Main screens

Dashboard, Projects, Patterns

The three tabs of the bottom navigation. Each opens on what matters most: today’s task, projects grouped by status, and a searchable pattern library.

Dashboard
Dashboard: the main daily task, Persian tiles blanket, and the pattern queue
Projects
My Projects: projects grouped as in progress, overdue and planned
Patterns
My Patterns: a searchable grid of saved crochet and knitting patterns

Home dashboard

Today’s task comes first

The home screen opens on the main daily task: the project in progress, how far along it is and the next colour change. Below it, the pattern queue shows what is next, with late, in-progress and finished projects marked by colour.

Top of the home dashboard: greeting, main daily task card and the pattern queue

Bottom navigation

Three tabs, always within reach

Home, Projects and Patterns stay at the bottom of every screen, and the pink “Start new project” button floats above the list, so the main action is always under the thumb.

Bottom of the home dashboard: the pattern queue, the floating Start new project button and the bottom navigation

Start new project flow

Six short steps instead of one long form

Name the project and choose a pattern source, pick the craft type, add hook size and yarn, set an optional deadline and notes, then check the summary before the project is created.

  1. 1 · Name & pattern sourceNew project: project name and pattern source options
  2. 2 · Craft typeCraft type: crochet or knitting
  3. 3 · Hook & materialsMaterials: hook size and a yarn form with brand, weight, colour and amount
  4. 4 · Yarn addedMaterials with a yarn added: Crimson snow pink, light, 2 balls
  5. 5 · ScheduleSchedule: an optional project deadline
  6. 6 · Notes & summaryProject notes and the project summary with a Create project button

Light & dark mode

One design, switched by variables

Light and dark mode were built with variables and tokens, so the app can switch between them. Every colour is a semantic token with a Light and a Dark value: both sides below are the same frames, only the variable mode is different.

MODE · LIGHT
Dashboard in light mode Project detail in light mode
MODE · DARK
The same dashboard in dark mode The same project detail in dark mode

Reflection

What I learned

  • A design system pays off fast: once colours, type and components were variables, the dark theme took a fraction of the time.
  • Breaking a long setup into short steps makes it feel lighter, even when it asks for the same information.
  • Crafting is full of interruptions, so the app has to show people exactly where they stopped, instantly.

This is an ongoing project

Stitch Please! started last semester and I keep working on it as a hobby project. The next step is testing the prototype with crafters, then iterating on the design based on what I learn.

Stitch Please!