MODULE 1 ● Web browser - Based on the

open-source WebKit layout engine,

Android coupled with Chrome's V8
● an open source and Linux-based JavaScript engine supporting
Operating System for mobile devices HTML5 and CSS3.
such as smartphones and tablet ● Multi-touch - Android has native
computers. support for multi-touch which was
● Android was developed by the Open initially made available in handsets
Handset Alliance,led by Google, and such as the HTC Hero.
other companies. ● Multi-tasking - Users can jump from
● The first beta version of the one task to another and at the same
Android Software Development Kit time various applications can run
(SDK) was released by Google in simultaneously.
2007 whereas the first commercial ● Resizable widgets - Widgets are
version, Android 1.0, was released resizable, so users can expand them
in September 2008. to show more content or shrink them
● On June 27, 2012, at the Google I/O to save space.
conference, Google announced the ● Multi-Language - Supports single
next Android version, 4.1 direction and bi-directional text.
Jellybean. ● GCM - Google Cloud Messaging
Jellybean (GCM) is a service that lets
● an incremental update, with the developers send short message
primary aim of improving the user data to their users on Android
interface, both in terms of devices, without needing a
functionality and performance. proprietary sync solution.
● Wi-Fi Direct - A technology that lets
Features of Android apps discover and pair directly, over
● Beautiful UI - Android OS basic a high-bandwidth peer-to-peer
screen provides a beautiful and connection.
intuitive user interface. ● Android Beam - A popular
● Connectivity - GSM/EDGE, IDEN, NFC-based technology that lets
CDMA, EV-DO, UMTS, Bluetooth, users instantly share, just by
Wi-Fi, LTE, NFC and WiMAX. touching two NFC-enabled phones
● Storage together.
● SQLite, a lightweight relational Android Development Framework
database, is used for data storage ● Android applications normally are
purposes. written using the Java or Kotlin
● Media support - H.263, H.264, programming languages and are
MPEG-4 SP, AMR, AMR-WB, AAC, executed by means of the Android
HE-AAC, AAC 5.1,MP3, MIDI, Ogg Run Time (ART).
Vorbis, WAV, JPEG, PNG, GIF, and ● Each Android application runs in a
BMP. separate process,which stops and
● SMS and MMS kills processes as necessary to
manage resources.
 ● ART sits on top of a Linux kernel Android Architecture
that handles low-level hardware Android operating system
interaction, including drivers and ● a stack of software components
memory management. which is roughly divided into five
● A set of APIs provides access to all sections and four main layers
the underlying services, features, At the bottom of the layers is Linux
and hardware. ● Linux 3.6 with approximately 115
The Android API Libraries patches.
● The core of the SDK is the Android ● provides a level of abstraction
API libraries that provide developer between the device hardware and it
access to the Android stack. contains all the essential hardware
Development tools drivers like camera, keypad, display
● The SDK includes the Android etc.
Studio IDE and several other Kernel
development tools that let you ● handles all the things that Linux is
compile and debug your applications really good at such as networking
to turn Android source code into and a vast array of device drivers.
executable applications ● On top of Linux kernel there is a set
The Android Virtual Device Manager and of libraries including open-source
Emulator Web browser engineWebKit
● The Emulator runs within an Android SQLite database
Virtual Device (AVD) that simulates a ● useful repository for storage and
device hardware configuration. sharing of application data, libraries
Full documentation to play and record audio and video,
● The SDK includes extensive SSL libraries responsible for Internet
code-level reference information security etc.
detailing exactly what’s included in
each package and class and how to A summary of some key core Android
use them. libraries available to the Android
Sample code developer is as follows:
● The Android SDK includes a
selection of sample applications that android.app
demonstrate some of the ● Provides access to the application
possibilities available with Android, model and is the cornerstone of all
as well as simple programs that Android applications.
highlight how to use individual API android.content
features ● Facilitates content access,
Online support publishing and messaging between
● a hugely popular destination for applications and application
Android questions and a great place components.
to find answers to beginner android.database
questions. ● Used to access data published by
content providers and includes
 SQLite database management Application Framework layer
classes. ● provides many higher-level services
android.opengl to applications in the form of Java
● A Java interface to the OpenGL ES classes.
3D graphics rendering API. The Android framework includes the
android.os following key services:
● Provides applications with access to
standard operating system services Activity Manager
including messages, system ● Controls all aspects of the
services and inter-process application lifecycle and activity
communication. stack.
android.text Content Providers
● Used to render and manipulate text ● permits applications to publish and
on a device display. share information with different
android.view applications.
● The fundamental building blocks of Resource Manager
application user interfaces. ● Provides access to non-code
android.widget embedded resources such as
● A rich collection of pre-built user strings, color settings and user
interface components such as interface layouts.
buttons, labels, list views, layout Notifications Manager
managers, radio buttons etc. ● permits applications to show alerts
android.webkit and notifications to the user
● A set of classes intended to allow View System
web-browsing capabilities to be ● An extensible set of views used to
built into applications. create application user interfaces.
Android Libraries Components of an Android Application
● the third section of the architecture
and available on the second layer
from the bottom.
Dalvik Virtual Machine
● which is a kind of Java Virtual
Machine specially designed and
optimized for Android.
● The Dalvik VM makes use of Linux Additional Components
core features like memory
management and multi-threading,
which is intrinsic in the Java
language.
● The Dalvik VM enables every
Android application to run in its own
process, with its own instance of the
Dalvik virtual machine.
 Android version releases 2.On the first page enter an Application
