
At a glance
ROLE
Interaction designer
COLLABORATORS
Senior interaction designer
SCOPE
Text field component architecture
SUMMARY
I designed the text field component for the Google Ads Figma design system, translating hundreds of states and configurations into a reusable component architecture for the broader Google Ads design organization.

The challenge
Google Ads was expanding its Figma design system, but one foundational component was missing: the text field. What appeared to be a relatively simple component needed to support a large number of states, configurations, content patterns, and product requirements. The challenge wasn't determining what a text field should look like. It was determining how to encode that complexity into a component designers could reliably use.

Reconciling Multiple Sources of Truth
Before defining the architecture, I needed to understand the standards the component had to satisfy. I worked across three internal systems:
Material 2 established Google's broader design system standards.
Reach UX documented Google Ads-specific patterns and requirements.
ACX represented engineering specifications and implementation guidance.
I supplemented those sources by auditing text field usage throughout Google Ads. Together, they helped answer three questions:
What should the component support?
What does engineering already support?
What does the product actually need?

Material 2 Documentation

Reach UX Documentation

ACX Documentation
Mapping the Component
Architecting the Component
I owned the component architecture and built it using the existing Google Ads foundations. That included defining:
Component hierarchy
Auto layout behavior
Nested components
States and configurations
Typography and color inheritance
Icon relationships
Connections to existing foundational libraries
The goal wasn't to create an isolated Figma asset. The component needed to inherit and behave consistently with the larger system.

Second Problem
The first architecture supported the required configurations, but it introduced another problem. It was too deeply nested.
Designers had to navigate multiple layers just to change common states and content. The component worked technically, but the experience of using it was unnecessarily complicated.
That became a second design problem: I wasn't only designing the text field. I was designing the experience of using the text field component.

Simplifying the Experience

Testing at Scale
With hundreds of possible configurations, testing was essential. I systematically tested the component to identify broken states, resizing problems, inheritance issues, and unexpected behavior before publication. This reduced the likelihood that designers would encounter problems after adopting the component.

The impact
280+ configurations supported
The architecture accommodated the breadth of text field requirements identified across Google Ads.
Reduced repetitive work
Designers could start from standardized configurations rather than repeatedly constructing and configuring text fields manually.
Standards embedded into the tool
Material, Google Ads, and engineering requirements were encoded directly into the component instead of relying on individual designers to interpret them repeatedly.
