Introduction To first introduce the topic, Android is an incredibly popular mobile operating system. It has gained a huge following in recent years and a person can find Android enabled phones and tablets everywhere. According to Kerr (2013), as of November 2013 Android devices currently dominated the smartphone market and approximately 80% of all smartphones were Android devices. Personally, I currently use a Droid Razr running Android Jelly Bean (Android 4.1), which isn't the latest Android version, but is among the most popular right now. I also previously owned a Droid 1, which is what really set me on the Android path. Even though my usage of Android products doesn't represent a large market share, I'm still a firm believer in Android and the numbers really show that a lot more people are like-minded. However, as the popularity of Android grows more and more, it comes to the point of being effective as a programmer in the mobile market; you have to learn the basics of Android. The basics of Android programming begin with Java programming, which makes the transition quite simple for most programmers since Java is still a very popular language. This raises some questions, however. Now that I know where to start, where will this path lead and how is it different from regular Java? Are there many challenges in this transition from JRE to Android? Introduction to Java ProgrammingJava itself is a very powerful and flexible programming language. It has many features that make it a fantastic choice for programming. Some of the features include, but are not limited to:1. Portability: Code is compiled and run in a specific environment, not in an operating system2. No pointer arithmetic3. Garbage collection... half the paper... ster-based processing requires fewer instructions, but the trade-off is that these register instructions need to be longer. The benefit of using register-based processing is that Android applications require less memory to run efficiently. This is especially useful because of the compressed environment it has to work with. It's very helpful to learn the specifics of programming in standard Java and where it compares to Android-based Java. This is especially true if a programmer wants to delve into the mobile world. Realistically it wouldn't even be a difficult transition, learning to program Android applications would essentially be an extension of learning Java. The only reason I brought this up to learn Android was also stated in the introduction. Android is an incredibly popular mobile operating system. Not only that, but it is incredibly successful.