Pepsico Partner
Role: Product Designer
Project Type: B2B Consumer, Responsive, Native Mobile
Design System: PepsiCo Partner Design System
About the Project
As part of a five-designer team at PepsiCo, I owned the product browsing and purchasing experience for a B2B ordering and rewards application used by small business owners (bodegas and grocery stores) internationally. The application was built as a native mobile app for iOS and Android alongside a responsive web experience using a shared codebase. Working within an established, collaborative design system, I contributed components and patterns that needed to flex across platforms, languages, and varying levels of functionality based on regional requirements.
Designing for Multi-Platform Consistency and Adaptation
The application followed a mobile-first approach, with designs that maintained consistency across iOS and Android while adapting meaningfully for desktop environments. Product browsing patterns leveraged additional screen real estate on desktop through adjusted navigation and layout structures, while maintaining the core interaction model across devices. All component work needed to function seamlessly across both mobile and web implementations, requiring close attention to how design tokens, spacing, and interactions translated through the shared codebase to ensure a cohesive experience regardless of platform.
Navigating Globalization and Cross-Team System Contributions
One of the most complex challenges was designing for international markets with significant variance in both language (accommodating longer German translations, for example) and functionality availability - South American markets had the full suite of features including online ordering and rewards, while other regions had limited capabilities. This required maintaining flexible component specifications that could handle different feature sets and content lengths across countries. Working on a shared design system with five designers simultaneously meant constant communication and alignment; we held weekly check-ins to review component changes and assess cross-application impact, ensuring updates like new discount indicators or promotional tags would work across all team members' sections of the app.
Personal Reflection
This project reinforced that design systems are as much about people and process as they are about components. Managing a living, evolving system across a multi-designer team required clear communication protocols and a shared understanding that the system would need frequent extensions. Working within these constraints while designing for multiple markets taught me to build flexibility into components from the start and to consider the ripple effects of any design decision across platforms, languages, and team members' work.
Pepsico Partner
Role: Product Designer
Project Type: B2B Consumer, Responsive, Native Mobile
Design System: PepsiCo Partner Design System
About the Project
As part of a five-designer team at PepsiCo, I owned the product browsing and purchasing experience for a B2B ordering and rewards application used by small business owners (bodegas and grocery stores) internationally. The application was built as a native mobile app for iOS and Android alongside a responsive web experience using a shared codebase. Working within an established, collaborative design system, I contributed components and patterns that needed to flex across platforms, languages, and varying levels of functionality based on regional requirements.
Designing for Multi-Platform Consistency and Adaptation
The application followed a mobile-first approach, with designs that maintained consistency across iOS and Android while adapting meaningfully for desktop environments. Product browsing patterns leveraged additional screen real estate on desktop through adjusted navigation and layout structures, while maintaining the core interaction model across devices. All component work needed to function seamlessly across both mobile and web implementations, requiring close attention to how design tokens, spacing, and interactions translated through the shared codebase to ensure a cohesive experience regardless of platform.
Navigating Globalization and Cross-Team System Contributions
One of the most complex challenges was designing for international markets with significant variance in both language (accommodating longer German translations, for example) and functionality availability - South American markets had the full suite of features including online ordering and rewards, while other regions had limited capabilities. This required maintaining flexible component specifications that could handle different feature sets and content lengths across countries. Working on a shared design system with five designers simultaneously meant constant communication and alignment; we held weekly check-ins to review component changes and assess cross-application impact, ensuring updates like new discount indicators or promotional tags would work across all team members' sections of the app.
Personal Reflection
This project reinforced that design systems are as much about people and process as they are about components. Managing a living, evolving system across a multi-designer team required clear communication protocols and a shared understanding that the system would need frequent extensions. Working within these constraints while designing for multiple markets taught me to build flexibility into components from the start and to consider the ripple effects of any design decision across platforms, languages, and team members' work.
Pepsico Partner
Role: Product Designer
Project Type: B2B Consumer, Responsive, Native Mobile
Design System: PepsiCo Partner Design System
About the Project
As part of a five-designer team at PepsiCo, I owned the product browsing and purchasing experience for a B2B ordering and rewards application used by small business owners (bodegas and grocery stores) internationally. The application was built as a native mobile app for iOS and Android alongside a responsive web experience using a shared codebase. Working within an established, collaborative design system, I contributed components and patterns that needed to flex across platforms, languages, and varying levels of functionality based on regional requirements.
Designing for Multi-Platform Consistency and Adaptation
The application followed a mobile-first approach, with designs that maintained consistency across iOS and Android while adapting meaningfully for desktop environments. Product browsing patterns leveraged additional screen real estate on desktop through adjusted navigation and layout structures, while maintaining the core interaction model across devices. All component work needed to function seamlessly across both mobile and web implementations, requiring close attention to how design tokens, spacing, and interactions translated through the shared codebase to ensure a cohesive experience regardless of platform.
Navigating Globalization and Cross-Team System Contributions
One of the most complex challenges was designing for international markets with significant variance in both language (accommodating longer German translations, for example) and functionality availability - South American markets had the full suite of features including online ordering and rewards, while other regions had limited capabilities. This required maintaining flexible component specifications that could handle different feature sets and content lengths across countries. Working on a shared design system with five designers simultaneously meant constant communication and alignment; we held weekly check-ins to review component changes and assess cross-application impact, ensuring updates like new discount indicators or promotional tags would work across all team members' sections of the app.
Personal Reflection
This project reinforced that design systems are as much about people and process as they are about components. Managing a living, evolving system across a multi-designer team required clear communication protocols and a shared understanding that the system would need frequent extensions. Working within these constraints while designing for multiple markets taught me to build flexibility into components from the start and to consider the ripple effects of any design decision across platforms, languages, and team members' work.