MIDP 2.0 offers a number of enhancements over the older version of Java cell phone software. For games, for instance, it comes with sound features and a standard way to handle graphics layers such as foreground characters and background scenery. "The user interface in MIDP 2.0 gives application developers more control over the look and feel of their applications," Lorain said. It mandates a standard method for downloading programs over cell phone networks. That's likely to be a boon to software and wireless companies that want to make money selling cell phone programs. Data is handled more gracefully. MIDP 2.0 lets data be stored on the cell phone where its predecessor relied on fetching it from the network, said Eileen Mercilliott, senior manager of Nextel's J2ME products and developer program. Nextel, which will begin shipping its first MIDP 2.0 phones in October 2003, also likes Record Management System (RMS), a database of information such as contact names and phone numbers that can be shared by many programs on the phone. Another part of MIDP's promise is the replacement of a profusion of unique devices with a more standard infrastructure for programs. For phone software companies, that means a larger market, and for cell phone companies, it means less development effort. MIDP 2.0 is also expected to offer a big leap in support for Internet data services compared with the current version of the software, tantalising some with visions of new billing opportunities. Java already offers support for Web access on cell phones, but surfing hasn't taken off due to relatively slow connection speeds and cramped screens that make it hard to display Web pages designed for PCs. MIDP 2.0 is designed to address some of those shortcomings as cell phone makers prepare new, higher-powered models. A new place for 'push'?
One of the most significant features in the new Java version, expected to begin arriving in new phones in the second half of 2003, is the incorporation of "push" technology for business customers that send data to employees on the road. With this technology, a customer filling out a trouble ticket on the Internet could prompt a server to "push" the customer's address and problem description to a technician's cell phone. Receiving that information could trigger the phone to launch a program that downloads driving directions. And afterward, the technician could use the phone to update the server about whether the problem had been solved. Companies such as Cingular Wireless and Verizon Wireless are now pushing news and sports scores to their customers to encourage more surfing by mobile phone. MIDP 2.0 gives push more abilities such as responding to messages or using the messages to send and receive applications over the air, said Sanjay Gupta, Motorola senior manager of global standards for the mobile networking team. Today's push experience is primitive by comparison. Email lands in a cell phone's in-box and can be read, but very few services go beyond that. "What you end up doing today is instigating the user," Gupta said. "It's more like a little pin prick to somebody to go do something now. The user experience now leaves a lot to be desired." The pitfalls
For all of the improvements touted by MIDP 2.0's backers, some manufacturers have expressed concerns about the relatively heavy memory needs of the new version, which requires 100K more memory than its predecessor. For handsets with several megabytes of memory, such as Motorola's $400 (about £270) i95cl model, the upgrade is feasible. But manufacturers will have trouble fitting the new version of MIDP 2.0 into lower-end phones without much memory to spare, according to Yach. RIM currently uses MIDP 1.0 in its Blackberry handset. The extra 100K of required memory may also make it impossible to upgrade some Java-enabled handsets already on the market, Yach said. These phones simply don't have enough room and, unlike personal computers, most cell phones can't be upgraded with more memory. Bill Nguyen, founder of wireless messaging company Seven, says that MIDP 2.0 will be used predominantly for "heavy" business applications, so his company will work on applications along those lines. Not everyone believes the additional memory requirements will be a major problem. "I don't know what our MIDP 2.0 product roadmap looks like right now," said Victor Brilon, Java applications manager at cell phone giant Nokia. "But we're definitely not talking about excluding it from some low-end phones." Siemens spokesman Jacob Rice said the handset maker is already building more memory into most of its cell phones for new features such as complex ring tones or messages with attached files. There's likely enough cushion to fit a fatter MIDP 2.0. "This isn't a major concern," Rice said. Nextel's Mercilliott agreed, arguing that MIDP 2.0's memory penalty is worth enduring. "We are increasingly moving toward phones that have more memory," she said. "Our customers that are looking for the more sophisticated capabilities are going to be willing to invest in the new devices." Whether that implies high-end MIDP 2.0 business applications are around the corner, or something else, remains to be seen. "It looks to me like they built a game platform," Venture Development's Lanfear said of the new Java. "That appears to be where the money is coming from."
If it moves, we cover it. See ZDNet UK's Mobile Technology News Section for the latest news, reviews and price checks on mobile phones, PDAs, notebook computers and anything else you can take away.
Have your say instantly, and see what others have said. Go to the ZDNet news forum.
Let the editors know what you think in the Mailroom.
Talkback
I hope this does catch on. We currently have created a golf scorecard (www.wireless18.com) which is a java downloadable application for mobile phones. We like it but you never really know if anyone else will find it useful. Even though it is late 2003 were still sticking to MIDP 1.0 as MIDP 2 still has limited support.