How many more ui kits will we build until we develop a standard for the wider ecosystem of ui components?
Panels, cards, pickers of all kinds, trees, etc. The mess of ui kits we deal with only causes duplication and increases integration workload while limiting compatibility with functionality frameworks. (React, Angular etc.)
I think we have had long enough to see what UI functionality is most needed since 99% of Ui kits contain the same ~50 components. Isn't it time that we standardize these? It seems the whole reason for the web component standard to exist is to allow devs to add the missing ui components from the current HTML standards.
How many more ui kits will we build until we develop a standard for the wider ecosystem of ui components?
Panels, cards, pickers of all kinds, trees, etc. The mess of ui kits we deal with only causes duplication and increases integration workload while limiting compatibility with functionality frameworks. (React, Angular etc.)
I think we have had long enough to see what UI functionality is most needed since 99% of Ui kits contain the same ~50 components. Isn't it time that we standardize these? It seems the whole reason for the web component standard to exist is to allow devs to add the missing ui components from the current HTML standards.