Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

I am a SE and EE developer plan to learn Android for ME

 
Rajkumar Katudia
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey Jeff,

congrats for launching the book.

Just wanted to know if the book brings out the difference between normal java (both SE and EE) development and Android development.

As far as I know and am aware of, there's no much difference between normal Java and Android development.

I mean things like memory management, application footprint general paradigm about threads and so on???...
 
Monu Tripathi
Rancher
Posts: 1369
1
Android Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SE and EE and plan to learn Android for ME? Really?
You might find the following thread interesting:
1. Android vs iPhone vs J2ME...
2. Android newbie
 
Jeff Friesen
author
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Rajkumar,

My book focuses on the Java language and foundational APIs (such as regular expressions and collections) that are part of Java SE and Android -- I only cover APIs that are part of both platforms, which restricts me to Java 1.5 because Android APIs are based on Java version 5. I'll follow this same practice with the six PDF-based chapters that I'm writing to supplement my book, and which will be freely available to download from my website over the next few months.

Despite similarity of language features and many APIs, there are significant differences between Java SE and Android development. For example, the concepts of application are very different in Java SE and Android. For example, a Java SE application has a class with a public static void main(String[] args) method. In contrast, an Android application consists of some combination of activities, services, broadcast receivers, and content providers -- there is no class with a main() method because there is no single entry point. Any component of the Android application can be started when requested by another application and when the component's application allows other applications to start it.

Another area of difference is threading. In Java SE, you would typically work with the low-level Threading API or the concurrency utilities (or perhaps some combination of the two). In Android, you typically work with special classes such as Looper, MessageQueue, and Handler.

All the best.

Jeff
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic