It is one of the best Android seminar report.

1. Presented By:
Shivananda Rai
USN:4NM11MCA66
VIII Sem

2. 1. History of Android
2. Introduction
3. Architecture
4. Application development
5. Conclusion
Main topics

3. 1.History of Android
•Android Inc. was founded in Palo Alto, California, United States
•Developed by Andy Rubin, Rich Miner, Nick Sears and Cris White –
October 2003
•Google acquired Android Inc. August 2005
•The Open Handset Alliance, a group of several companies was formed-
November 2007
•Android Beta SDK Released November 2007

4. Versions of Android
Platform codename
ANDROID 1.5 CUPCAKE
ANDROID 1.6 DONUT
ANDROID 2.1 ECLAIR
ANDROID 2.2 FROYO
ANDROID 2.3 GINGER BREAD
ANDROID 3.0 HONEY COMB
ANDROID 4.0 ICECREAM SANDWITCH
ANDROID 4.2 JELLY BEAN
Coming up…….. KEY LIME PIE

5. 2. Introduction (1)
What is an Android?
Android is an open source mobile operating system that
combines and builds upon many different open source
projects.

6. 2. Introduction (2)
• We can write different apps to run on mobile phones
• Android is Lightweight and full featured
• Android is an Open Source Product, we can download SDK free
• A SDK is available to build, compile, test and debug user applications
• Android is developed by Google and later the Open Handset Alliance
(OHA)
• Allows writing managed code in the Java language
• Good framework based on Java

7. 2. Introduction (3)
What is the Open Handset Alliance (OHA)?
• It's a large group of companies.

8. 3.Architecture of Android

9. Linux Kernel
• Linux Version 2.6 as - h/w abstraction layer
• Proven driver model
• Security, Memory & Process Management
• Efficient computing resource management
• Stable and proven for mobile platform

10. LIBRARIES
• Written in C/C++ - System C Library(libc)
• Surface manager - composing different drawing screens
• Display/Graphics(SGL)-for 2D graphics
• OpenGLES – 3D Graphics Library
• Media Libraries
• SQLite –RDB engine-light weight
• WebKit–web browser engine–embeddable web view

11. Content provider
Enable applications access data from other applications ,sharing etc.
Resource Manager
Providing access to non-code resources
Notification Manager
Enables all applications to display alerts in the status bar
Activity Manager
Manages the lifecycle of applications
Application Framework

12. Android Runtime
Core libraries
• Includes a set of core libraries that provides most of the
functionality-JAVA
Dalvik VM
• Every Android application runs in its own process
• Uses its own bytecode, not Java bytecode.
• Dalvik VM executes files in the (.dex) format
• Device can run multiple VMs efficiently

13. At the top of Android Architecture we have all the applications,
which are used by the final user.
Application Layer

14. Application Building Blocks
Activity
User interface component, which corresponds to one screen at time.
Intent Receiver
Wakes up a predefined action through the external event.
Service
A task, which is done in the background.
Content Provider
A component, which allows sharing some of the data with other processes
and applications.
4. Application development (1)

15. Development requirements
•Java(jdk).
•Android SDK
•Eclipse IDE
4. Application development (2)

16. Android SDK
•Class Library
•Developer Tools
 dx – Dalvik Cross-Assembler
 aapt – Android Asset Packaging Tool
 adb – Android Debug Bridge
 ddms – Dalvik Debug Monitor Service
•Emulator and System Images
•Documentation and Sample Code
Eclipse IDE + ADT (Android Development Tools)
•Reduces Development and Testing Time
•Makes User Interface-Creation easier
•Makes Application Description Easier
4. Application development (3)

17. Supported Operating Systems
•Windows XP, Vista or later version.
•Mac OS X 10.5.8 or later(x86 only).
•Linux(tested on Ubuntu Linux, Lucid Lynx).
•On Ubuntu Linux, Version 8.04 or later is required.
4. Application development (4)

18. Programming Language(s)
•Java – officially supported
•C/C++ – also possible but not supported
4. Software development (3)

19. Open - Android allows you to access core mobile device functionality
through standard API calls.
All applications are equal - Android does not differentiate between the
phone's basic and third-party applications -- even the dialer or home screen
can be replaced.
Breaking down boundaries - Combine information from the web with data
on the phone -- such as contacts or geographic location -- to create new user
experiences.
Fast and easy development - The SDK contains what you need to build
and run Android applications, including a true device emulator and
advanced debugging tools.
Advantages

20. Security - Making source code available to everyone inevitably invites the
attention of black hat hackers.
Incompetence - Google’s dependence on hardware and carrier partners puts
the final product out of their control.
Disadvantages

21. We can only hope that the next versions of Android have overcome the
actual limitations and that the future possibilities became a reality.
The first Android based official devices may well be launched sometime in
the early half of 2009. Obviously, that's an age away when it comes to
handset design, and Android may well find itself competing against the
forthcoming Windows touch screen phones and maybe even the iPhone.
Conclusion