All projects
Design Systems Product Design Wellness Component Library

Nature Counter

Building a unified design language for a growing wellness platform — enabling a small team to ship consistent, accessible experiences at scale.

Role Lead Product Designer
Timeline 2024 — Present
Platform iOS, Android, Web
Users 100,000+
Nature Counter MVP OT showreel overview

Outcomes

30% fewer inconsistencies · 45% faster handoff · 100K+ users on a unified system

30% reduction in UI inconsistencies across all platforms
45% faster design-to-dev handoff after system launch
100K+ users on the platform benefiting from consistent UX
100% WCAG AA compliance on all new components
01
Overview

One source of truth for a platform that grew faster than its design

Created the core design system for NatureCounter, a wellness app promoting outdoor journaling. The challenge was building a scalable token-based system that non-design-system-savvy engineers could implement without friction — while maintaining visual richness across 40+ component types.

I led the design system initiative from scratch — establishing foundations, building a component library in Figma and code, and creating documentation that made adoption easy for engineers with zero design background.

Industry

Wellness · Outdoor Journaling

Timeline

2024 — Present

Platform

iOS · Android · Web

Components Built

40+ production-ready

Skills

Design Systems · Tokens · Figma Variables · Accessibility · Documentation

Users

100,000+

02
Problem

A product that outgrew its design — three platforms, zero consistency

Nature Counter had been designed piecemeal by different contractors over 18 months. Each surface — the iOS app, the Android app, and the web dashboard — had diverged in color, spacing, typography, and interaction patterns.

Engineers were spending significant time debating implementation details that should have been pre-decided. Each new feature required redundant design work because there was no reusable foundation to build from.

  • 6 different button variants with no shared base style
  • No design token layer — hex values hardcoded across 200+ Figma frames
  • Accessibility failures on color contrast across 30% of UI elements
  • Design and dev using different names for the same components
  • New features took 2× longer to design due to from-scratch work

"Every time we shipped a new screen, I'd catch three things that didn't match the rest of the app. It was death by a thousand cuts."

— Engineering lead, internal retro session
03
Process

Audit, architect, then build — in that order

Design systems fail when they're built in isolation. I started with a cross-functional audit — involving both engineers and the product manager — to ensure the system would actually be used, not just admired.

01
Audit
Catalogued 200+ existing UI elements across all platforms. Identified 6 button types, 4 type scales, 12 color inconsistencies, and 8 spacing increments.
02
Foundations
Defined token layer: color primitives → semantic tokens → component tokens. Unified type scale, spacing system (4px base), and motion curve library.
03
Components
Built 40+ production-ready components in Figma with auto-layout. Paired with engineering to define the code API for each component.
04
Documentation
Wrote usage guidelines, accessibility notes, and do/don't examples for every component. Made it a reference tool, not just a spec doc.
04
Solution

A living system — tokens, components, and documentation as one

The Nature Counter Design System launched with a token-first architecture. Every color, space, radius, and motion value is a named token that maps from primitive → semantic → component. This means theme changes (like dark mode) require updating one layer, not hundreds of individual values.

Nature Counter component library and token architecture
05
Results

Faster, more consistent, accessible by default

Three months after full rollout, measurable improvements across every tracked metric. The 45% handoff speed improvement translated directly to shipping velocity — the team went from 2-week feature cycles to under 10 days for medium-complexity features.

30%
Fewer UI Inconsistencies
UI inconsistencies flagged in QA dropped by 30% within the first three months of full rollout.
45%
Faster Handoff
Design-to-dev handoff time cut nearly in half. Medium-complexity features went from 2-week cycles to under 10 days.
100%
WCAG AA Compliance
All new components launched with full WCAG AA accessibility compliance — accessibility is built in, not bolted on.

"Now when someone asks 'what does a modal look like in this app?' — there's one answer. That alone cut our review cycles in half."

— Product Manager, Nature Counter
06
Assets

Nature Counter visual asset showcase

All available files from the Nature Counter image folder are surfaced below for quick review and reference in one place.

Nature Counter hero composition — full design system overview

Design System Overview

Nature Counter component library — primary UI components

Component Library

Nature Counter design tokens — color, type, and spacing system

Design Tokens

Nature Counter interaction patterns — states and transitions

Interaction Patterns

Nature Counter mobile component — compact layout variant

Mobile Component

Nature Counter design system detail — iconography grid

Iconography

Nature Counter design system detail — spacing and rhythm

Spacing & Rhythm

07
Reflection

Design systems are as much about documentation as design

01
Constraints create coherence
The best design systems aren't the most flexible — they're the most opinionated. Clear constraints on spacing, color usage, and type scales reduced decision fatigue for the whole team.
02
Documentation is the real deliverable
A component library without clear naming conventions and usage guidance is just a Figma file. The 45% handoff reduction came from documentation quality, not component count.
03
Systems thinking over visual craft
Design system work demands thinking about relationships between components, not just how individual elements look. The mental shift from "designing screens" to "designing systems" was the hardest part.
04
Build with engineers, not for them
Co-authoring the component API with engineers meant zero back-and-forth during implementation. What design names ButtonPrimary, code names ButtonPrimary — simple, but transformative.

Conclusion

Nature Counter taught me that design systems are the most leveraged design work you can do — every hour invested in the system pays back across every future feature, every future engineer, every future sprint.

The 100K users on the platform never see the design system. They just experience a product that always feels coherent. That invisibility is the whole point.

Glad we could cross paths.
Out of anywhere you could be, you're here.

Next project

Saarthi
All projects