1. Naming conventions
Design tokens were already being used on adidas web. Initially, the team tried reusing the naming conventions as much as possible to have a standardized and consistent design language system across the organization. After several rounds of iteration, the naming conventions were getting too confusing due to their flexibility. Thus, the team redefined the naming conventions to give them more structure.
2. Shared components
The Confirmed app was sharing some components with the adidas flagship app. As both apps were visually styled differently, tokens came in handy - the same decision token could point to different corresponding tokens for both apps. However, this means alignment across both apps as to which decision token could or should be used while taking into consideration where else the token was potentially used.
3. Partner's Theming
The Confirmed app collaborates with various partners such as Gucci, Prada, Balenciaga, and many more. To express their brands, many of these partners have a defined theme. An additional consideration when creating these tokens was how the theming would be applied whether it was on a component level or it should be applied on a page level. All of these had further implications on the token mapping.