Android system Name and your Company Domain.
● backward-compatible within the 3.select the form factors you wish to support
usual sense: an app engineered for within this project, as well as the minimum
an older release can run on a more Android platform version on which your
modern version of Android application will run.
ANDROID RELEASES 4.Select a template for your app’s main
Activity (user interface screen).
5.specify the class name for your initial
Activity, and specify the name for the XML
file that will be used to provide the Activity’s
UI layout.
6.When you’ve entered these details, click
Finish
ANDROID ANATOMY
The Main Activity File
● The main activity code is a Java file
MainActivity.java.
● This is the actual application file
which ultimately gets converted to a
Dalvik executable and runs your
application.
Manifest File
● you must declare all its components
in a manifest file called
AndroidManifest.xml which resides
SETTING UP ANDROID DEVELOPMENT at the root of the application project
Android Studio directory.
● purposeful by the Android team at ● This file works as an interface
Google to accelerate your between Android OS and your
development and assist you to build application.
high-quality apps. <application>...</application> tags
● provides tools for the testing, and ● enclosed the components related to
publication phases of the event the application. Attribute
method,and a unified development android:icon will point to the
atmosphere for making apps for all application icon available
Android devices. underres/drawable-hdpi.
Creating a New Android Project <activity> tag
1.From the welcome screen, choose the ● used to specify an activity and
“Start a brand-new Android Studio project” android:name attribute specifies
choice. as an alternative, among Android thefully qualified class name of the
Studio choose the File ➪ New ➪ New Activity subclass.
Project... menu item.
android:label
● attributes specifies a string to use as
the label for the activity. You can
specify multiple activities using
<activity> tags.
android.intent.action.MAIN
● indicate that this activity serves as
the entry point for the application.
android.intent.category.LAUNCHER
● indicate that the application can be
launched from the device's launcher
icon.
@string
● refers to the strings.xml file

Android application components:

<activity>elements for activities

<service> elements for services
<receiver> elements for broadcast
receivers
<provider> elements for content providers

Strings File
● The strings.xml file is located in the
res/values folder and it contains all
the text that your application uses.
R File
● The gen/com.example.helloworld/R
.java file is the glue between the
ANDROID ACTIVITIES
activity Java files like
● Android applications (or
MainActivity.java and the resources
simply “apps”) are software
like strings.xml.
programs that are installed
Layout File
and run natively on Android
● The activity_main.xml is a layout file
devices.
available in the res/layout directory
Android Activity Life Cycle
that is referenced by your application
when building its interface.
Different Resources folder
 ● The onStop method should be
used to pause or stop animations,
threads, Sensor listeners, GPS
lookups, Timers, Services, or other
processes that are used exclusively
to update the UI.
● The onRestart method is called
immediately prior to all but the first
call to onStart. Use it to implement
special processing that you want
done only when the Activity restarts
within its full lifetime.
The Active Lifetime
● The active lifetime starts with a call
to onResume and ends with a
Activity State corresponding call to onPause.
Active ● An active Activity is in the
● When an Activity is at the highest of foreground and is receiving user
the stack it is the visible, focused, input events.
foreground Activity that is receiving Process Priority
user input. Active processes (Top Priority)
Paused ● Active (foreground) processes have
● Activity is going to be visible but will application components the user is
not have focus; at this time it’s interacting with.
paused. Active processes include one or more of the
Stopped following components:
● When an Activity isn’t visible, it ● Activities in an active state—that is,
“stops.” those in the foreground responding
Inactive to user events.
● After an Activity has been killed, as ● You explore Activity states in greater
well as before it’s been launched, it’s detail later in this chapter.
inactive. ● Broadcast Receivers executing
● Activities have been removed from onReceive event handlers.
the Activity stack and need to be ● Services executing onStart,
restarted before they can be onCreate, or onDestroy event
displayed and used. handlers.
Activity Lifetimes Visible processes (High Priority)
The Full Lifetime ● Visible but inactive processes are
● the full lifetime of your Activity those hosting “visible” Activities or
occurs between the first call to foreground Services.
onCreate and when it is destroyed. Started background Service processes
The Visible Lifetime (Medium Priority)
● Activity's visible lifetimes are ● Processes hosting background
bounded between calls to onStart Services that have been started.
and onStop.
 Because these Services don’t
interact directly with the user, they
receive a slightly lower priority than
visible Activities or foreground
Services
Background processes (Low Priority)
● Processes hosting Activities that
aren’t visible and that don’t have any
running Services.