Motorola Droid and Google's Android OS
February 28, 2010
android
So last November, I finally got a smartphone (through work no less). Gotta love not having to pay that monthly phone+data bill. The iPhone always had a lot of appeal to me, but the thought of having to switch to AT&T wasn’t especially attractive to me. I’m not big on the restrictions Verizon usually places on their phones (let’s disable all the features of your phone out so we can force you to use an expensive VZW service instead and nickle-and-dime you to death). But it’s hard to beat their coverage. Long story short (too late), I ended up with a Motorola Droid running Google’s Android OS.
So far I’ve been pretty pleased with it. In general, integration with Google services is pretty solid (gmail, calendar, contacts). There’s the Google Market for installing new apps, and there are lots of pretty good free apps. At some point I’ll probably do some followup posts highlighting some of the apps I find clever/useful. The SDK is readily available and more importantly you don’t have to hack the phone to install non-Market apps (such as those you wrote yourself). So Google isn’t maintaining a chokehold on app distribution as Apple is. There are some really neat features of the Android SDK/API (e.g., a barcode scanner app can easily export it’s scanning routines so that other apps may rely on them). And of course there’s the added flexibility you get with multitasking support. But there are tradeoffs that come with this freedom.
I’ve never owned an iPhone/iPod Touch, but I suspect Apple has easily done a better job when it comes to general polish and usability. While a vanilla Android install seems pretty snappy (at least on the Droid), you can definitely bump into issues with responsiveness especially as you install more apps. You can definitely see the appeal of Apple’s approach to a restricted hardware platform since you know how it will perform, what features it will have, etc. Since Android runs on a variety of platforms, there’s no guarantee how fast a CPU, how much memory, how much storage, etc are available. And since it relies on every manufacturer to manage OS ports for their devices, there’s no guarantee that new OS releases will make it to all phones (or in a timely manner).
As far as the Motorola Droid in particular, it’s been a pretty solid phone. It’s got some heft to it, but feels more solid than heavy to me. The screen is pretty fantastic, and call quality is good. It’s nice having a standard headphone jack and microUSB connector instead of any vendor-specific nonsense. Most of the time, I find myself using the on-screen keyboard (especially after downloading the 3rd party Better Keyboard app), but occasionally having a physical keyboard is nice (such as when typing up long emails, or funky passwords). They’ve certainly made some sacrifices with the keyboard to keep the size/weight down (keys aren’t offset and they’re pretty flat without as much of the usual tactile feedback you’d like).
What I find most odd is their choice of the Dpad. It’s pretty big and forces you to a smaller keyboard. But it’s on the right side instead of standard left as you’d find on a video game controller. Makes it a little awkward since there are some pretty decent game emulators out there (I’ve got NES, SNES, and Genesis emulators installed at the moment so I can play Zelda, Mario, Sonic, etc). Not bad for a phone.