Here’s a simple rule: if your product isn’t a condom then don’t name it like one. What am I talking about? Let’s take a look…

The simplest way for web developers to build native iOS, Android and web apps using a single HTML5 codebase.

Welcome to Android Design, your place for learning how to design exceptional Android apps.

Google, here is the problem: If you cannot make the UI of your apps consistent, how do you expect developers to follow your design language? Which one should they follow? You have to set the bar high. You have to show what a good app is supposed to be like.

To answer the question posed in the headline: yes, a prototype Android device looked like a BlackBerry phone. However, at least one other prototype Android device from the same time frame did not (and it wouldn't surprise me if Google was testing Android on several more prototypes with different form factors). On top of that, the SDK from that exact same time frame also included support for large touch screens. In other words, the argument is invalid.

“Na­tive vs Web apps on mo­bile; what do you think?” I think about it all the time. And I talk to de­vel­op­ers all the time so I think I know what they’re think­ing. Thus this piece, which is goes on and on and on but that’s OK, blog­ging is for long-form pieces! In­cludes a case study with screen­shots.

RT @timoreilly: brilliant post by @bgurley about #android in terms of warren buffet's castle and moat analogy

This is not a post about what Apple will or should do to improve notifications on iOS. It’s a post talking about what solutions other platforms currently use to notify the user, and why Apple is (possibly, probably) taking such a while to create an optimal solution to the notification problem.

Android has two major technical UX problems: animation performance and touch responsiveness.

Google's common Java library for parsing, formatting, storing and validating international phone numbers. Optimized for running on smartphones. A direct port to Javascript is also available.

What brand of freedom do you prefer? I find myself undecided. I don't like either brand, since neither really seems free to me. I'm sure, though, that saying Apple is an overly restrictive platform and Google/Android is a free and clear platform is a false dichotomy.

A virtual keyboard lives and dies by the details. It’s not that there’s a single feature which makes the iPhone’s virtual keyboard better than Android’s; it’s death by a thousand cuts. A number of small differences end up making a huge difference.8 Apple obviously spent a lot of time getting every little detail just right (well, except for the ducking dictionary), while Google decided to go ahead with what they had – which is usable, but no match for what the iPhone offers. I have no doubt that Android’s virtual keyboard will be improved in the future, and I’m looking forward to what they will come up with.