Presentation on theme: "Android Overview and Android Development Environment"— Presentation transcript:
1Android Overview and Android Development Environment CS378 - Mobile ComputingAndroid Overview and Android Development Environment
2What is Android? A software stack for mobile devices that includes An operating systemMiddlewareKey ApplicationsUses Linux to provide core system servicesSecurityMemory managementProcess managementPower managementHardware drivers
4Android FeaturesApplication framework enabling reuse and replacement of componentsDalvik virtual machine optimized for mobile devicesIntegrated browser based on the open source WebKit engineOptimized graphics powered by a custom 2D graphics library; 3D graphics based on the OpenGL ES 1.0 specification (hardware acceleration optional)SQLite for structured data storageMedia support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF)GSM Telephony (hardware dependent)Bluetooth, EDGE, 3G, and WiFi (hardware dependent)Camera, GPS, compass, and accelerometer (hardware dependent)Rich development environment including a device emulator, tools for debugging, memory and performance profiling, and a plugin for the Eclipse IDE
5A Short History Of Android 2001 Palm Kyocera 6035, combing PDA and phoneBlackberry smartphone released2005Google acquires startup Android Inc. to start Android platform.Work on Dalvik VM begins2007Open Handset Alliance announcedEarly look at SDKJune, iPhone released2008Google sponsors 1st Android Developer ChallengeT-Mobile G1 announced, released fallSDK 1.0 releasedAndroid released open source (Apache License)Android Dev Phone 1 releasedPro Android by Hashimi & Komatineni (2009)
6Short History cont. 2009 2010 SDK 1.5 (Cupcake) SDK 1.6 (Donut) New soft keyboard with “autocomplete” featureSDK 1.6 (Donut)Support Wide VGASDK 2.0/2.0.1/2.1 (Eclair)Revamped UI, browser2010Nexus One released to the publicSDK 2.2 (Froyo)Flash support, tetheringSDK 2.3 (Gingerbread)UI update, system-wide copy-paste
7Short History cont. 2011 SDK 3.0 (Honeycomb) for tablets only New UI for tablets, support multi-core processors, fragmentsSDK 3.1 and 3.2Hardware support and UI improvementsSDK 4.0 (Ice Cream Sandwich)For Q4, combination of Gingerbread and Honeycomb
8Short History cont.2012Android 4.1, "Jelly Bean" released in July2013Android 4.4, KitKat released October 31, 2013
9Device Distribution Jan 2012 Based on active devicesForward compatibleNot necessarily backward compatible1.5 Cupcake: 0.6%1.6 Donut: 1.1%2.1 Ecliar 8.5%2.2 Froyo 30.4%2.3 Gingerbread: 56%3.X Honeycomb 3.3%4.x Ice Cream Sand. 0.6%
12August 1, 2013Based on device visits to Google Play
13January 8, 2014Based on device visits to Google Play
14Devices and AppsEstimated 1 billion+ as of Sept activated devicesM, MEstimated 1.5M new activations per dayM2014 expected to ship 1 billion devices this yearGoogle Play (formerly Android Market)> 1,000,000 apps600,000 apps, June 20122/3 free, 1/3 paidApple App Store, >825,000 apps April 2013Apple and Google each claim 50,000,000,000 downloadsWhat's old is new - Mac vs. PC iPhone vs. Android???
22Setup Development Environment Install JDK 7Install Eclipse IDE (version Kepler)recommended "Eclipse Standard"Download and unpack the Android SDKInstall Android Development Tools (ADT) plugin for EclipseDetailed install instructions available on Android site
24Android Emulator or AVD Emulator is essential to testing app but is not a substitute for a real deviceEmulators are called Android Virtual Devices (AVDs)Android SDK and AVD Manager allows you to create AVDs that target any Android API levelAVD have configurable resolutions, RAM, SD cards, skins, and other hardware
29Emulator Basics Host computer’s keyboard works Host’s mouse acts as fingerUses host’s Internet connectionOther buttons work: Home, Menu, Back, Search, volume up and down, etc.Ctrl-F11 toggle landscape portraitAlt-Enter toggle full-screen modeMore info at
30Emulator Limitations That's why we need the dev phones and tablets! No support for placing or receiving actual phone callsSimulate phone calls (placed and received) through the emulator consoleNo support for USB connectionsNo support for camera/video capture (input)No support for device-attached headphonesNo support for determining connected stateNo support for determining battery charge level and AC charging stateNo support for determining SD card insert/ejectNo support for BluetoothNo support for simulating the accelerometerUse OpenIntents’s Sensor SimulatorThat's why we need the dev phones and tablets!
31Create an AVD using AVD Manager or use the command line
32Android Runtime: Dalvik VM Subset of Java developed by GoogleOptimized for mobile devices (better memory management, battery utilization, etc.)Dalvik runs .dex files that are compiled from .class filesIntroduces new librariesDoes not support some Java libraries like AWT, Swing
33Or From the Command Line C:\android-sdk-windows\tools>android create avd -n MyDevice -t android-8Android 2.2 is a basic Android platform.Do you wish to create a custom hardware profile [no]Created AVD 'MyDevice2' based on Android 2.2,with the following hardware config:hw.lcd.density=240vm.heapSize=24C:\android-sdk-windows\tools>emulator -avd MyDeviceDevice nameTarget platformLaunch deviceMore info:
34Applications Are Boxed By default, each app is run in its own Linux processProcess started when app’s code needs to be executedThreads can be started to handle time-consuming operationsEach process has its own Dalvik VMBy default, each app is assigned unique Linux IDPermissions are set so app’s files are only visible to that app
35Producing an Android App Java codeByte codejavacDalvik exedx.java.classaaptclasses.dexEvery application must have an AndroidManifest.xml file (with precisely that name) in its root directory. The manifest presents essential information about the application to the Android system, information the system must have before it can run any of the application's code. Among other things, the manifest does the following:It names the Java package for the application. The package name serves as a unique identifier for the application.It describes the components of the application — the activities, services, broadcast receivers, and content providers that the application is composed of. It names the classes that implement each of the components and publishes their capabilities (for example, which Intent messages they can handle). These declarations let the Android system know what the components are and under what conditions they can be launched.It determines which processes will host application components.It declares which permissions the application must have in order to access protected parts of the API and interact with other applications.It also declares the permissions that others are required to have in order to interact with the application's components.It lists the Instrumentation classes that provide profiling and other information as the application is running. These declarations are present in the manifest only while the application is being developed and tested; they're removed before the application is published.It declares the minimum level of the Android API that the application requires.It lists the libraries that the application must be linked against.Byte code<xml>Other .class filesAndroidManifest.xml.apk<str>Resources
36Other Dev Tools Android Debug Bridge Part of SDK command line tool to communicate with an emulator or connected Android devicecheck devices attached / runninginstall apk's, Android PacKage files, "executables", can find samples on places besides Google Play (security?)and more!
37Dalvik Debug Monitor Server DDMSdebugging tool"provides, screen capture on the device, thread and heap information on the device, logcat, process, and radio state information, incoming call and SMS spoofing, location data spoofing, and more."can interact with DDMS via Eclipse plugin, another view in Eclipse