Behind the scenes of Google's new type system

When Android first launched as a mobile platform, I designed its typefaces Droid Sans and Droid Serif. These web fonts were extended to include quite a few languages, and I created several scripts in the same style. After the launch, there was a strong desire at Google to go for global coverage, so that there would no longer be any ‘tofu’ characters, the blank boxes people get if they try to search in a language that isn’t supported by their operating system.

At first the brief for Google Noto was to create one typeface, with one character for every unicode point. But we soon realised we also needed a bold to show emphasis in text copy or on buttons on the UI , and an italic too. Later, we also added a serif, because Google wanted to be able to set formal documents in a serif typeface. Many writing systems don’t have the notion of serifs – instead they have height and low contrast – so that was an interesting process.

Thank you for reading 5 articles this month* Join now for unlimited access

Enjoy your first month for just £1 / $1 / €1

*Read 5 free articles per month without a subscription

Join now for unlimited access

Try first month for just £1 / $1 / €1

Steve Matteson, Monotype's creative type director, joined Monotype in 1991, where he worked on technical and aesthetic aspects of type production. In 2004, he left to form Ascender Corporation and designed UI fonts for Xbox and Android, among many others. Since rejoining Monotype in 2010, he has focused on improving type for the screen and legibility for the car and aviation industries.