Most design systems start as a collection of buttons, inputs, tokens, and reusable patterns, but teams quickly discover that components alone do not solve the real friction between design and engineering. Figma drifts from code, documentation gets outdated, ownership becomes unclear, and the system slowly turns into either a bottleneck or a forgotten asset.

This roundtable brings together React Native developers, designers, and product-minded engineers to talk about what makes a design system sustainable in practice: governance, contribution models, release processes, quality checks, and the day-to-day habits that keep adoption easy. The goal is to compare what has worked, what has failed, and what makes a design system feel like product infrastructure instead of just a shared UI kit.