Usage of design systems: React V3
Google Material Design System
Don’t risk making a crappy UI, use Material Design👌🏾
Don’t risk making a crappy UI, use Material Design👌🏾
Understand why Material Design – it’s not a must to implement Material Design in web app, but the guideline serves as a really great starting point for many use cases, while still allow unique brand expression for a product ( Color, typography, illustrations etc.). And it’s a guideline, so nothing is set in stone – it’s an evolving design system and it’s OK to deviate with strong reason sometimes.
Material Design will gradually be extended throughout Google’s range of web and mobile products, providing a consistent experience across all platforms and applications. Google has released APIs for third-party developers that allow them to easily incorporate the design language into their applications. Material V3 Library, an extended version of the material design library with react components that implemented Google's Material Design.
Figma material design UI KIT
It was by applying it as part of a B2B web application project, methodically and respecting its guiding principles, that the magic worked.
The more screens were available, around sixty in total, the more I realised to what extent this system was able to cover an infinite number of issues and bring very strong consistency to the entire experience. Google Material Design has faced the difficulties that we regularly encounter in a B2B environment: complex forms at several levels, management of data organised in tables, coexistence of several option menus, etc.
The other dimension that is reflected in the solutions offered by Google Material Design is ease of use: display only useful content, at the right time with clarity and consistency. This is absolutely obvious, but trade-offs are not always straightforward in the case of applications that handle large amounts of information.