I'm an Android fan. Over the years I've used lots of smartphones running lots of OSs, and Android just works for me.
And yes, I used an iPhone for 5 months before abandoning it. Why? The primary reason was the keyboard. I use my phone for email more than I do texting or talking, and so, for me, the keyboard is critical. Everyone said give it a few months and you'll get used to it, but nope, in all that time I was never able to write a single email or text message without having to go back and make corrections. Plus, iPhone always felt like I was using someone else's device, not one that I could tweak and adjust and tinker until it looked and felt like mine. So, sorry, no iPhone for me. (It's worth noting that when it comes to tablets, I have 5 of them, iPad is my favorite. I use my phone for email far more than I do the tablet, so the iPad keyboard does not stress me out as much as the iPhone one does).
What about Windows phones? The new Nokia Lumia devices running Windows are spectacular, boasting what appears to be the very best email client and support on any device out there right now. And I actually could see myself using one in the future. Perhaps.
For now though, it's Android for me, and has been for several years. I like the OS, I like the options, I like the openness, and I like the flexibility to make the phone my own.
But unlike iOS where you have a single device vendor offering a single experience, Android consumers have lots of options to choose from, and the differences between them range from subtle to significant. Over, the past few years I have tried and used lots of Android phones, and I do mean lots. And here is what I have learned:
Part of what gives Android its flexibility is the fact that device vendors can tweak and enhance the OS to create a unique customer experience. (Of course, this is also what makes Android devices far less consistent than iOS devices). Device vendors do this by creating custom overlays (skins) that sit on top of the Android OS itself. You can indeed buy devices running pure unadulterated Android (for example, the Galaxy Nexus) but most Android devices come with vendor created skins which create the vendor specific Android experience. Ok, keep that in mind, we'll come back to it in a moment.
Motorola brought us the Atrix (and its successor, the Atrix 2), the Droid devices, and more. I've made the switch to Motorola Android devices twice, and gave up both times. For starters, I found the Atrix case to be too plasticy and flimsy, it felt too light and crushable. But the bigger issue for me was the Motorola Android skin, Moto Blur, which at times feels just too heavy and intrusive and in-your-face. Requiring the creation of a Moto Blur account just to turn the phone on and use it? Unacceptable. Custom versions of stock Android apps? Great idea, but not when they feel slower and more sluggish. I've heard that Motorola has recently made changes to Moto Blur so address some of these issues, but I have yet to try the changes for myself. Bottom line, based on my Motorola experiences I'd be hard pressed to try one again anytime soon.
Next up is Samsung, currently the number one Android device maker in the world. At various times I have owned and used 4 different Samsung devices (and several immediate family members have these, too), and the experience makes it easy to understand why these are so popular. Earlier devices, like the Captivate (local version of the Galaxy S) had a really poorly designed case that could open too easily, but those issues have long been addressed. The Galaxy S2 (both the 3G version and the considerably larger LTE version) are well built, feel good to hold, are fast and responsive, and boast gorgeous screens. TouchWiz is Samsung's Android skin, and in addition to being bright and colorful and even fun, it adds useful social integration features, and also replaces or enhances stock apps. But I also find it irritatingly juvenile. From the colored text messaging bubbles to the overly cartoony app icons, at times TouchWiz feels in the way. But my biggest problem with the Samsung devices (and I experienced this on all of them) was a reliability issue with the mail clients. As I noted previously, e-mail is a huge part of what I use my phone for, and I need Gmail and Exchange clients that are capable and powerful and responsive. And while I appreciated the extra features that Samsung added to the stock Android mail clients, problems like mail getting stuck in the Outbox folder forever made them close to unusable. Still, I stuck with Samsung for a long time, and could see myself using one again in the future.
Which brings me to HTC. I was first introduced to the HTC Desire HD by my colleague Serge Jespers who was thoroughly enjoying trying to make me jealous of the screen and performance. He succeeded. I bought the local version of the Desire HD in early 2011, and was hooked. The phone was heavy, but featured a rubberized back, and an industrial design inspired curved case that just felt so good to hold. It also featured one of the worst battery and SIM compartments I have ever seen, impossible to open and harder to close - you can't have it all. HTC has their own Android skin called Sense. It feels lighter weight than Moto Blur or TouchWiz, it's definitely cleaner and more professional looking, and best of all, the enhanced versions of the stock apps feel right and intuitive and even native. Oh, and I have yet to find a single undelivered piece of email in an outbox folder on any HTC device to date. The downside? The AT&T version of the Desire HD was needlessly crippled by really poor radio inclusion which cause no 3G in Europe and no coverage at all in Japan. So a while back I updated to the HTC Vivid, an LTE phone with every radio you could want (it works everywhere), and a stunning screen. It also features a pretty but terribly designed back cover that slides off at the most inopportune times.
You see the problem? I like stock Android, but HTC Sense really does work for me. I want a phone that feels good to hold, and has a solid well thought out case. And I also want every possible radio, a top notch screen, and killer performance. Yep, I want it all.
HTC phones are currently my Android devices of choice. They are not perfect, but they are the best for the type of use (and abuse) I throw their way.
As for what is next? The HTC One X is now days away. Could it be the perfect phone? Stay tuned ...
Andy Trice has created app-UI, a collection of reusable application container user interface components that may be helpful to web and mobile developers for creating interactive applications using HTML and JavaScript, especially those targeting mobile devices. As per Andy, app-UI was born out of the necessity to have rich and native-feeling interfaces in HTML/JS experiences. It works great with PhoneGap applications, and can easily be styled/customized using CSS.
Ray Camden has posted an excellent article explaining the fundamentals of data synchronization between a PhoneGap client and a back-end server.
"Smartphones and tablets are everywhere. If you need to reach your customers or employees on these devices, now's the time to start developing mobile apps. We provide essential information to help you get started, including development basics for Apple iOS, Google Android, RIM BlackBerry and Microsoft Windows. We also look at the pros and cons of cross-platform development and discuss how to build secure apps from the get-go."
Thus starts InformationWeek Reports' new report on Mobile App Development, for which I was interviewed, and which includes coverage of building apps with Flash/AIR and PhoneGap.
Adobe Shadow is a new inspection and preview tool that allows mobile web developers and designers to work faster and more efficiently by streamlining the preview process, making it easier to create and optimize content for mobile devices. Shadow allows device pairing, synchronized browsing and refreshing in sync with your computer, and remote inspection and debugging so you can see HTML/CSS/JavaScript changes instantly on your device. Shadow is now on Adobe Labs, and the Shadow team is also blogging.
In this Adobe TV video, Lee Brimelow and Thibault Imbert discuss the enhanced graphics rendering engine and the Stage3D API, enabling developers to port their Flash games to mobile with performance greater than 60 frames per second.
What is Apache Cordova? The core code that drives PhoneGap has been donated to the Apache Software Foundation. Apache Cordova is thus the engine that powers PhoneGap, similar to how WebKit is the engine that powers Google Chrome. And the Apache Cordova site is now live.
Fellow Adobe evangelist Christophe Coenraets recently posted a three part article on building a CRUD application using HTML and the Backbone.js framework. He has now followed it up with a post on building a mobile app using Backbone.js And PhoneGap.
