In fact, let me tell you what the recipe for determining what your "smartphone strategy" should be: 1. Think hard about whether you can ship an HTML5 version that your customers can find, use, and be delighted by. If so, do that and skip the rest.2. If the answer to #1 is no, build an iOS app.3. After you get to a million downloads (yes, 10^6) think about writing a version for Android. But only after you GOTO #1 and re-evaluate that issue. Before you stop reading, consider this: I have 3 Android phones. I worked on several Android projects at HP. I love Android, but I love it as a political statement only because Apple's controlling stance on everything creeps me out. If you want users with credit cards that spend money, mainstream reach, or a platform that actually might make an interesting case for abandoning open standards ("write once, run almost anywhere"), then iOS is it-- for everything else, just be happy the mobile web is now a legit platform to deploy to.

via theonda.org Good advice. I would add, that you should be thinking smartphone / mobile access to your website from day 1. In fact, you might even do mockups / wireframes along with your MVP that actually target mobile use cases, and decide whether to build those first. Depending on your market and specific application, you may actually find that you're a "mobile" company / service rather than a desktop web one. And by targeting mobile first, you know that it will work on the desktop.