3 ms·
Are there changes to the web that you think would lift that burden, or make design systems less necessary? Two major drivers come to mind in terms of DS adopti
by RickS 7y ago
Are there changes to the web that you think would lift that burden, or make design systems less necessary?
Two major drivers come to mind in terms of DS adoption:
1) Giving teams a common toolkit of resources so that they can design consistent experiences without having to independently implement and maintain the same components.
2) It's really trendy. It's the designer equivalent of moving to serverless, or nosql years ago, etc etc. Small teams do it because it's cool and fun despite not necessarily feeling the enterprise-scale pains that originated some of the practices.
(I would not put flexport in that category. They've got an extremely data-intensive software, and a good component lib helps a lot there)
- akrymski 7y agoSure, the HTML standard needs to go - it was designed for hyperlinked documents, not software. Components should be provided by browser/OS vendors with a standard look and feel, the same way desktop software has been written for decades. React Native is a glimpse of what HTML of the future will look like. Flexport is a logistics company. They aren’t in the business of selling software. What we’re doing right now is like the first GUI desktop apps - lacking consistency because there was no solid platform every designer reinvented the wheel.
- akrymski 7y agoThank god the browser provides the text input component otherwise every designer would have their own take on that too.