Short spoken monologue arguing that design systems should be tailored to a company’s specific products, priorities, and customers rather than be generic libraries. The speaker (Dan Mall) references his post “Distinct Design Systems” and contrasts bespoke systems with Material/Bootstrap, noting inclusion of components (e.g., voice or hardware) only when relevant to the company.
I mean, if you think about a design system for, say, Google, would a design system include voice components or include, like, physical hardware components? Sure. But if your company doesn't do physical hardware, then your design system doesn't need to have any physical components. Eventually, when it does, or when you do, then you can include some of that stuff. So. Absolutely. I think that the company that you work for, I wrote a post about this called Distinct Design Systems, where, like, I think that a design system should be for a specific company, like, for a specific purpose. Otherwise, we might as well all just use material. Like, if material is amazing, bootstrap is amazing, we might as well use all of those things. But, like, different companies have different priorities, different customers, different needs. And I think that the design system should reflect that.
