Rants And Ramblings About Mobile Technology
Anders Borg writing about the fun and crazy world of mobile and Internet service technologies.
You can also read the blog via Twitter or your phone via wap.abiro.com. See the left menu for more news.
Comments on blog entries are moderated, but I'm rather liberal as long as it's not blatant advertising.
For general comments, advertising and contribution queries, please use the feedback form.
Monday, February 05, 2007
Java ME CLDC/MIDP, the choice for mobile widget platforms
I read Java ME as middleware to Mobile Ajax? with interest, yet with some concern about the logic. This is not intended to flame Ajit's note. Rather it shows reality from a slightly different point of view.
To clarify the acronym mumbo jumbo: CLDC/MIDP is the configuration/profile combination of Java ME that's completely dominating on mobile phones. Java ME is Java Micro Edition, intended for smaller and/or mobile devices.
Regarding "rather curious development", about using CLDC/MIDP as middleware for widget platforms: Not at all...
What after-market application platform exists in most mainstream phones? CLDC/MIDP. 1.5 billion according to Sun.
What after-market application platform does most phones only have? Again, CLDC/MIDP. There are less than 200 million phones that run any other such platform. The only serious alternative is Symbian OS / Series 60 with 100 million phones.
If mFoundry instead would have gone embedded they would have had to convince phone manufacturers to integrate mojax despite no operator has requested it. Close to impossible (not even a giant like Adobe can convince them to integrate Flash Lite on all phones), and it takes a long time to get phones on the market, hence mFoundry would be outcompeted in a jiffy. Again an argument for CLDC/MIDP.
This same reasoning applies to other mobile widget platform providers.
Regarding "CTO and co-Founder of mFoundry (creator of mojax) counters this argument saying that it is too technical": It's strange to argue that it's too technical, and it indicates the CTO thereby agrees that it's not AJAX compatible. Hidden under this is of course that people think they understand what AJAX is and it's of course hyped, hence the value of using that term for describing mojax is very high, even if it's wrong. Marketing 101 ;).
See also my 2007, the year of mobile widgets.
To clarify the acronym mumbo jumbo: CLDC/MIDP is the configuration/profile combination of Java ME that's completely dominating on mobile phones. Java ME is Java Micro Edition, intended for smaller and/or mobile devices.
Regarding "rather curious development", about using CLDC/MIDP as middleware for widget platforms: Not at all...
What after-market application platform exists in most mainstream phones? CLDC/MIDP. 1.5 billion according to Sun.
What after-market application platform does most phones only have? Again, CLDC/MIDP. There are less than 200 million phones that run any other such platform. The only serious alternative is Symbian OS / Series 60 with 100 million phones.
If mFoundry instead would have gone embedded they would have had to convince phone manufacturers to integrate mojax despite no operator has requested it. Close to impossible (not even a giant like Adobe can convince them to integrate Flash Lite on all phones), and it takes a long time to get phones on the market, hence mFoundry would be outcompeted in a jiffy. Again an argument for CLDC/MIDP.
This same reasoning applies to other mobile widget platform providers.
Regarding "CTO and co-Founder of mFoundry (creator of mojax) counters this argument saying that it is too technical": It's strange to argue that it's too technical, and it indicates the CTO thereby agrees that it's not AJAX compatible. Hidden under this is of course that people think they understand what AJAX is and it's of course hyped, hence the value of using that term for describing mojax is very high, even if it's wrong. Marketing 101 ;).
See also my 2007, the year of mobile widgets.
