Comments on: What future for J2ME? http://blog.landspurg.net/what-future-for-j2me/ Technology, wireless, games...and more..... Wed, 08 Sep 2010 07:38:40 +0000 http://wordpress.org/?v=2.5 By: Haim. http://blog.landspurg.net/what-future-for-j2me/#comment-468578 Haim. Wed, 19 May 2010 18:54:57 +0000 http://blog.landspurg.net/?p=265#comment-468578 thanks for your post.. i wonder whether the game is indeed still open... java me has so many problems that i doubt if it ever gets it well known dominance we all knew during its early days. i have summarized the problems i see at http://www.lifemichael.com/en/?p=68. best, haim. thanks for your post.. i wonder whether the game is indeed still open… java me has so many problems that i doubt if it ever gets it well known dominance we all knew during its early days.

i have summarized the problems i see at http://www.lifemichael.com/en/?p=68.

best,
haim.

]]> By: abhishek http://blog.landspurg.net/what-future-for-j2me/#comment-425630 abhishek Sun, 19 Apr 2009 08:09:21 +0000 http://blog.landspurg.net/?p=265#comment-425630 FUTURE OF JAVA IS SO STRONG THAT NO ONE CAN IMAGINE BUT THE THING IS THAT THE VARIOUS BRANCHES OF JAVA IS GOING IN DEEP AND IN THIS SERIES ,,I DON'T THINK THAT J2ME STANDS FOR FUTURE OF JAVA IS SO STRONG THAT NO ONE CAN IMAGINE BUT THE THING IS THAT THE VARIOUS BRANCHES OF JAVA IS GOING IN DEEP AND IN THIS SERIES ,,I DON’T THINK THAT J2ME STANDS FOR

]]> By: Mo Agha http://blog.landspurg.net/what-future-for-j2me/#comment-403529 Mo Agha Wed, 25 Feb 2009 20:07:41 +0000 http://blog.landspurg.net/?p=265#comment-403529 I agree 100%. I worked in Porting J2ME to handsets and it was always the most problematic stage of a Game's Fanout. The fractious implementations of the KVM serve to cause massive headaches to J2ME developers. Developing for the iPhone, which only needs 1 single build makes the App's development lifecycle much smaller as you remove all the Porting out of the equation and also reduce QA costs, as you don't need to test for obscure cases that show up on MIDP handsets. J2ME is slowly dying, and MIDP3 is way too late to make an impact. Many Mobile Dev companies are dropping J2ME and focusing solely on smartphones (Blackberry, iPhone, WinMo, and Android Cupcake). This trend will only increase and serve to undermine future adoption of J2ME as content dwindles. J2ME is still a powerful deveopment platform but it is nothing compared to the iPhone's API's and Android's capabilities. I never understood why Manufacturers could never get something like drawRoundRect() to actually draw a proper Rounded Rectangle, or why some handsets would give the weirdest events when Paused/Resumed, or even not give any events at all! The java community really messed the MIDP implementation up as they only standardized the spec and not the KVM. Even with MIDP3, if there isn't a standard KVM then I expect more and more Mobile Dev companies to abandon J2ME altogether as it is too much work for very little revenue (especially when carriers are eating up to 70% of the On-Deck revenue). I agree 100%. I worked in Porting J2ME to handsets and it was always the most problematic stage of a Game’s Fanout. The fractious implementations of the KVM serve to cause massive headaches to J2ME developers. Developing for the iPhone, which only needs 1 single build makes the App’s development lifecycle much smaller as you remove all the Porting out of the equation and also reduce QA costs, as you don’t need to test for obscure cases that show up on MIDP handsets. J2ME is slowly dying, and MIDP3 is way too late to make an impact. Many Mobile Dev companies are dropping J2ME and focusing solely on smartphones (Blackberry, iPhone, WinMo, and Android Cupcake). This trend will only increase and serve to undermine future adoption of J2ME as content dwindles. J2ME is still a powerful deveopment platform but it is nothing compared to the iPhone’s API’s and Android’s capabilities. I never understood why Manufacturers could never get something like drawRoundRect() to actually draw a proper Rounded Rectangle, or why some handsets would give the weirdest events when Paused/Resumed, or even not give any events at all! The java community really messed the MIDP implementation up as they only standardized the spec and not the KVM. Even with MIDP3, if there isn’t a standard KVM then I expect more and more Mobile Dev companies to abandon J2ME altogether as it is too much work for very little revenue (especially when carriers are eating up to 70% of the On-Deck revenue).

]]> By: Frederic Thuard http://blog.landspurg.net/what-future-for-j2me/#comment-385480 Frederic Thuard Tue, 20 Jan 2009 17:35:12 +0000 http://blog.landspurg.net/?p=265#comment-385480 Tuomas, This is an excellent and visionary post. Despite the half billion download on Apple App store and forthcoming Blackberry and Android app stores as well as rebirth of Palm, J2ME stays the most widespread standard for branded apps in mobile handsets. The mobile world is only getting richer ... Tuomas, This is an excellent and visionary post. Despite the half billion download on Apple App store and forthcoming Blackberry and Android app stores as well as rebirth of Palm, J2ME stays the most widespread standard for branded apps in mobile handsets.
The mobile world is only getting richer …

]]> By: David Adams http://blog.landspurg.net/what-future-for-j2me/#comment-380813 David Adams Thu, 08 Jan 2009 14:38:29 +0000 http://blog.landspurg.net/?p=265#comment-380813 Excellent post and I agree 100%. I'm a former J2ME game developer who now exclusively works with smartphones. The difference in the quality of applications built to the native OS'es is night and day (no surprise), but that fact that the gap continues to widen is extremely sad. The power and capability of the average handset has long since passed the capacity of J2ME to take advantage of it. That's part of what's enabling the "alternate" JVM models like HipLogic's both from a technology and market opportunity perspective. When you have to spend 60%+ of your effort/budget in porting your app to fractious implementations of J2ME...PLUS the resulting effort is generally head-and-shoulders below the native OS equivalent...well, the result is what we have today. Excellent post and I agree 100%. I’m a former J2ME game developer who now exclusively works with smartphones. The difference in the quality of applications built to the native OS’es is night and day (no surprise), but that fact that the gap continues to widen is extremely sad. The power and capability of the average handset has long since passed the capacity of J2ME to take advantage of it. That’s part of what’s enabling the “alternate” JVM models like HipLogic’s both from a technology and market opportunity perspective. When you have to spend 60%+ of your effort/budget in porting your app to fractious implementations of J2ME…PLUS the resulting effort is generally head-and-shoulders below the native OS equivalent…well, the result is what we have today.

]]> By: jonathan http://blog.landspurg.net/what-future-for-j2me/#comment-375424 jonathan Fri, 26 Dec 2008 14:53:44 +0000 http://blog.landspurg.net/?p=265#comment-375424 i believe j2me will still be there but there will b more fragmentation with android coming to more phones. I can c j2me dying if every single one of us start using an ipone :P i believe j2me will still be there but there will b more fragmentation with android coming to more phones. I can c j2me dying if every single one of us start using an ipone :P

]]> By: Pascal http://blog.landspurg.net/what-future-for-j2me/#comment-374523 Pascal Wed, 24 Dec 2008 19:30:03 +0000 http://blog.landspurg.net/?p=265#comment-374523 Interesting post Thomas! I know your knowledge and involvment in J2ME so your analyse (which is not really optimistic for J2ME) is really interesting knowing this... Interesting post Thomas!
I know your knowledge and involvment in J2ME so your analyse (which is not really optimistic for J2ME) is really interesting knowing this…

]]> By: TomSoft http://blog.landspurg.net/what-future-for-j2me/#comment-374351 TomSoft Wed, 24 Dec 2008 11:41:32 +0000 http://blog.landspurg.net/?p=265#comment-374351 Allan, My point was not about the ability to create great applications in J2ME. As you know, we (Webwag) are aslso one of the big provider of powerfull application in J2ME. So trust me, I beilieve that J2me can be used now to create the best mobile applications. My point was more about evrything else: the discovery process, the payment, the ecosystem, etc... As usual, J2me is a good and mature technology now, but operators and manufacturers failed to bring the missing pieces. Allan,

