Don’t risk making a crappy UI, use Material Design

Don’t risk making a crappy UI

Use Material Design

Recently, I’ve been attacked online by Sturgeon’s Law. I realize that most things are crap. That’s common sense. After a brief reflection, however, I’ve come to the conclusion that this knowledge is not reflected in my modus operandi.

90% of everything is crap

Theodore Sturgeon

It changes the game

A 90% chance that the service or the software you are working on will prove itself to be crap is a big risk.

I’m a designer. is there anything I know that could help you reduce this risk?

What would I do if I had been trying to create a commercial piece of software and wanted to minimize the chance that its user interface turns out to be crap?

I would build the interface using Material Design: a mature, constantly developed visual language with very good documentation and pattern library. the principles of Material Design include issues from typography to iconography, layouts to onboarding, and the presentation of the new features in an application. the pattern library includes components from dividers to buttons, text fields to dialogs and steppers. Consistent use of Material Design significantly reduces the risk of a crappy user interface.

Being consistent is extremely important at this point. In each project, there is always the temptation to go against to the adopted conventions. More often than not, it ends badly.

Consistence (like simplicity) is difficult but essential.

What does consistency means in the context of Material Design

Examples from the documentation of Material Design:

With Material Design, you can design not only the user interface of your web application but also versions for tablets and phones (and not just Android phones).

Example from the Material Design’s documentation: “Material Design’s responsive UI is based on a 12‑column grid layout. This grid creates visual consistency between layouts, while allowing flexibility across a wide variety of designs. the number of grid columns varies based on the breakpoint system.”

It’s worth the time to choose an optimal library, which will allow you to quickly implement Material Design. In the case of a web app, I’d recommend looking at Material‑UI first. Check out Polymer afterward. Material‑UI and Polymer both provide ready to use components that implement Google’s Material Design. Material‑UI has the advantage of being compatible with React — one of the most popular libraries for building user interfaces. Polymer has the advantage of being an open-source project led by a team of front‑end developers working directly at Google. Both libraries enable you to move fast without breaking too many things.

What if Material Design does not suit some of your needs?

What if you need to do something that Material Design documentation does not mention? Well, I’ve been designing user interfaces using Material Design for more than two years, and I can assure you that that won’t happen often.

You may miss an icon or three, but The Noun Project, Material Design’s documentation, and a few hours of designer’s work will let you solve this problem easily.

So how about it?

Would you give Material Design a chance?

Let me know if you come across any obstacles.

All examples of the documentation of Material Design are licensed under the Apache 2 license.

Thank you for your timeEnjoy the rest of your day

© Gregory Wolanski