3 ms·
This article was pretty confusing. At one point I thought the main thesis was to take inspiration from software APIs to document the process between the design
by omneity 7y ago
This article was pretty confusing.
At one point I thought the main thesis was to take inspiration from software APIs to document the process between the design and development team, which already looked like a pretty horrible proposition, taking Anti-Agile to a new extreme in the Individuals and Interactions vs Processes and Tools spectrum.
But then ... I just got lost.
So is the idea to build a REST API to serve constants of a design system, such as colors and font sizes and have a single reference point?
Design tokens and standard formats seem to go in this direction, but honestly this seems like one of the last problems to solve, in the Design System space.
Please someone enlighten me if I'm misled somehow.
- jaksawesome 7y agoI think you're right about this. In fact, I think the API ecosystem would be better served by trying to take inspiration from design teams to provide more standardized, compliant, and good-looking interfaces.
- omneity 7y agoExactly, that looks like a much better cross pollination. I was secretly hoping TFA would talk at one point about API design and leveraging design systems to bring uniformity and consistency to software APIs. That would have made for a much more juicy proposition.
- jiofih 7y agoDesign System teams need to stay busy after they exhausted the 17 different ways to redesign a toast notification that still only serves 10% of the product needs, and management needs a roadmap for next year.