J2ME Luminary: John Muhlner of Sun Microsystems

Print-friendly Version

John Muhlner is the J2ME Platform Marketing Manager at Sun Microsystems. He's been with Sun since 2002, and is responsible for driving standardization of Java technology relating to mobile devices. John holds a degree in mechanical engineering from Northwestern University in Evanston, Illinois, and an MBA from MIT Sloan School of Management in Cambridge, Massachusetts. He is a member of the expert group for the two Java Specification Requests (JSRs) currently defining the Mobile Service Architecture (MSA) within the Java Community Process, JSR 248 and JSR 249.

In this interview, John describes the MSA initiative, Sun's involvement in it, and the benefits he expects for manufacturers, operators, and developers. He also gives us his insights into the future of J2ME technology.

Qusay Mahmoud: As the Marketing Manager for the J2ME Platform, what is your role in the MSA initiative?

John Muhlner: I work on the marketing and business aspects of the JSRs. Recently this has included facilitating the development of the use cases and requirements for JSR 249. My focus has been on trying to make sure that we fulfill our objectives of creating the next-generation mobile platforms that meet customer requirements and lead to rapid adoption. In addition, Sun is creating the reference implementations (RIs) and technology compatibility kits (TCKs) for these two platforms, so I'm focused on keeping the expert group on schedule with the specification development, so we can keep the delivery of these components on track.

QM: Can you give us an overview of MSA?

JM: JSRs 248 and 249 are the next-generation mobile platforms. JSR 248 picks up where Java Technology for the Wireless Industry (JTWI) left off. It defines the architecture of the Connected Limited Device Configuration (CLDC) stack that is targeted at mass-market Java technology phones. Its goal is to provide a solid platform base with limited optionality, so Java developers can create applications that can be easily deployed on a wide number of handsets.

JSR 249 is focused on creating a new, advanced mobile platform based on the Connected Device Configuration (CDC) stack. This platform is targeted at high-end consumers and enterprise workers. We are in the process of collecting use cases and identifying requirements for this platform, so the specifics are still in process. It's clear from our initial work, however, that this platform should provide a more reliable and robust system, deliver a richer user experience, support current JTWI and Mobile Information Device Profile (MIDP) applications, and enable mobile enterprise applications.

QM: What is your definition of a mobile service?

JM: Have you seen the new dashboard widgets in Mac OS X? They provide users with updates on stocks, weather, flight status, package tracking, etc. These mini-applications are great examples of what could be delivered as a mobile service on a handset. I believe we will soon see these types of mobile services become prevalent from operators trying to provide compelling offerings to their subscribers in order to increase average revenue per unit.

QM: How does MSA relate to JTWI?

JM: JSR 248 is very closely related to JSR 185. MSA for CLDC is a continuation of JTWI. With only four component JSRs, you might call JTWI the baby brother of JSR 248, whose early draft release included 17 component JSRs. In 2003, JTWI provided a common or base platform that application developers could rely upon. This will also be true for JSR 248.

MSA for CDC, JSR 249, is a continuation of this evolutionary path. This platform will build on JSR 248 to deliver even greater functionality to application developers targeting more capable devices.

QM: How will MSA benefit mobile subscribers, developers, and companies such as carriers and manufacturers?

JM: Developers will have a consistent, feature-rich Java platform that they can count on from handset to handset. Consistency will allow them to focus on developing the next great application instead of spending time trying to figure out which JSRs are available on which handsets and potential differences between their implementations.

Operators and manufacturers will also benefit significantly from these new platforms. Manufacturers will have two well-defined, technology-rich specifications that will help them create implementations that will meet operators' requirements. With standard platforms, many more applications will be able to run on a wider number of handsets.

In addition, the new advanced mobile platform, JSR 249, will provide new market opportunities for both handset manufacturers and operators. As I mentioned before, MSA for CDC will make possible more sophisticated and customizable applications for both high-end consumers and, more importantly, the enterprise workforce. This will help drive more high-end mobile data services and handset sales.

QM: What is the timeline for the release of the two MSA specifications, TCKs, and RIs?

JM: The expert group's immediate focus is on getting MSA for CLDC out as quickly as possible. The target for completion is the end of 2005. For MSA for CDC, it is a bit less clear, as we're currently identifying the requirements. That said, I believe the completion target is the summer of 2006.

QM: When do you expect devices that support MSA for CLDC and MSA for CDC to become commercially available?

JM: As I mentioned earlier, we are trying to complete MSA for CLDC as quickly as possible, so that compliant devices will be available for the 2006 holiday season. Due to the difference in schedules, JSR 249 handsets will probably follow some six to nine months later.

QM: Where do you see J2ME technologies and mobile data services going in the next three years?

JM: I believe that the next few years are going to be very interesting. We will see continued success with CLDC handsets in the market, as well as huge growth in a new breed of wireless devices based on the new advanced mobile platform, MSA for CDC. With the adoption of JSR 249, we will see more and more companies extending their current enterprise applications to mobile handsets, and thereby empowering their mobile workforce. In addition, I believe that we will see operators offering more compelling mobile services like the ones I mentioned, and a steady increase in the market adoption of these services.

QM: Do you have any advice for developers of Java-based wireless applications?

JM: I'd like to invite mobile developers to take a look at the MSA specifications and provide feedback. Their input is extremely valuable in making sure that we end up with a high-quality specification that meets their requirements.

Qusay H. Mahmoud provides Java-related consulting and training services. He has published dozens of articles on Java technology, and is the author of Distributed Programming with Java (Manning Publications, 1999) and Learning Wireless Java (O'Reilly, 2002).