Android 14's colors, primitives, components, and patterns were spread across a mix of files and teams in Figma rather than living in one design system. That fragmentation made it hard to know where the source of truth actually was, and the Android team's organization within Figma made things worse: the Android 14 Figma library was difficult to distribute, and cross-functional teams building for handheld, tablet, and foldable devices struggled to discover the right files for their specific feature areas within the operating system.

There was a clear opportunity to bring everything — colors, primitives, components, and patterns — under a single design system team in Figma, giving Android 14 one source of truth instead of several. There was also an opportunity to rethink how the Android team's Figma presence was organized, so the library could be distributed more effectively and cross-functional teams could actually find the files relevant to their device form factor and feature area.

I led the aggregation of colors, primitives, components, and patterns for Android 14 into a single design system team in Figma, consolidating what had been scattered across multiple files and owners. Alongside that, I restructured how the Android team was organized within Figma, which improved distribution of the Android 14 Figma library and made it easier for cross-functional teams to discover the files they needed for handheld, tablet, and foldable devices and their respective feature areas within the operating system.

With colors, primitives, components, and patterns aggregated into a single design system team, Android 14 gained one clear source of truth in Figma. The reorganized Android team structure made the Android 14 Figma library easier to distribute and gave cross-functional teams working across handheld, tablet, and foldable devices a more direct path to the files for their feature areas.