The Challenge
The sitter profile page is a crucial touchpoint for pet owners selecting a caregiver. Despite its importance in the customer journey, we faced significant obstacles:
Outdated code that prevented new feature development
Inconsistent designs across iOS and Android platforms
Need for integration with our emerging design system (KDS)
My Role
As the lead designer, I was responsible for:
Creating a unified cross-platform design
Identifying necessary component needs
Designing missing elements
Building Figma components for our design system
Before (ios/android), After (unified design)
Approach
To prevent scope creep, we established key guardrails: maintain interaction patterns and component parity with legacy pages, while allowing for visual updates to match our new design system.
Existing screens
Component blueprints
I created blueprints documenting every component and pattern across both platforms. The goal was to merge these into a solution that felt natural across all devices—neither iOS nor Android dominant.
Component blueprints
Building Block Strategy
The implementation plan organized components into three categories:
Atoms: Core UI elements built by the KDS team
Molecules: Combined elements also handled by KDS
Organisms: Complex, page-specific components built by our feature team
I created the first draft of the component proposal to kick-off the team discussion. The page needed atoms, molecules and organisms, the first 2 being built by the KDS team, the 3rd group being built by my feature team.
atoms, molecules, organisms
Design explorations & asset creation
I developed initial component proposals to kickstart team discussions, created design explorations to ensure the profile metadata section could expand for future needs, and designed new icons in our Kibble style.
Created new icons needed in kibble style
See it live on the Rover app
Future phases
While meeting immediate needs, I also explored enhancement opportunities like displaying preferred pronouns and extending mobile patterns to our web experience.
This approach delivered a cohesive design solution that resolved technical constraints while establishing a foundation for future improvements to this business-critical feature.
Exploring future opportunities, like expressing preferred pronouns, and extending the native pattern to web