Linked by Moochman on Mon 23rd Mar 2009 09:28 UTC
PDAs, Cellphones, Wireless Engadget's recent piece, "Mobile OS shootout", provides a relatively thorough comparison of current smartphone platforms and what they have going for them, mostly from a consumer gadget hound's point of view. They provide a bunch of nice comparative tables, among them the table "Third Party Development". From this table we learn that each platform has its own SDK, whereby some of the apps available are considered "native" - a distinction most non-developers won't be able to grok, since it depends on an understanding of runtime environments, etc. It's hard to say exactly who this table is targeting, actually; the developer or the end-user that the rest of the article seems to target. Let's just investigate some of the assumptions it makes.
Permalink for comment 354739
To read all comments associated with this story, please click here.
by Timmmm on Tue 24th Mar 2009 14:40 UTC in reply to "J2ME"
Member since:

Have you ever written a J2ME app? I'm guessing not. If you did you would find that it is extremely limited. Compared to a real native app it has the following limitations:

1. Java, hence slower, more power hungry and... well java is just bad.
2. Maximum app size (including all data) of around 1 MB on most phones.
3. Very simple GUI toolkit. Only supports simple (and ugly) forms. There are 3rd party alternatives but none are very good.
4. No filesystem access (unless you pay lots to get your app signed). No seek function.
5. Most other APIs also *require* your app to be signed.
6. Very small library missing lots of functionality.
7. No multitasking (at least on most phones).
8. You can't choose which buttons to assign to menu items - only give each item a priority and the phone chooses (usually in a stupid way).
9. Did I mention Java is shit?

J2ME is possibly the *worst* option. I wish Google would make a nice C++ API for Android.

Reply Parent Score: 1