How to approach mobile is a tough question with a simple answer: It depends. It certainly depends on budget and it certainly depends on the vision and business model. But it also certainly depends on what-you-want-to-get-out-of-it (WYWGOOIT, candidate to be the most horrible acronym in the entire history of modern computing).
A tough question is not necessarily hard to answer. It only requires more context and deeper understanding of the underlying mechanics. So, as a company, what you want to get out of your mobile platform?
- Are you selling a consumer platform? You need to have it integrated with web and social and available on three major mobile operating systems (iOS, Android, WIndows Phone). This poses a number of issues including those discussed in other posts on this blog such as “Windows Phone and the Low-or-Nothing Dilemma” and “Android Matrix-reloaded“.
- Are you selling an enterprise platform? You need to focus on one mobile platform to develop your services. Your customers may be primarily interested in the added value of your services and products rather than the fact their personnel may work with an iOS or Android or BlackBerry or Bada device.
If you’re selling an enterprise platform the mobile part of it must more than everything else seamlessly integrate with the backend. And the backend can be whatever combination of technologies you wish. In an enterprise logic, Windows Phone is the ideal frontend of an excellent stack that relies on Azure, Office, SQL Server, .NET Framework, C# and the like.
In a mobile perspective, Microsoft has a tremendous platform. And Windows Phone is on the top of it. Easy and effective.