My point was not about the ability to create great applications in J2ME. As you know, we (Webwag) are aslso one of the big provider of powerfull application in J2ME. So trust me, I beilieve that J2me can be used now to create the best mobile applications.

My point was more about evrything else: the discovery process, the payment, the ecosystem, etc… As usual, J2me is a good and mature technology now, but operators and manufacturers failed to bring the missing pieces.

]]> By: Allan MacKinnon http://blog.landspurg.net/what-future-for-j2me/#comment-374033 Allan MacKinnon Tue, 23 Dec 2008 21:12:27 +0000 http://blog.landspurg.net/?p=265#comment-374033 The irony is that J2ME devices are more powerful and bug-free than they've ever been. But plain MIDP is nearly featureless when compared to iPhone and Android OS's. Some JSR's are nice but the more exotic ones are either poorly designed or on too few devices to make a market. However, I believe that J2ME devices are more relevant than ever because the low to mid-range devices have become powerful enough -- screen, cpu, memory, camera and radio -- to build great applications. A good example is Nokia's announcement of six "emerging market" devices ranging from US$ 60-90. The $90 device has a QVGA display, camera and a fair amount of memory. Here's a link with some mobiles Nokia classifies as "entry level": http://www.nokia.com/A4405104 So what can you do on these devices? What are they capable of? Well, with some work and ingenuity you can build some slick applications that run well on them. Check this out: http://nemo.everypoint.com/wiki/index.php/Live_Stocks Go Java! The irony is that J2ME devices are more powerful and bug-free than they’ve ever been. But plain MIDP is nearly featureless when compared to iPhone and Android OS’s. Some JSR’s are nice but the more exotic ones are either poorly designed or on too few devices to make a market.

