Designing for Android

Sebastiaan de With:

Designing the app was difficult. It wasn’t just difficult for the obvious reasons, like implementation details, aesthetic preferences, and because you want to add more and more to an application as you go along designing it, but also because Android is simply a really hard platform to design for.

Take for instance all the screen technologies and qualities between the hundreds of Android devices out there. doubleTwist Alarm uses a very dark color scheme to ensure it is pleasant to use in dark spaces and uses a small amount of battery power on most Android devices — AMOLED screens actually use over double the power of ‘normal’ screens, like the iPhone’s, when displaying bright colors — and it prompted numerous other designers to ask me what the secret was: how did we overcome the challenge of designing for such a wide target and ensure a legible design that didn’t appear banded, jagged or otherwise completely screwy on [insert screen technology]?

If you require a short url to link to this article, please use

designed for use cover

But wait, there's more!

Want to read more like this? Buy my book's second edition! Designed for Use: Create Usable Interfaces for Applications and the Web is now available DRM-free directly from The Pragmatic Programmers. Or you can get it on Amazon, where it's also available in Chinese and Japanese.