Proposed iconset for breeze

Posted in Core User Interface, User Interface Guidelines by

This is my proposed iconset for breeze.

breeze iconset

The icons are all based on a circle for reasons outlined in the previous post. The circle has a very low contrast radial gradient with the center of the circle being slightly lighter than the rim.

Colors are still pale and playful and should match the tint colors of the apps (I know this isn’t the case yet with the mockup I did a few posts back, but this is going to be fixed)

Let’s talk type

Posted in Core User Interface, User Interface Guidelines by

One of the basic things we’ve got to choose is the font we’ll be using. We need a sans serif font, with many weights and good quality. I personally like the new humanist sans fonts that have appeared (and almost dominated) the digital type in the last few years. Very nice examples are the Nokia Pure font, the Segoe UI font and Ubuntu.

For a free project we obviously need a free font. There is a very nice free/open source font recently developed by adobe, Source Sans.
That would be my choice for the nemo main font but, it doesn’t yet speak Greek, and you know, I would be filing bugs about my own choice :)

I’d like to note here that Greek and Cyrillic are a bit different than all the other scripts out there that can easily use their own font. Because Greek and Cyrillic have common glyphs with Latin, it’s important that they look the same. Especially for Greek as the GSM alphabet is mixed Greek/Latin (there is no true Greek support but only the capital Greek letters that do not have counterparts in the latin alphabet exist). Thus, if we had to fall back to another font, different fonts would be used only for the missing glyphs and Greek SMS message would look like this:


unacceptable and unprofessional

So the choice, at least for the time being, is Steve Matteson’s open sans.
open sans

It’s a font that looks modern, it’s easy to read, has many weights and isn’t extreme in any way. The only thing I have against it, is that it’s being used too much.

Happy reading!

Settings in applications

Posted in User Interface Guidelines by

Settings/Preferences/Options pages should be called Settings and reside either in the toolbar behind a gear icon, or in the menu, under a settings item. The menu item or icon should go to a seperate settings page in the page stack, with a back button. Settings must be applied immediately (no save button)


Rationale in this post.

Post tags


Posted in Core User Interface, Marketing material, User Interface Guidelines by

The posts are tagged proposal, draft and final. The proposals are just that. Things that come off our minds, and they might be plain stupid. Drafts are ideas that are generally acceptable and work can be started based on them, but more discussion around them may bring changes. Finals are guidelines or mockups that should be implemented as specified.

All the sources of this project available at

Because of a spam flood comments are disabled. I might enable them back at some point. However you can reach us on twitter (@qwazix, @nemomobile) or irc (#nemomobile)