The State Of The Mobile OS Debate
As performing essential work outside the four walls becomes a standard way of doing business, companies - and you, as decision makers - will be making a heavy mobile investment. You'll want to choose devices with an operating system (OS) that can support your intended use. Enter the debate about whether .NET (Microsoft's mobile OS) or J2ME (Java 2 Platform Micro Edition, Java's mobile OS) is better suited for mobile deployments.
One of the selling points of J2ME is that it gives users the ability to customize their operating environments. Users can choose applications, and design the look and feel of those applications. J2ME also has IBM on its side as a key Java developer; therefore, IBM's partners provide a range of applications for J2ME users to access. However, Java's language is complex, so your IT staff's knowledge of programming languages needs to be rather advanced. Also, J2ME is often limited to running thinner-type client applications such as messaging, e-mail, Web browsers, voice, and some client-server applications.
With .NET, you're talking about Microsoft, which gives this mobile OS an advantage in itself due to Microsoft's industry presence. .NET provides users with a streamlined working environment that mirrors what users are used to seeing on PCs. Your company's applications are usually in a Microsoft environment, so back end interoperability is easier. Also, .NET can handle thicker-type client applications such as data-heavy field service and route delivery programs. However, the fact that .NET is from Microsoft has its downfalls - Microsoft's application vulnerabilities are frequently exploited, so security is a bigger issue (how often have you downloaded Windows patches on your PC?).
Still, .NET is the frontrunner of the mobile race. A recent survey of Integrated Solutions' readers (enterprise executive management, IT decision makers, and operations managers) by Venture Development Corporation supports this. Almost 46% of the responders currently support .NET, while 25% support J2ME.
A third element to this debate is Research in Motion's (RIM) popular BlackBerry devices, developed with Java programming language. RIM reached 2 million users a couple months ago and has formed partnerships with more than 100 ISVs (independent software vendors) to extend applications like CRM and sales force automation to mobile users. Until recently, the OS was still Java-based. However, RIM is not overlooking the prevalence of Microsoft users. It created Blackberry Enterprise Servers (which sit behind the corporate firewall and create the BlackBerry environment for the devices) for Lotus Notes, Novell GroupWise, and Microsoft Exchange. Also, RIM recently released its new development framework, BlackBerry Mobile Data System v4.1, that supports both J2ME and .NET mobile environments.
I attended Gartner's annual Mobile and Wireless Summit in April, where Gartner analyst Nick Jones presented a session on this topic. The gist of his presentation was that no mobile environment has everything you need. In all mobile deployments, you'll need partners and middleware providers to get your solution off the ground. Both .NET and J2ME have their pros and cons, so to make your decision, you should look at how you'll be using your mobile devices. If your workers will be doing data-intensive work remotely, and their application use is limited to one or two specific programs, .NET is probably a better choice. If you have mobile professionals who need e-mail on the go, messaging, and access to multiple back end applications (without bring a large amount of server data down to the device), J2ME is more the way to go.
Of course, there are exceptions to these statements. Integrated Solutions' June mobile feature story discusses how contracted tractor-trailer drivers for CSX Intermodal use BlackBerrys to communicate with their home bases. The true winner of the mobile debate is you, the adopter. You have two strong contenders to choose from for an OS, and an ever-evolving industry of software and hardware developers that continue to make it more feasible to adopt either OS.