Re:Removing User Interface Complexity, or Why React is Awesome
by colinramsay on Tuesday May 13, 2014 @10:52AM
(#7738395)
Not even if bower let you search by component type or some kind of category or tag?
Re:Removing User Interface Complexity, or Why React is Awesome
by NathanKP on Tuesday May 13, 2014 @10:59AM
(#7738439)
The best interface for a react UI component repository would be something that had information like:
* A picture of what the component looks like
* How large the component is in KB
* Which CSS frameworks it requires or supports
* Cross browser support information
Bower is a very simple package manager right now with little information about the package beyond its name, a line of descriptive text, and a link to the Github.Overall the experience would be better for React devs to develop a customized package manager interface well suited to the type of packages being delivered.
Of course there is nothing stopping UI component creators from distributing their components on both Bower and a React specific package manager, but I think for purposes of discoverability a React specific one would be better suited.
However, it would be more convenient if there was a distinction between packages that are designed to be UI components, and packages like AJAX libraries, async, and other logic libraries, which are a better fit for bower.
Distributing the UI components via bower is doable, but it wouldn't be nearly as nice as a dedicated component ecosystem where it is easy to search and discover relevant React components.