• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Android vs. J2ME

 
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I know that they're quite different, but was wondering if a background in J2ME development would help or hinder learning Android?
 
security forum advocate
Posts: 236
1
Android Flex Google App Engine
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
clojure forum advocate
Posts: 3479
Mac Objective C Clojure
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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
Posts: 236
1
Android Flex Google App Engine
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ranch Hand
Posts: 222
Google Web Toolkit Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Rancher
Posts: 436
2
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Just my 2 cents:

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

 
author
Posts: 18
Android Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic