Designing a scalable design system and monetization experience for 30,000+ monthly active users, resulting in an 18% lift in click-through rate and 12% improvement in creator retention.
Creator profile and monetization tool redesign driving measurable engagement lift.
Improved creator experience keeping more content producers on the platform longer.
Design system supporting rapid feature launches at scale across 3 platforms.
Full component library and token architecture built from scratch in under 6 months.
When I joined Nowbase, Bamboo was a fast-growing creator monetization platform serving 30,000+ monthly active users — but it had no design system. Every feature was built in isolation. Components were duplicated or inconsistent across platforms. Engineers spent hours reconciling divergent specs. The product felt fragmented, and it showed in the numbers.
My mandate was twofold: build a robust design system that could scale across web, iOS, and Android — and use it to redesign the creator profile and monetization tools that were underperforming against key retention and revenue metrics.
"Every feature was built in isolation. The product felt fragmented — and it showed in the numbers."
I started with a full audit. I reviewed every screen across web and mobile, catalogued inconsistencies, and mapped the user journeys for both creators and consumers. Then I ran structured interviews with 12 creators across different content categories to understand their workflows and frustrations.
In parallel, I partnered with the data team to analyze funnel drop-off and engagement patterns using Amplitude and Fullstory. The data told a clear story: creators were abandoning their profile setup mid-flow, and monetization features were being ignored entirely — not because they didn't want to earn, but because the surface was confusing and low-trust.
68% of new creators never completed their profile. Exit points clustered around the bio and media upload steps — both technically error-prone and visually uninspiring.
Creators skipped monetization tools not from disinterest, but because the UI signaled low legitimacy. Inconsistent styling made paid features look "beta" or experimental.
Creators switching between web and mobile encountered different component behaviors and layout patterns for the same features — eroding trust and familiarity.
Developer interviews revealed that 40% of sprint time on front-end features was spent reconciling design specs — a direct symptom of no shared system.
Rather than jumping to UI solutions, I proposed a system-first approach: establish the design system foundation, then use it to redesign the creator experience. This would take longer upfront but would pay compounding dividends on every future feature.
I worked in close collaboration with engineering to ensure the system was implementable — not just beautiful in Figma. Every token, every component was validated against what Storybook could actually render on both platforms.
Defined color, typography, spacing, and motion tokens in Figma variables — mapped 1:1 to CSS custom properties and React Native theme values.
Built 60+ components from atoms to organisms in Figma. Each documented with usage guidelines, do/don'ts, and accessibility annotations.
Rebuilt creator profiles, onboarding flows, and monetization tools using only system components — proving system validity under real conditions.
The design system I built for Bamboo centered on three principles: tokens first (everything derives from a single source of truth), platform-native (components felt at home on iOS and Android, not just ported from web), and documented to ship (every component had usage specs ready for Storybook).
For the creator profile redesign, I focused on establishing trust and momentum. The new profile setup flow reduced steps by 40% and introduced contextual guidance that helped creators understand what made a compelling profile. The monetization surfaces got a full visual refresh — high-density layouts replaced by clear, tier-based structures that communicated value and legitimacy.
Building a great token architecture is only half the work. I spent significant time running workshops and pairing sessions to help engineers understand why tokens mattered — and that investment paid back tenfold in consistency.
The most impactful decisions came from triangulating Amplitude funnels with qualitative creator interviews. Neither alone would have surfaced the monetization trust issue — I needed both lenses simultaneously.
The system only delivered long-term value once I treated it as a living product with a roadmap, release notes, and regular stakeholder reviews — not a one-time deliverable to hand off and move on from.