4 ms·
That's awesome! This space is still really, really ripe for tools. Looking at some of your past comments, it sounds like we're thinking about these problems / p
by RickS 7y ago
That's awesome! This space is still really, really ripe for tools. Looking at some of your past comments, it sounds like we're thinking about these problems / pain points in similar ways.
One of the things I observe that's potentially good for smaller players and less exciting to a team like mine is that ~80% of the market is web/react only, and very satisfied with things that are 1) narrowly scoped in terms of platform coverage 2) mostly about "stickers" or pictures of design, even as more advanced players are itching to design with more dynamic, deeply integrated component representations.
I'm curious about your thoughts on what it means to "nail it" with a full-scope / all-inclusive solution to design systems problems. Currently, I think that an ecosystem of smaller, more tightly scoped tools is the likely path forward. Designers will be plumbing together pipelines of modules that fit their specific needs, the same way a react project would today. I did a thread on this you might be interested in [1].
Feel free to ask whatever – anything I can say is fair game, and anything I can't say I wouldn't have said anyway.
[1] https://twitter.com/graphrick/status/1139964218243874816 https://twitter.com/graphrick/status/1139964218243874816
- tenaciousDaniel 7y agoAwesome, thanks a lot! I'll try not to prod too much, knowing that you work for Adobe. As it happens, I am working directly in one of those areas you mentioned. I'm trying to create a nicely abstracted language that designers can use to describe components from a platform-agnostic angle. Something more nuanced and sophisticated than "pictures of design", but something that doesn't leak implementation details. A shared language that teams of designers can use to communicate not just with themselves, but also developers.