This new series starts with an introduction of Android designed specifically for Java developers just getting started with programming for mobile phones. Learn about the system of three-layer of versioning for Android (and find out why it's important), then Setup the development environment and build the first Android applications.
Survey on the Android programming environment and build the first application!
The recent increase in the use of mobile technology's amazing even for those active in the sector of this industry. The Chief Executive of Apple, Tim Cook has summed up the feelings in an interview in September 2012, as he discussed the success of the Apple iPad. 67 million iPad sales in two short years are the most significant thing. Tim Cook giving that number into the historical context when he noted that "we had to take 24 years to sell Mac computers, iPod music players for five years and more than three years for the new iPhone could reach that number." (See the resources section.)
If iOS is doing very well, the Android platform then grabs a Java-centric, also have kept the growth rate. According to a recent Google statement, 500 million Android devices activated since Android was released in 2008, and 1.3 million new devices are activated every day. According to the report, on the iTunes App Store of Apple and Google Play lists at least 1,400,000 applications and more than 60,000 million downloads of applications.
All the mobile devices that are enabled which means new opportunities for application sales and market applications for mobile phones was also developed. For developers who want to build mobile applications quickly, the Android is a great environment to start. If you can program in Java and other JVM languages, then you just need to focus on the study of how to build applications and deploy the application from there. Android's flexibility means that you can easily apply and experiment with new technologies like HTML5 and PhoneGap. And the omnipresent background — along with Google's Play — ensure that your production applications can be shared widely.
This first article in a new series for everyone is a profile about Android. Starting with an overview of the Android version of the system, then set up a development environment and begin construction of the first application.
Android devices are distributed are the growth rate faster than any other mobile platform, that helped Android becomes a great choice in the journey developing applications on your mobile phone, especially if you are a Java developer. A major drawback of the app is its fragmentation, which presents significant challenges for the test application. Practice shows that most of the developers of applications almost impossible to examine an application for every Android device to the operating system version. (In fact, do so in a way the main economic effect is the development of the service industry.) The following section of the article will look into the technical issues related to the export to many Android versions, plus the Java-based tools to test Android applications on mobile phones. Now, let's take the same survey through the Android version so that you can understand and develop applications on this platform.
The Android version
While the number of the version of the Android operating system version sequentially is 1.6, 2.1, 4.2 —, and etc. The releases also are named similar to the different items in a menu of fine desserts: Donut, Eclair, and Jelly Bean. When people refer to Jelly Bean means Android version 4.2. The Android version is also described at the API level, by integer ascending sequence. So, Android API level 17 mentioned the Android version 4.2, also known as the Jelly Bean.
Not only do you think this is not clear. However, the understanding is very important because the three methods set the version to be used interchangeably.
Most Java developers have to reverse their basic thoughts when it comes to supporting the different versions of Android. The Java platform has a reputation primarily as a server-side technology, where the communication with the user is typically a web page. If the site can be viewed, readers of the site that are not interested in the Java version that your application is running on it. However, with Android, your application source code again really safe when running on devices that you do not have the ability to control.
Many potential consumers to upgrade your application to a newer version with the version of the Android operating system when their old phones not be used anymore. Your decision in which the Android OS support is very important. While the latest version of Android is 4.2, about half the number of Android devices still supports Android 2.3. An application is written to the target for Android devices running 3.1 cannot run on a newer version as 4.2, nor run on the previous version as 2.3. So, it is the reason, if you want a wider distribution of your choice, it is better to be targeted to an older version of the operating system.
A downside of the aimed targets larger and more extensive distribution platform is newer always has new features that you want to apply to your application. If you are lucky, the Android development team will release a compatible library for you to use.