patangTry Patang

How Patang was built

The process, the tokens the app is drawn with, and every screen with the Figma frame it comes from. For the story behind it, see the story page.

Figma and the app, side by sideEvery place the app departs from the file, with the frame, the screen and why, to keep or roll back.

Process

  1. 1

    Research

    Interviews and a design workshop on what storytelling means. The stickies on the story page are participants’ own words.

  2. 2

    Figma

    74 frames on one page (787:29) in four acts: onboarding, making it, one change, sharing with Ammi. Base truth for every screen.

  3. 3

    Clickable prototype

    The frames wired together, so the trip could be tapped through end to end.

  4. 4

    SwiftUI simulator films

    Each act rebuilt in SwiftUI and recorded in the iPhone 17 Pro Max simulator. The story page plays those takes.

  5. 5

    This web app

    Next.js on Vercel with Neon Postgres and Vercel Blob. Your choices, edits, links, reactions and notes are real rows. It installs to the Home Screen and opens offline once visited.

Colour

Inventoried from the 74 Figma frames. No study colour is mixed or faded into a new one.

Ink

#0F172A

Titles and body text

Sub

#64748B

Secondary text

One blue

#004DFF

Anything you can tap: buttons, links, the mic, selection

Patang’s voice

#FFC93C

What Patang found or fixed, sparingly

String orange

#FF9F1C

The string, and a Blend friend’s thread

Paper

#FBFAF8

The String’s ground

Type

SF Pro from the system on Apple devices; Inter elsewhere.

Display

SF Pro Bold 32 / 37 · −2.5 %

Screen titles

Your stories deserve to take flight.

Title

SF Pro Semibold 30 / 34 · −1.5 %

Onboarding and making titles

Which places matter?

Place

SF Pro Semibold 29.6 / 35.5 · −1.5 %

Places on the String

Lake Pamvotis

Body

SF Pro Regular 16 / 22

Her words, descriptions

so still. like the whole lake was holding its breath.

Label

SF Pro Semibold 11 · +9 % · caps

Kickers and place counts

Place 3 of 5

Motion

The designsystems.surf Motion Foundation: primitives, then intents that say what a move is for, then a reduced-motion override that keeps the meaning and drops the travel. Structural moves (push, sheet) are springs, so they start at rest. Source: lib/motion.ts and styles/tokens.css.

IntentDurationCurveDistanceFor
enter240 msdecelerate8 pxSomething arrives
exit160 msaccelerate8 pxSomething leaves
replace240 msstandard16 pxOne thing becomes another
feedback160 msstandard0 pxA press answers
emphasize240 msemphasized4 pxLook here
loading320 mslinear0 pxProgress, spinners
attention320 msemphasized8 pxSomeone did something
instant · 0 msfast · 160 msmoderate · 240 msslow · 320 msexpressive · 400 msspring.push · 170/26spring.sheet · 180/27spring.snappy · 520/38spring.soft · 180/26spring.pop · 600/22

Reduced motion: durations fall to 160 ms, distances to 0, springs become cross-fades, and nothing plays on its own.

Every screen

Live from the app’s route registry, by act. Each screen sits beside the Figma frame it is rebuilt from, with the Mobbin screen its structure follows where it is new.

Loading the screens…

References for these pages