wood burning stoves 2.0*
The moose likes Android and the fly likes Android vs. J2ME Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Mobile » Android
Bookmark "Android vs. J2ME" Watch "Android vs. J2ME" New topic
Author

Android vs. J2ME

Lanny Gilbert
Ranch Hand

Joined: Jun 11, 2002
Posts: 103
I know that they're quite different, but was wondering if a background in J2ME development would help or hinder learning Android?
Sai Hegde
security forum advocate
Ranch Hand

Joined: Oct 26, 2010
Posts: 199
    
    1

Android can be said to be a Google version of J2ME... with minor differences. Android might be a little more tightly integrated , while J2ME is far more liberal in its specifications for the developer and mobile device manufacturer. So any experience in developing J2ME apps would really be helpful in learning Android programming.
Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

Sai Hegde wrote:Android can be said to be a Google version of J2ME... with minor differences. Android might be a little more tightly integrated , while J2ME is far more liberal in its specifications for the developer and mobile device manufacturer. So any experience in developing J2ME apps would really be helpful in learning Android programming.

Minor differences?
I say Huge differences. Android is completely different beast from JME.
JME applications are monolithic while Android apps are more composite-able.
Sai Hegde
security forum advocate
Ranch Hand

Joined: Oct 26, 2010
Posts: 199
    
    1

Sorry, what I intended to say was significant differences.
Thanks for pointing that out, John. The only point that I was trying to drill in here was that it would be easier understanding Android if you really did work on J2ME apps anytime.
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41613
    
  55
The points where both overlap are the use of the core Java language, and the fact that they're both mobile environments. In that sense, knowledge of JME helps with Android. The APIs for using any handset features (like GPS, local storage, GUI, keyboard, etc.) are completely different.


Ping & DNS - my free Android networking tools app
Elchin Asgarli
Ranch Hand

Joined: Mar 08, 2010
Posts: 222

No way knowing one platform would hinter knowledge of other I think. You just have to be aware of differences, and start learning Android "from scratch". Learning curve should be easier though, if you have experience with similar platform.


Personal page, SCJP 6 with 91%, SCWCD 5 with 84%, OCMJD
Hauke Ingmar Schmidt
Rancher

Joined: Nov 18, 2008
Posts: 433
    
    2
APIs, build process, deployment... are all completely different.

But if you are good at designing an application (not to be misunderstood as "graphical design" alone) and delivering a great user experience, then the technical differences don't matter that much. So while experience with specific APIs will not help (and even hinder sometimes, if one wants to do things like in the other environment), the experience gained in designing for small screen, limited input methods, mobility, different life cycle compared to a desktop app and so on will help.

Luckily Android allows to use more of the standard Java library than J2ME did. This helps. But built on top of it are APIs that are totally new and different.
Dejan Stojadinovic
Greenhorn

Joined: Jul 13, 2009
Posts: 5
Just my 2 cents:

Previous experience with J2ME (or any other framework) wont hurt you in front of Android's learning curve.

Marko Gargenta
author
Greenhorn

Joined: Mar 27, 2011
Posts: 18

Actually, Android's Java is based on JavaSE (Standard Edition) and has nothing to do with JavaME (aka J2ME). So, knowing Java programming is important but knowing how JavaME works is not at all.
 
jQuery in Action, 2nd edition
 
subject: Android vs. J2ME