I know we talk a great deal about the device not mattering, and it ultimately shouldn't. But if organizations need to standardize around a mobile device or platform, they still need to pick one.

Given all the changes to Android, iOS, and even Windows Phone 8 in 2012, plus anticipated changes to RIM in 2013, which platform has the most to offer for enterprise mobility going forward?

What are the pros/cons of each given the realities companies face to enable mobile productivity.

I'm trying to make this broad enough to run with the question any way you see fit, but also keep it fairly confined. I'll leave the discussion open through the weekend and for parts of Monday.

If BlackBerry can win back developers, it still has the most to offer -- security, manageability, reliable email -- from a pure enterprise mobility standpoint.

The problem is the overall mobility market, where consumers rule and BlackBerry faces a much steeper climb. If an organization is going to standardize, it needs to pick a platform that employees will use, and that means either iOS or Android.

I can't edit my initial post, but I'd like to add a disclaimer of the potential existing to publish this conversation on SearchConsumerization.com. (Thanks, Colin!)

I am an unapologetic Apple user, so if you're really putting the gun to my head, I'm choosing iOS. It's a complete ecosystem compared to the challenges of supporting Android's variety of devices, versions and manufacturers. I also strongly prefer the Apple App Store and I believe that it is a major edge in the consumer personal use arena.

That said, I do think a complete policy should include an Enterprise Mobility platform for security that supports both iOS and Android. While it's not my personal choice, it would be shortsighted and ill-advised to overlook the popularity of Google.

Maybe these ARE the Droids we were looking for. :-)

- Walt

When considering mobile in large organizations, one should consider the opportunity to use the devices for mobile learning, onboarding, job tools, etc. Our recent work in mobile (over the past 2 years) has given us insight into how organizations are using these devices and what the shortfalls and advantages are for different types of devices used for corporate training to job tools like Jetblue's online facility map (designed for Blackberry) . We have a technical needs assessment embedded here allencomm.com
You can click it to see a larger version. I think this assessment is helpful for large organizations considering what technology can work best for their audience.

Walt, I agree that Android fragmentation is a problem, but nobody's saying you have to support the entire Android ecosystem. An organization can go with Android and limit users' devices to one (or a few) that meets everyone's needs. Plus, if you go with the Nexus devices, you know you'll get regular updates.

Colin, since we're in this alternate reality where we are rejecting one entire mobile OS, I guess it's entirely reasonable to further limit the choice of devices within Android... hahah

Really though - I think if you go with Android, you need to be prepared for the variety of devices. One more reason to go with iOS in this scenario... you can comfortably accept every phone and tablet.

Ideally, an organization would support everyone on the planet. However, that's not realistic (Not enough value to outweigh cost). Supporting specific devices isn't the answer either (too specific/ narrow).

Therefore, I've taken the approach to support specific platforms and leave it there. For example, if you support iOS and Android, you cover a very large portion of the market (and users) without overextending yourself.

You can always default to a generic HTTP based approach to cover the non-iOS/Android population. Less functional, but more inclusive.