
At a glance
ROLE
Senior UX designer
COLLABORATORS
Marketing manager, design manager, and engineering manager
Focus
Component architecture, Figma variables, nested components, component performance, design-to-code collaboration
outcome
A widely adopted multipurpose card system that replaced most existing card patterns across Qualcomm's marketing website.
SUMMARY
I developed a scalable, multipurpose card system for Qualcomm's marketing website, consolidating existing patterns into a consistent, reusable architecture. By leveraging nested components, design variables, and thoughtful property configurations, I balanced flexibility with usability while improving Figma performance. The system was implemented in production and became widely adopted, replacing most existing card patterns across the website.

The challenge

Building the foundation

Component architecture
Shared foundations
Designing a hierarchy of customization
A key architectural decision was determining which properties should be exposed at the top level and which should remain within nested components.
Frequently used controls were made accessible directly from the parent component. More specialized options remained available through nested components.
For example, asset configurations were predefined according to the selected offering, but designers could access the nested asset component to replace an icon with an image or customize related tags.
This provided flexibility without requiring every possible option to appear in the main properties panel.
Optimizing for performance

As the number of supported configurations grew, the original component structure became increasingly slow to work with. Switching between configurations could take several minutes.
I evaluated the balance between variants and nested components and decided to separate the card families into focused component sets rather than maintain one oversized component.
The change noticeably improved Figma performance and made the system easier for designers to navigate.
The team responded positively to the revised architecture.
This reinforced an important principle: a component's scalability depends not only on what it supports, but also on how efficiently designers can use it.
Design-to-code collaboration

Governance and adoption
I tested the component configurations extensively, paying particular attention to similar variants with subtle differences in content and layout.
I organized properties and layers to make the components easier to understand and configure.
When incorporating an existing List component into the Multi Content family, I aligned with the marketing manager before changing the established structure.
After sharing the components with the design team, I gathered feedback and refined the architecture.
Multi Content became widely used and replaced most existing card patterns across Qualcomm's marketing website.

The Takeaway
The biggest lesson was learning when to reuse, when to nest, and when to separate components. By balancing configuration flexibility, Figma performance, and maintainability, I created a system that supported diverse content requirements while remaining practical for designers to use.

