Compared to the seamless nature and ease of use of Meteor, the state of UI frameworks right now is pretty terrible. Which is probably why Meteor didn’t pick any particular CSS library or set of UI components to (really) integrate with.
Bootstrap and MaterializeCSS both have refused to use Flexbox, citing the ~3% IE market that doesn’t support it properly. The Bootstrap boilerplate code you have to add around everything never made sense to me, and I always had to copy the code for any form elements from the docs.
I’ve reviewed over 30 UI components libraries and so far it seems that Webix is the best choice for picking one library for a complex app, and being done with the selection process: it’s fast, has a Material Design theme, brings almost all the components you want (grids, trees, treegrids, accordions, tabs, carousel, charts, uploader, windows, tag autocomplete, calendar, forms, color picker, master-detail etc.), is open source yet supported commercially (MIT license in the works), and their team has built the core of a Meteor integration. It’s also relatively small (128KB minified for all the 50+ components and ~135k for the Material Design CSS). By comparison, MateralizeCSS is 258k and it needs jQuery too.
The code is very concise and expressive. Check out this demo:
Designing layouts in Webix is similar to using the flexbox model (there’s a
gravity property that’s equivalent to
growth). Adding a resizer between two components/panels is only one line of code. A visual designer is planned for September.
Webix has a few issues, sure: the documentation needs editing, some mobile specific components aren’t there yet (e.g. side drawer), contributing is harder than it should be, and the Meteor integration needs some more work (I’m on it). But with a profitable company behind it, who’s active on the forum and pushes regular updates, I find Webix very promising and I’m using it in the admin app for iDoRecall.