Venice Interface Guidelines (VIG), is the design language for the PayPal Consumer Mobile App. It is a project I co-created with my colleagues Chris Sybico and Libo Su. The mobile app, Venice, is a particularly customized app in its design. It has its own PayPal typeface, its own gradients and colors, its own iconography, motion, etc. Designing for Venice was at times an inconsistent process. There was multiple duplication of assets; reusable components, framework and patterns were not being shared across the design organization; and time spent with developers was inefficient. To solve this, we decided to document every element within the app and create a centralized repo where building blocks for Venice would live. Our hope was to create reusable components and reusable code that could be shared between different teams and make conversation with developers more efficient.
The VIG initiative started from a simple problem that almost every designer has gone through: exporting assets.
During my very first project as a Product Designer at PayPal, I was asked to export assets. With that request arose a few questions: how and where to export them, what to name them, and determine what assets are already in the app.
I got answers to some of my questions, but not all. I suggested to my team that we should have one folder in our cloud system that would contain all the assets for the app. They would have meaningful names to avoid duplications and be available for all designers and developers to use. In the process of documenting all the assets and making them shareable, we realized that there was so much more than just assets that needed to be shared throughout the organization. There were styles, components, patterns, frameworks and animations that needed to be documented and made available to use in order to make the product more consistent and thus more intuitive and enjoyable.