Overview
My role
Product designer, Design systems
Timeline
~2 months
Deliverables
Figma component, documentation
Summary
I collaborated with engineers to implement the refactored page controls to meet accessibility standards, best practices, and improve component architecture to reduce improper usage.
Method
I followed the component creation and lifecycle process, established by the design systems team, to ensure a high bar of quality is maintained throughout my project.
Competitive research
I conducted an external audit of page control best practices from 4 design systems.
I reviewed the internal usage and support requests of page controls in the past 3 months.
Rides
Eats
Uber for Business
External
External
Internal
Internal
Explore & Feedback
Accessibility
Education
Build the page controls component to increase discoverability of the ascending and descending navigation behaviors.
Bridge the gap
Iteration & Feedback
Bloated component
Justify the value of having a 162 variant Figma component for 5 dots.
Accessible within context
Identify the different layouts and surrounding context to ensure page control accessibility.
Design feasibility
Re-evaluate pressed state in web vs. mobile in light of technical constraints.
ENG
Justify the value of having a 162 variant Figma component for 5 dots.
API layout to ensure functionality
Identify the different layouts and surrounding context to ensure page control accessibility.
Prototypes to demonstrate design navigation intention
Re-evaluate pressed state in web vs. mobile in light of technical constraints.
The results
Figma component
Prepare assets and component variants for the Base Figma component library publish and changes to the new component for design engineers to implement into the Base Figma plugin.
Documentation
Publish guidelines on usage, best practices, specs, grid layouts, and more to include in Base documentation to give a holistic understanding of the redesigned component.
Web component