Based on some experience (designer and developer), here’s some thoughts I currently have about them:
- high-level idea is usually understood, although mixed with design tooling
- practical usage rarely straightforward
- most of the activities are surface level and trivial
- required effort to maintain and develop often underestimated
- maturity level rarely reaches the potential
- ”component” is not an easy concept, especially in multi-product setting
- too often design driven, when implementation driven would make more sense
- generates meetings on many meta-dimensions
- not necessarily rewarding exercise for the maintainer due to various organisational and political challenges
- does not actually help on design-to-development e2e flow as much as advertised
- even with all the work put in, does not guarantee good product
- high-level idea is usually understood, although mixed with design tooling - practical usage rarely straightforward - most of the activities are surface level and trivial - required effort to maintain and develop often underestimated - maturity level rarely reaches the potential - ”component” is not an easy concept, especially in multi-product setting - too often design driven, when implementation driven would make more sense - generates meetings on many meta-dimensions - not necessarily rewarding exercise for the maintainer due to various organisational and political challenges - does not actually help on design-to-development e2e flow as much as advertised - even with all the work put in, does not guarantee good product