| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Thanks for your interest in The Question! Sign up to participate in future questions here. This file is the raw data from Episode 007. You can check out the Episode 007 FigJam file, watch Episode 007 on YouTube, or read the Episode 007 Wrap-up Post! Major thanks to zeroheight and Sparkbox for their sponsorship of The Question this week. There are 31 answers. The question this week was: ----- I was chatting with one of our regulars (Hi, Jesse!) about some of the complexity in supporting multiple platforms with a design system. Of course, the word “platform” can mean different things to different people. Some use it to mean a JavaScript framework like React or Angular. Some use it to mean an entire content management system like Drupal or WordPress—those are platforms, right? Some use it to draw distinctions between web and native experiences like iOS, tvOS, Android, Android TV. For the sake of today’s question, I’ll offer this clarity: A “platform” supported by your design system is one for which you offer unique assets that enable the building of products constructed for/with that platform. So, if your system offers assets used by multiple teams of React devs to build multiple products — you support React as a platform. With all of this as context, here is the week’s question: How many platforms does your design system support? Which platforms do you support and how are you overcoming the challenges of doing so? | |||||||||||||||||||||||||
2 | Question 1: How many platforms does your design system support? | Question 2: Which platforms do you support and how are you overcoming the challenges of doing so? | ||||||||||||||||||||||||
3 | 3 | Win, MacOS and we have some web components as well. But we dont really overcome the challenges, we need to build these components more times, and also some of our web services are using different frameworks. In that case, only the design (UI) is included in the design system, but not the actual code components, since those are more specialized for the framwork itself. Fir desktop components we have our own framework but thats different for both platform, and honestly, its a real pain to achieve the same UI/UX with both of them.... | ||||||||||||||||||||||||
4 | 3 | Vue, Ruby, HAML. We have implementation docs and guides for each. When we do component migrations we have a guide and examples. | ||||||||||||||||||||||||
5 | 3 | React for web, native iOS and Android. Right now the only shared assets are tokens since the technologies are incompatible otherwise. We manage the tokens in Figma with Token Studio, then push directly to a mono-repo that parses them into individual JSon files for each platform and light and dark themes. They're then exported as a private NPM package for consumption. It's mainly just semantic colors that are shared, but we have plans to dive into component level tokens. | ||||||||||||||||||||||||
6 | 3 | Our products are web focused, which is why we’re using web components. The tech stack is diverse, with many versions of mostly angular and react. Which means we test everything in both and maintain a playground for each. Throw AEM in the mix and that’s fun too. What makes it manageable is having a dedicated engineering team. | ||||||||||||||||||||||||
7 | 3 | We support Angular, React and Stencil/web components. We are challenged with the need to support 6 major versions of Angular (12-17). It is quite a challenge because we support Angular via web components that use Stencil and Stencil's Angular output target package. The irony is that while web components are ideally platform agnostic, once you set up Stencil using the Angular support package you end up coupled to Angular dependencies. With 6 major versions to support, this actually quite a problem, and we're working on improving how we address it in our next major release prep. Ultimately, I believe our design system is a bit of a cautionary tale of scaling too fast. Engineering and design mandates have required adoption of our components across our organization has made our mission of delivering the best components with a focus on performance and developer experience very difficult. While any design system team would probably celebrate the level of adoption we've had in a year, it is happening faster than our little team can adequately support. | ||||||||||||||||||||||||
8 | 2 | web / mobile web we have native experiences (iOS/Android) on our road map for 24 | ||||||||||||||||||||||||
9 | 1 | React. Just doing the one is one way of avoiding the challenges. I don't feel very insightful on this topic. | ||||||||||||||||||||||||
10 | just answering off of previous experience! | In my last role, we built our system in Figma and Contentful. It was pretty straightforward given the size of the company. I'm looking forward to hearing everyone else this week! | ||||||||||||||||||||||||
11 | 3 | Android, iOS, and Web. We maintain agnostic specifications, guidance, and tokens, and build platform specific components. | ||||||||||||||||||||||||
12 | 2 | We needed to support both Web and Native (iOS). We had a team of designers and engineers dedicated to each; unfortunately the iOS team was much smaller (1 designer, 1 engineer) than web (around 5-6 of each). There was a lot of debate on the mobile side (true native vs React native, etc.). We unfortunately had a designer who didn't understand design tokens (or design systems writ large, really) name a whole bunch of design tokens prefixed with "-desktop" or "-mobile", which is redundant and makes token names needlessly verbose. Design tokens should share naming taxonomies cross platform, and values may change, but naming should remain consistent. | ||||||||||||||||||||||||
13 | 1 | To me, a platform is an application that uses a design system. For example, if a company has several applications and they are from different areas, e.g. one is e-learning platform, the other is real estate platform, etc. We had a pretty simple design system case based on React. Just one project with 5-6 teams. So, unfortunately, I have nothing interesting to share. It's clear how different devices/browsers affect design system from both a development and design perspective. I understand how development can be affected by framework (as React, Angular, etc), but I don't understand how a design team depends on a framework. Looking forward to learn it from the Q team! | ||||||||||||||||||||||||
14 | 3 | Based on previous experiences, the split was commonly desktop web, mobile native, and marketing. Overcoming the challenges? Does one every really overcome them? The problems have been largely people-based and not tech-based. Each "platform" has their own set of PMs with their own goals, often career goals. Finding common ground has been hard. What I've seen being somewhat effective is constantly finding outliers and nudging them towards either contributing that as an official pattern or showing them there's a better way. | ||||||||||||||||||||||||
15 | 1 | Right now only web but I used to support iOS Android and email previously. | ||||||||||||||||||||||||
16 | 3 | React, IOs, Android | ||||||||||||||||||||||||
17 | 1 | Just web experiences in React. From the beginning of our system it was decided that React was the way to go, because it was widely used by the product teams in the organization. However, the challenge we're facing now is that the teams that don't use React, cannot adopt the design system. This is happening both internally and especially with external partners. This is causing them to rebuilt components using our documentation, but costing so much time and money, that it's doing the opposite of what the design system is for. Abandoning React for something like webcomponents at this stage seems like too steep of a hill to climb. Especially because we have to keep maintaining the current system for our current subscribers at the same time. We're also not sure if we even need to support those teams that don't use React internally or if they would benefit from switching to React so they can adopt the system. | ||||||||||||||||||||||||
18 | 5 or more | We support 9 platforms across mobile, tablet, web, and OTT streaming | ||||||||||||||||||||||||
19 | 5 or more | Angular, React, Web Components (lit), iOS, Android (XML, Compose) We haven't exactly overcome the challenges yet! We haven't been equally staffed across the platforms we've promised to support. And, some platforms come more from contributions than the others. So, we (our design and our various code implementations) are out of sync. We're in talks of merging 2 of the existing systems in our org. One has more native offerings and the other has more web. So, while there will need to be some "harmonizing" of the 2 systems, it will put more on the shelf (and meet the platform promises made) than if one group had to start from scratch. This has taken us years to convince leadership to consider. A lot of politics/line of business issues to overcome. (and ego) We've done a lot of work on aligning releases across documentation, figma libraries, and code in the effort of being 1:1:1 on those 3 deliverables. (But, this applies to a singular framework at a time, currently.) So, we have a release cadence, a release note about what is going out in Slack, and check points to make sure we can release aligned. This has been done through spreadsheets, docs, and Jira stories/releases. | ||||||||||||||||||||||||
20 | 5 or more | Swift (iOS) Compose (Android) Web Components React Angular Many dedicated developers is the solution we’re using here. We’re up to about 10 now across all the platforms. On the Web side, the Web Components platform is not really consumed directly by teams. Instead, it is used to output React and Angular versions of components through Stencil that provide much better support for the platform it is used in. | ||||||||||||||||||||||||
21 | 1 | Within our core team, Salesforce is our main platform, but we also handle ~5 to 7 other brands within Salesforce, each needing (at times) different support. With this, we've also started dealing with transactional and marketing emails using tools in addition to Salesforce like Mailgun and our own custom internal systems. Outside our core team, and where we plan to expand, other groups use different modular technologies like Angular, React, and Vue. To expand our system to these other teams and projects at the onset, we've started with a Figma library for design components and have been having frequent collaboration sessions to ensure we understand their needs as the system grows. Since our system is still new, and a "side-project" to the larger website overhaul, most challenges continue to be addressed by our core teams. This is both an advantage and a disadvantage. It's good because they quickly spot and solve issues, but it means they're only focused on our single platform (Salesforce) updates which the majority of our external teams don't support. It is a key 2024 roadmap item to extend the system, at least in a minimal technological capacity, to other teams and platforms so I'm very excited for this week's conversation and to hear how others have addressed this challenge. | ||||||||||||||||||||||||
22 | 3 | Angular, WordPress & Dynamics CRM. Without a design system, through project management of assets. | ||||||||||||||||||||||||
23 | 5 or more | React (JavaScript), CSS, SCSS, iOS, Android, Email. Challenges were handled by using Design Tokens by Lukas Opperman to export tokens for multiple brands and customized Style Dictionary to process to multiple platforms. | ||||||||||||||||||||||||
24 | 3 | - SwiftUI - Material2 - Vue We still haven't overcome the challenges, I'd say! The fact that we use native components to ensure consistency across platforms mitigates the challenges of a multi-platform system. | ||||||||||||||||||||||||
25 | 3 | Web, app (iOS/Android, or Flutter), CRM | ||||||||||||||||||||||||
26 | 1 | We officially support React, but our design tokens are made available to other platforms via Style Dictionary. | ||||||||||||||||||||||||
27 | 3 | We support Swift, UI Kit for Native iOS applications, and React for web development. | ||||||||||||||||||||||||
28 | 1 | Current just web with responsive built in. But will need to consider how to handle native apps in the future. | ||||||||||||||||||||||||
29 | My team ships React and CSS. Others use our CSS and maintain their own platform (Vue, svelte, web-components, etc). We support over 200 products world wide, and have almost no insight to the breadth of platforms consuming our CSS. | More than I can figure out. Shipping CSS only as an option was our strategy, and has been successful. It’s a common language across the majority of platforms. The company I work for is so large and global (our target for full adoption is 500+ products maintained by thousands around the world), and our team is so small, we had to find a common denominator (CSS). We also ship React, but leave it up to other teams to build out components for other frameworks. React was chosen because of its market concentration and our pilot teams were using it. It’s interesting to see how framework popularity can be regional. For example, our European teams are 80% Vue. | ||||||||||||||||||||||||
30 | 2 | React and (soon) Angular; a challenge in pacing our work is one thing (since these are parallel code assets, but one design asset) that we have to plan around. Also, the "temporary" nature of supporting some platforms that company wants to move away from, but hasn't yet outlined a plan of how/when. | ||||||||||||||||||||||||
31 | 2 | React and Angular. We’re over coming the strenuous overhead by shifting into Web Components so we can build once, deploy into any platform. | ||||||||||||||||||||||||
32 | 5 or more | We're still in early stages of our design system work, but one big challenge we're facing is that we support a lot of monolith apps like Drupal that require full templates vs. apps like React that natively support components. Debating web components as a way to tackle this, but it's not a perfect solution as different platforms may have unique impletmentations. | ||||||||||||||||||||||||
33 | 2 | We currently build on Stencil.js and support web components, React and Angular. We cannot mandate what technology any team within the organization uses, so we have tried to create a flexible component library that can meet most teams' needs. We have struggled with some legacy technologies trying to use design systems. | ||||||||||||||||||||||||
34 | ||||||||||||||||||||||||||
35 | ||||||||||||||||||||||||||
36 | ||||||||||||||||||||||||||
37 | ||||||||||||||||||||||||||
38 | ||||||||||||||||||||||||||
39 | ||||||||||||||||||||||||||
40 | ||||||||||||||||||||||||||
41 | ||||||||||||||||||||||||||
42 | ||||||||||||||||||||||||||
43 | ||||||||||||||||||||||||||
44 | ||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||
46 | ||||||||||||||||||||||||||
47 | ||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||
52 | ||||||||||||||||||||||||||
53 | ||||||||||||||||||||||||||
54 | ||||||||||||||||||||||||||
55 | ||||||||||||||||||||||||||
56 | ||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||
59 | ||||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||
61 | ||||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||
68 | ||||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 | ||||||||||||||||||||||||||