Case study · “Figma to Deploy” workshop by Lucas Marte · In progress
Gooday: from a 28/100 audit to a design system that ships
My wellness social app looked consistent, but an audit scored it 28/100. I turned it into a documented design system and a responsive app with 0 accessibility violations.
Role
Sole designer of the identity, UI and product decisions
Timeline
Since September 2026, a personal project
Tools
Figma, Affinity, Notion, and Claude for the build
Deliverables
Design system, docs and a responsive web app
409 → 0
hard-coded colors, replaced by semantic tokens
31
component sets with full states
0
axe accessibility violations in the coded app
The idea
A social network for healthy living, without the perfect-profile filter.
Fitness apps feel like dashboards or highlight reels. Gooday is a real social network with a calm, human wellness identity.
People meet in communities like running, yoga and cycling. The tagline: “we move together.”

The audit
A strong visual language that wasn’t a system yet.
Before building, I audited my own screens: 28/100, with 0 variables, styles or components and 409 hard-coded fills.
Copies had already drifted: the same Follow button existed at three different widths.
Accessibility flags: clipped line heights, a 32 px Follow button, 12 px tappable text and lime on white at 1.15:1.
Area
Before
After
Audit score
28/100
A documented system
Variables
0
84+
Hard-coded fills
409
0
Hand-made patterns
14, already drifting
134 copies replaced with instances
Line height
26 text layers at 50%, clipped
All fixed
Follow button
32 px, at three widths
One component, 44 px target
Tokens and components
Energetic in color, calm in structure.
A light-gray canvas, white cards, real photography and a single lime for action. Personality lives only in the wordmark and the community banners.
Variables on about 1,860 properties, 10 text styles and 31 component sets with full states.

Fix · 134 copies replaced
Hand-made duplicates became instances of the new components.
Fix · Touch targets
The Follow button grew from 32 to 44 px, and option labels from 12 to 16 px.
Fix · Line heights
All 26 clipped text layers fixed before they could break in code.
Fix · Real auto layout
Fake padding and gaps replaced, and web screens aligned to a 4-pt grid.
Documentation
Twenty pages, built from live tokens.
20 pages of documentation, built from live tokens and instances, so they update with the system.
A design.md rule book for developers and AI agents, and a Notion tracker taking each screen from spec to QA.


Design to code
Pixel-matched at 393 and 1728 px.
Built in Next.js and Tailwind, set up so only Gooday tokens compile.
Login, Home, Search, Create and media capture are built and pixel-matched to Figma.
Quality: 0 axe violations, no horizontal scroll from 320 to 1920 px, 44 px hit areas, a visible focus ring and reduced-motion support.

Results and next steps
From mockups to a working system.
Next: Profile is designed but not coded yet. Groups, Messages, Notifications, the post page and stories are still placeholders, and the app runs on mock data.
Gooday is a personal, non-commercial case study: its fonts are licensed for personal use only.
What I learned: A design that looks consistent isn’t a design system. I turned a file with no tokens or components into a documented system: semantic tokens, components with every state, and accessibility built in from the start. Taking it from Figma to code showed me that details like spacing and line heights decide whether a design survives handoff.
let’s connect!
© 2026 Isabela Telles · Goiânia, Brazil (GMT-3)







