Presented by: Asad Shaikh Roll no (30)

General Overview ANDROID

Open Handset Alliance Open Source ASAD Features Of Android Challenges Android Architecture Development Tools Anatomy of an Android Application Android Versions

Android is a comprehensive open source platform designed for mobile devices. It is championed by Google and owned by Open Handset Alliance. ASAD The goal of this alliance is to Accelerate innovation in mobile and offer consumers a richer, less expensive and better mobile experience.

Open source platform. The entire stack, from low level Linux modules all the way to native libraries & from the application framework to complete applications is totally open. Apache/MIT licences.

Android, Inc. was founded in Palo Alto, California, United States in October 2003 by Andy Rubin (co-founder of Danger), Rich Miner (co-founder of Wildfire Communications, Inc.), Nick Sears (once VP at T-Mobile) and Chris White (headed design and interface development at WebTV).

ASAD

Google acquired Android Inc. on August 17, 2005, making Android Inc. a wholly owned subsidiary of Google.

On November 5, 2007, the Open Handset Alliance, a consortium of several companies which include unveiled itself. The goal of the Open Handset Alliance is to develop open standards for mobile devices. On the same day, the Open Handset Alliance also unveiled its first product, Android, a mobile device platform built on the Linux kernel version 2.6.

General Overview ANDROID

Open Handset Alliance

Open Source ASAD Features Of Android Challenges Android Architecture Development Tools Anatomy of an Android Application Android Versions

ASAD

ASAD

ASAD

ASAD

ASAD

ASAD

General Overview ANDROID Open Handset Alliance

Open Source ASAD Features Of Android

Challenges Android Architecture Development Tools Anatomy of an Android Application Android Versions

ASAD

ASAD

ASAD

ASAD

ASAD

General Overview ANDROID Open Handset Alliance Open Source

ASAD Features Of Android

Challenges Android Architecture Development Tools Anatomy of an Android Application Android Versions

A simple and powerful SDK No licensing, distribution, or development fees Excellent documentation Thriving developer community

ASAD Development over many platform Linux, Mac OS, windows

Application framework enabling reuse and replacement of components Dalvik virtual machine optimized for mobile devices Integrated browser based on the open source WebKit engine Optimized 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 storage

ASAD

Media 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 Wi-Fi (hardware dependent)

Camera, GPS, compass, and accelerometer (hardware dependent)

General Overview ANDROID Open Handset Alliance Open Source Features Of Android ASAD

Challenges
Android Architecture Development Tools Anatomy of an Android Application Android Versions

CPU typically runs 500-600 Mhz RAM available to an App may only be a few megabytes Disk (flash) access is very slow Lifecycle - apps must pause/quit often, and restore to ASAD give the illusion that they are always running UI design o typical screen may be HVGA (320x480) o may be in portrait or landscape o very high DPI - small text may not be readable o touch resolution is very low (~25 pixel) Network access may be slow and (very) intermittent

General Overview ANDROID Open Handset Alliance Open Source Features Of Android ASAD Challenges

Android Architecture
Development Tools Anatomy of an Android Application Android Versions

ASAD

ASAD

ASAD

ASAD

ASAD

ASAD

Core Libraries Providing most of the functionality available in the core libraries of the Java language APIs Data Structures Utilities File Access Network Access Graphics Etc

Dalvik Virtual Machine Providing environment on which every Android application runs Each Android application runs in its own process, with its own instance of the Dalvik VM. Dalvik has been written such that a device can run multiple VMs efficiently. Register-based virtual machine

ASAD

ASAD

ASAD

Feature View System

Role

Content Provider
Resource Manager Notification Manager Activity Manager

ASAD Enabling applications to access data from other

applications or to share their own data

Used to build an application, including lists, grids, text boxes, buttons, and embedded web browser

Providing access to non-code resources (localized strings, graphics, and layout files) Enabling all applications to display customer alerts in the status bar Managing the lifecycle of applications and providing a common navigation backstack

ASAD

ASAD

General Overview ANDROID Open Handset Alliance Open Source Features Of Android ASAD Challenges Android Architecture

Development Tools
Anatomy of an Android Application Android Versions

DEVELOPMENT TOOLS
The Android SDK includes a variety of custom tools that help you develop mobile applications on the Android platform.Three of the most significant tools are: 1.Android Emulator ASAD -A virtual mobile device that runs on our computer -use to design, debug, and test our applications in an actual Android run-time environment. 2.Android Development Tools Plugin -for the Eclipse IDE adds powerful extensions to the Eclipse integrated environment. 3.Dalvik Debug Monitor Service (DDMS) -Integrated with Dalvik -this tool let us manage processes on an emulator and assists in debugging.

General Overview ANDROID Open Handset Alliance Open Source Features Of Android ASAD Challenges Android Architecture Development Tools

Anatomy of an Android Application

Android Versions

There are four building blocks to an Android application: Activity Intent Receiver Service Content Provider Not every application ASADneeds to have all four, but your application will be written with some combination of these.

Activity
An activity is usually a single screen in your application. Each activity is implemented as a single class that extends the Activity base class. ASAD Most applications consist of multiple screens. E.g Text message send 1) write the message. 2)choose contact etc Each of these screens would be implemented as an activity. Moving to another screen is accomplished by a starting a new activity

Intent
An Intent is a special Android class. Intent describe what an application wants done. Two most important parts of the intent 1) the action & 2)the data to act upon

ASAD

Intent Receiver
An IntentReceiver when you want code in your application to execute in reaction to an external event. for example, when the phone rings, or when the data network is available. Your application does not have to be running for its intent receivers to be called, the system will start your application, if necessary.

Service
A Service is code that is long-lived and runs without a UI. E.g. A media player playing songs from play list.

ASAD

Content Provider

A content provider is a class that implements a standard set of methods . Other applications store and retrieve the type of data with content provider It is useful if you want your application's data to be shared with other applications.

IMPORTANCE HIERARCHY
Foreground Process -required for what the user is currently doing Visible Process -holding an Activity - visible to the user onASAD screen but not in the foreground(on pause)

Service Process -holding a Service - not directly visible to the user- relevant tasks
Background Process -holding an Activity - not visible to the user - can kill at any time(stopped) Empty Process -doesn't hold any active application components(as a cache to improve start-up time)

General Overview ANDROID Open Handset Alliance Open Source Features Of Android ASAD Challenges Android Architecture Development Tools Anatomy of an Android Application

Android Versions

ASAD

Gingerbread Android 2.3x

Honeycomb Android 3x

IceCream Sandwich Jelly Bean Android 4.0x Android 4.1x

ASAD

ASAD

ASAD