However, I believe that J2ME devices are more relevant than ever because the low to mid-range devices have become powerful enough — screen, cpu, memory, camera and radio — to build great applications.

A good example is Nokia’s announcement of six “emerging market” devices ranging from US$ 60-90. The $90 device has a QVGA display, camera and a fair amount of memory. Here’s a link with some mobiles Nokia classifies as “entry level”: http://www.nokia.com/A4405104

So what can you do on these devices? What are they capable of? Well, with some work and ingenuity you can build some slick applications that run well on them. Check this out:

http://nemo.everypoint.com/wiki/index.php/Live_Stocks

Go Java!

]]> By: DMY http://blog.landspurg.net/what-future-for-j2me/#comment-370459 DMY Fri, 19 Dec 2008 20:41:53 +0000 http://blog.landspurg.net/?p=265#comment-370459 maybe J2ME arrived to early on a too young market, with device manufacturers too powerful to just apply java specs. very single manufacturer designed their own J2ME implementation So with concentration, maybe fragmentation will decrease But I'm not optimistic on it. I think times have changed, new technologies (Apple, Android & other ones still to come) will make J2ME the prehistory on mobile applications maybe J2ME arrived to early
on a too young market, with device manufacturers too powerful to just apply java specs.
very single manufacturer designed their own J2ME implementation
So with concentration, maybe fragmentation will decrease
But I’m not optimistic on it.
I think times have changed, new technologies (Apple, Android & other ones still to come) will make J2ME the prehistory on mobile applications

]]> By: Ove Nordström http://blog.landspurg.net/what-future-for-j2me/#comment-370030 Ove Nordström Fri, 19 Dec 2008 08:35:01 +0000 http://blog.landspurg.net/?p=265#comment-370030 What about MIDP 3.0, do you know when it will be released? /ove What about MIDP 3.0, do you know when it will be released?
/ove

]]> By: Nicolai Wadsteom http://blog.landspurg.net/what-future-for-j2me/#comment-369057 Nicolai Wadsteom Thu, 18 Dec 2008 10:36:51 +0000 http://blog.landspurg.net/?p=265#comment-369057 What I have heard, from sources close to Sun is that Sun actually do have a JVM running on the iPhone. There are also more than one OpenSource port for this. The problem is Apple's license policy do not allow "interpreted code" such as java bytecode (even if it's JIT compiled into native at startup/run-time as is the case on the desktop and some MIDP2 phones, SonyEricsson for example). So only way to run the JVM's on the iPhone is by "jailbreaking it", which works great on the other hand! What I have heard, from sources close to Sun is that Sun actually do have a JVM running on the iPhone. There are also more than one OpenSource port for this.

The problem is Apple’s license policy do not allow “interpreted code” such as java bytecode (even if it’s JIT compiled into native at startup/run-time as is the case on the desktop and some MIDP2 phones, SonyEricsson for example). So only way to run the JVM’s on the iPhone is by “jailbreaking it”, which works great on the other hand!

]]> By: C. Enrique Ortiz http://blog.landspurg.net/what-future-for-j2me/#comment-368774 C. Enrique Ortiz Thu, 18 Dec 2008 02:44:11 +0000 http://blog.landspurg.net/?p=265#comment-368774 Yeah 2009 should be an interesting year for J2ME. about "Why Sun did not invest instead to provide an embeed VM into iPhone for instance?" that is because Apple controls the platform, and decides what goes into their Macs and iPhones (Java VM on Apple was written by Apple which is why it is always behind a couple of revs). ceo Yeah 2009 should be an interesting year for J2ME.

about “Why Sun did not invest instead to provide an embeed VM into iPhone for instance?”

that is because Apple controls the platform, and decides what goes into their Macs and iPhones (Java VM on Apple was written by Apple which is why it is always behind a couple of revs).

ceo

]]>