
At a glance
ROLE
Main designer
COLLABORATORS
Interaction design, engineering, production, accessibility
SCOPE
10 components + variants
SUMMARY
I led the redesign and specification of a card system used throughout Apple's online purchasing experience. After discovering that designers were detaching unreliable components from the library, I restructured the system and brought design, production behavior, accessibility, and engineering specifications back into alignment.

The challenge
The Apple Online Store's existing card components had become difficult for designers to use reliably. Responsive behavior broke, available variants didn't cover real product requirements, and overrides weren't behaving as expected. Designers had developed a workaround: they were disconnecting components from the library. I treated that behavior as a signal that something was wrong with the system itself. At the same time, the components needed to support an upcoming product-page launch, giving us less than a month to resolve the issues.

Auditing
I began by comparing the existing component library against actual designer usage and the live Apple Online Store implementation.
I also worked with the original designer to understand the intended purpose, structure, and use cases behind the cards.
This helped distinguish necessary product complexity from problems introduced by the component architecture.

Restructuring
I had final decision-making authority over the component structure. Based on the audit, I restructured the system to address:
Broken responsive behavior
Missing variants
Problematic overrides
Component usability
Design-file complexity
Across 10 related components and their variants, I created a structure that more accurately represented how the cards needed to behave across the purchasing experience.

Design-to-Code
Fixing the design library was only part of the work. Engineering needed an accurate specification for implementing the same behavior in production. I documented:
Component anatomy
Measurements and spacing
Responsive behavior
Breakpoints
Typography
Interaction states
Animation and transitions
Accessibility requirements
User behavior
I worked directly with engineers to refine the specifications based on implementation constraints. These specifications were then used to update the production components.

Accessibility
I collaborated with accessibility experts to ensure accessibility requirements were represented directly within the component specifications.
Rather than treating accessibility as final QA, it became part of defining how the component should behave alongside interaction and responsive requirements.
Product Timeline
The component work was tied to a new product-page experience, so system improvements couldn't happen independently from product delivery.
I coordinated across interaction design, engineering, accessibility, and production while balancing system quality with implementation feasibility and the launch timeline.
The updated components and implementation specifications were completed in less than one month.
The impact
Restored component usability
Restructured the system after identifying component detachment as a symptom of architectural problems.
Improved responsive reliability
Addressed responsive behavior, missing variants, and override issues that had been creating friction for designers.
Reconnected design and production
Created detailed specifications that engineers used to update the production implementation.
Embedded accessibility
Accessibility requirements became part of the component definition rather than a downstream consideration.
Supported product launch
Updated and documented 10 related components and their variants in less than one month for the new product-page experience.
