Icon design

A treasure trove of cohesive design principles for developers and designers everywhere

As Google's Android matures, we all can see the shift in focus to great design. Google has long been at the forefront of the technology, offering services and features that most of us use every day, but it's clear that Mountain View now cares as much how their products look as they do how they work.

Getting a glimpse into Google's design language for Android usually means looking at the apps while you're using them, or opening up the files and studying the assets themselves. While Google offers some rudimentary suggestions at the Android developer site, that's only part of the picture. Developers and designers need to know how it all fits together. Apps, the web, and all the services under Google's umbrella.

Source: Behance (part 1), (part 2). Thanks, Melvin!

Geometric shapes

Enter Google's senior graphic designer Roger Oddone and art director Christopher Bettig. Together with other great graphic designers and contributors, they have compiled the mother lode for both Google itself and third-party vendors. Six months in the making, the Google Visual Assets Guidelines project hosted at Behance brings everything Google together in regards to design.

The assets cover everything from icons to fonts and logos, and does wonders to help create a uniform look and feel to help all applications resemble the beautiful design we see in recent projects like the Google+ application. If you're a developer or user interface designer on any level, you'll find plenty of insight to help your project blend with Google's design trends. Anyone who appreciates great user experience design will take something away from this one, and we hope everyone does.


Reader comments

A look into Google's visual design guidelines


I'm glad google does its things this way. First they made android functionally better and the next step is to make it visually better.

Posted via Android Central App

"I'm glad google does its things this way. First they made android functionally better and the next step is to make it visually better."

... and the next step is to drop their own UX guidelines and reinvent (copy) the wheel - again and again. Recent bad example: Google Maps 7. It's more a copy of the iOS 7 app, starting with the icons and color scheme, missing UX patterns (actionbar, menus)

It's like a epedemic: the new (old) sliding drawer menus. They dropped the sliding drawer component recently from the SDK, to introduce this old pattern in the support library (ignoring their own styleguide).

One more step to the ultimate fragmentation and missing platform recognition. Well done, Google.

It's too bad devs keep treating Android like its an unwanted step child.

Some are so slow about updating their apps and the design that it doesn't make sense. Say what you will about iOS, but devs are really quick to get on board with the updates of their apps. I guarentee you that come iOS 7 release time, the vast majority of apps will be ready to fit in with the new look.

Lets not get carried away here.

Why do iOS developers quickly conform to whatever Apple says? Because they have no other choice. If they dont, their app could get pulled it it doesnt meet UI and UX guidelines set out by the almighty fruit. It comes back to the walled garden.

Now this is nice I suppose, but many google apps out there look good and are functional without conforming to the "guidelines" set out by Google.

That is exactly what they are, guidelines. They are for guys like me who once and awhile make an app for a specific reason and want to try and get it to fit in with the rest of the OS.

Now where Android gets its crappy name is those developers looking to make a quick $$$ and dont care what the app looks like.

There should be some kind of check when an app gets published to the play store to make sure that the app at least tries to look decent..