{"id":3267,"date":"2020-02-06T10:24:07","date_gmt":"2020-02-06T09:24:07","guid":{"rendered":"https:\/\/www.codemotion.com\/magazine\/?p=3267"},"modified":"2020-03-05T11:39:21","modified_gmt":"2020-03-05T10:39:21","slug":"design-tokens-and-cross-platform-coherence","status":"publish","type":"post","link":"https:\/\/www.codemotion.com\/magazine\/frontend\/design-ux\/design-tokens-and-cross-platform-coherence\/","title":{"rendered":"Design Tokens and Cross Platform Coherence – Part 1"},"content":{"rendered":"\n

\nYou did it! You have exceeded one million users<\/span> and your team<\/span> has grown. Now there are enough teammates to directly and dedicatedly pursue the development of the web platform, smartphone and tablet apps, and smart TV apps, but also to reorganise the workflows to proceed independently for individual features.<\/p>\n\n\n\n

When teams<\/span> grow<\/strong>, it is not uncommon for single units to take small steps independently. Over the long haul, those steps might end up invalidating the initial cohesion. Developers know how easy it is to yield to the temptation of copy-and-paste from one codebase to another just to discover, months later, that the original code has changed and it wasn’t updated in any occurrences. Like single pieces of code, the style elements that contribute to defining brand identity end up fraying<\/strong>.<\/p>\n\n\n\n

The digital<\/span> world has contributed to multiplying possible touchpoints with users<\/span> and customers, without offering the chance of managing the basic elements of the style in a unified way for all those touchpoints. For example, just think about the diverse ways in which the three main digital<\/span> “platforms” (web, iOS, and Android<\/span>) allow you to define the same colour:<\/p>\n\n\n\n