Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Can Microsoft Windows Phone & Nokia Replace BlackBerry in Enterprise?

DZone's Guide to

Can Microsoft Windows Phone & Nokia Replace BlackBerry in Enterprise?

· Mobile Zone
Free Resource

Download this comprehensive Mobile Testing Reference Guide to help prioritize which mobile devices and OSs to test against, brought to you in partnership with Sauce Labs.

Jeremy Windmiller in his blog post wonders: “Can Microsoft Windows Phone & Nokia Replace BlackBerry in Enterprise ? ”.

Jeremy talks about a scenario posed by the VP of IS Infrastructure at a Midwest Healthcare System to several colleagues for retreiving the feedback on a project he did for his MBA class.

What would you do if you were in charge of all corporate cellular telephony decisions, and Microsoft came to us within the next year offering:
  • Fully encrypted devices
  • Device management using the same tools that manage your servers and desktops.
  • Devices with more consumer appeal than RIM. (And a broader range of devices, now manufactured by HTC, ZTE and Nokia.)
  • Per device license costs significantly lower than RIM.
  • Excellent Exchange / Outlook integration.
  • Better native cloud storage (whether public or private) integration than even Apple or Android.

 

Jeremy discusses about the various strengths, opportunities, weaknesses and threats for Windows Phone in the Enterprise.  He also has his own ideas for the strategies Microsoft and Nokia should implement to be successful.

What do you think about BlackBerry's future in the enterprise vs. Windows Phone?  Do iPhone and Android have a shot at wide enterprise adoption?

 

Analysts agree that a mix of emulators/simulators and real devices are necessary to optimize your mobile app testing - learn more in this white paper, brought to you in partnership with Sauce Labs.

Topics:

Published at DZone with permission of Senthil Kumar, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}