Jason Delport Home

Blog Feed Blog Feed

Paxmodept Website Paxmodept Website

Contact Information


Jason Delport

+44(0)7931445721

jason@paxmodept.com

Download vCard


Mobile Portal


~mobile.paxmodept.com~
QR Code

Blog Archive & Stats


MonthPosts
June 2010(2)
May 2010(1)
April 2010(4)
February 2010(1)
January 2010(2)
December 2009(1)
November 2009(3)
October 2009(3)
September 2009(7)
August 2009(1)
July 2009(2)
June 2009(4)
May 2009(7)
April 2009(5)
March 2009(10)
February 2009(10)
January 2009(19)
December 2008(11)
November 2008(16)
October 2008(28)
September 2008(7)
August 2008(19)
July 2008(17)
June 2008(13)
May 2008(11)
April 2008(11)
March 2008(18)
February 2008(17)
January 2008(19)
December 2007(8)
November 2007(29)
October 2007(38)
September 2007(30)
August 2007(50)
July 2007(46)
June 2007(38)
May 2007(20)
April 2007(16)
March 2007(35)
February 2007(28)
January 2007(36)
December 2006(26)
November 2006(42)
October 2006(39)
September 2006(26)
August 2006(16)
July 2006(4)
Total796


© 2010 Jason Delport

Fixing Java ME

I have been thinking about how to fix Java ME for some time. The one central idea that I coming back to is the need for an on-device application market place for Java ME applications. The iPhone and Android have proved this model works well for application distribution. I think this process needs to be driven by a device manufacturer or OS vendor but not by the network operators for obvious reasons.

Java ME devices already have something called a Java Application Manager (JAM) which is responsible for installing the midlet into the JVM sandbox. If correctly configured in the JAD file the JAM also reports to the application provider that the user has installed or un-installed the application. The iPhone and Android markets have both implemented similar features for tracking and analytical purposes.

So my idea is to re-write the JAM and make it a full-on application market place. For 3rd party remote application installations it would still function exactly the same as it does at the moment but it would have an new user interface that functions like the Android Market and let's users browse and install applications from a catalogue.

The catalogue would be administered by the device manufacturer or OS vendor and would require some type of application vetting (my preferred solution is no vetting but I'm being reasonable here). Although this vetting would be an annoyance to the developer it could be offset by giving applications provisioned through the catalogue interface unlimited API permissions (after warning the user during installation of course).

The revenue from commercial applications could be shared between the developer, the catalogue owner and the network operator. You have to have buy in from the network operators else this won't work.

Applications would need to be given first rate status on the device / operating system. This means that the JAM wouldn't install applications in some obscure folder hidden away in a sub menu as many currently do.

The improved JAM/JVM would have an automatic APN configuration feature so that connectivity is no longer an issue. This is simple to do. Motorola have had a midlet that does something similar for years.

These improvements wouldn't fix all of Java ME's problems but they would at least tackle some of the ones I mentioned in this blog post. One possible contention with this approach is that the application store would be Java ME specific. I'm not sure how the other runtime vendors would react to this. Probably not very well but that's a political and economic problem rather than a technical one.




~Comments~

C. Enrique Ortiz declares...

I agree w/ you that the lack of on-device app catalog/store etc. has hurt Java ME, and that Android and iPhone have proven the model, and the latter even a business model.

What are your thoughts on the JCP pushing for such a on-device mechanism to be part of the standard so it is guaranteed to be on all handsets on similar ways? Or, does it matter to make this piece consistent? I've my own opinion on this but would love to hear yours.

ceo

Date Wed, 04 Feb 2009 at 23:12:43

Andrew Ebling declares...

I think an on-device app store would a Good Thing (tm) for J2ME. However I feel it's only part of what J2ME is missing; even if independent developers like ourselves are given a route to market for J2ME applications, device fragmentation quickly rears it's ugly head. The cost involved of porting to a large enough selection of handsets is still likely to be a big issue.

Or do you think an on-device app store could make an app viable on just one or two popular handsets?

Date Thu, 05 Feb 2009 at 05:33:09

Jason declares...

Hi Guys,

Thanks for the comments guys. I think this is going to be a multi-post subject. I started with the least controversial aspects and I will get to the JCP and fragmentation in the next post.



Date Thu, 05 Feb 2009 at 10:48:22

~Add Comment~

Name
Email
Website
Website
Website
Comment (No HTML)
Human? Human?