When comparing Materialize vs WebUI, the Slant community recommends Materialize for most people. In the question“What is the best CSS framework?” Materialize is ranked 8th while WebUI is ranked 14th. The most important reason people chose Materialize is:
Ranked in these QuestionsQuestion Ranking
Pro Large selection of components
CSS components: Badges, buttons, cards, collections, footer, forms, icons, navbar, pagination, preloader.
Mobile-specific: slide-out drawer menu, toasts.
Pro Device agnostic
Since Materialize follows Google's guidelines for Material design, which in theory is device agnostic, Materialize itself is device agnostic too. It's designed to look good on every device.
Pro Great-looking demo
Pro Mobile navigation
Pro Nice showcase of sites built with Materialize
While the default style is not bad at all, Materialize also gives developers the ability to customize it and fit their own style, while still keeping in line with the Material Design philosophy.
Along with the CSS files, designers can also download the SASS files which can be edited and compiled.
Pro 12-Column Grid System
Pro Included icon font
Pro Meteor.js integration by developers
Material design is very opinionated on how design elements should behave and look. The basics of which revolve around certain visual elements (physics, space, momentum and light) which are used to create specific UX elements.
This is very helpful because it creates a consistent feel without making every design look the same. This can be seen in Materialize too, where each element may be customized but still it keeps the consistent look of the material design.
Pro Supports build customisation
Build customisation allows components that aren't required to be excluded using SASS includes and grunt tasks.
Pro Scalable CSS transform and SVG shapes
WebUI includes scalable CSS transform shapes and scalable clip-path shapes.
Pro Powerful tooltip system
The tooltip system includes viewport boundary collision detection, auto positioning and auto sizing for small viewport areas, configurable boundary margins, and many behavioral settings, such as focus, hover, static, nohide.
Pro Generic design
Every component is built to be generic and interchangeable. For example, there are no restrictions on where grids, containers, menu buttons, or dropdowns can be used.
Pro Multiple grid systems out of the box
WebUI includes a flexbox, a table, and standard grid systems. These grid types can be used in combination and together.
Pro Full support for flexbox
WebUI includes a full range of flexbox classes, including breakpoint specific classes based on REM units.