Mobile Application Development is designed to teach students how to create Android applications. Upon completing the course, students will be able to develop mobile apps for user requirements, create apps using views, intents, and APIs to send SMS/emails, add menus, notifications and multimedia, store data using SQLite and Firebase, and create cross-platform apps using web technologies. The document then discusses the Android architecture including its core building blocks and tools for mobile app development.

1. 18ITT61
MOBILE APPLICATION
DEVELOPMENT

2. Preamble
• Mobile Application Development is designed
to impart the knowledge on application
development framework and tools for creating
android applications. It also equips the
students to design, implement and deploy
applications in mobile devices.

3. Course Outcomes

4. Course Outcomes
• Upon completion of the course, students will be able to:
1. Develop mobile application for the given user requirement using
android development framework and tools.
2. Create android applications using views, layouts, intents and SMS
Manager API to send SMS and E-mails.
3. Create menu, notifications and multimedia features for the
applications using android Notification Manager and Multimedia
APIs.
4. Create databases for the applications to store and retrieve data
using SQLite and Firebase.
5. Create mobile applications using standard web technologies such
as HTML5, CSS3 and JavaScript for android and iOS platforms.

5. UNIT 1 GETTING STARTED WITH
ANDROID
• Android – Evolution of Android - Android
architecture – Features- Core building blocks –
Anatomy of android application – Android
activity life cycle. Android Toast. Android
Widgets: Button – TextView – EditText –
RadioGroup -ToggleButton – CheckBox –
Spinner –DatePicker - Progress Bar –
DialogBox.

6. • Google ? • Android?

7. Introduction
 Android's mobile
operating system is based
on the Linux kernel and is
the world's best-selling
Smartphone.
 There are currently over
200,000 apps available for
Android that are made
accessible through the
Android Market, which is
the online app store run
by Google.
 The apps are primarily
written in Java.

8. Introduction
 The Android operating
system, including the
Linux kernel, contains
approximately 12
million lines of code.
 In this there are: 3
million lines of XML,
2.8 million lines of C,
2.1 million lines of
Java, and 1.75 million
lines of C++.

9. Background
• Android Inc. was founded in Palo
Alto, California in October, 2003
by Andy Rubin, Rich Miner, Nick
Sears, and Chris White.
• Their goal was to develop a
"smarter mobile device
that was more aware of its
owner's location and
preferences.”
• They operated secretively,
admitting only that they were
working on software for mobile
phones.

10. Background
 Google acquired Android
Inc. in August, 2005,
making Android Inc. a
wholly owned part of
Google Inc.
 Nick Sears was the only
original founder that did
not stay with Android Inc.
after the acquisition.
 At this point in time, many
assumed that Google was
planning to enter the
mobile phone market with
this move.

11. Background
 Once at Google, Rubin led a
team to develop a mobile
device platform powered by
the Linux kernel.
 Google marketed the
platform to handset makers
and carriers with the intent
of providing a flexible,
upgradable system.
 This caused speculation
about Google's intention to
enter the mobile
communications market to
build.

12. Background
 On October 21st, 2008,
Android 1.0 became
available to the public.
 "Today's announcement is
more ambitious than any
single 'Google Phone' that
the press has been
speculating about over the
past few weeks. Our vision is
that the powerful platform
we're unveiling will power
thousands of different phone
models.“
-Eric Schmidt, former
Google Chairman/CEO

13. Mobile Applications
• What are they?
– Any application that runs on a mobile device
• Types
– Web apps: run in a web browser
• HTML, JavaScript, Flash, server-side components, etc.
– Native: compiled binaries for the device
• Often make use of web services

14. TEXT & REFERENCE BOOKS
• TEXT BOOKS:
1. Reto Meier, “Professional Android 4 Application
Development”, Wiley India Pvt. Ltd, New Delhi - 2014.
2. John M. Wargo, “Apache Cordova API Cookbook”, Pearson
Education – 2015.
• REFERENCES:
1. ZiguardMedneiks, Laird Dornin G, Blake Meike and Masumi
Nakamura, “Programming Android”, O’Reily,2013.
2. Anubhav Pradhan and Anil V Deshpande, “Composing
Mobile Apps”, First Edition, Wiley India Pvt. Ltd, 2014.
3. Charlie Collins, Michael Galpin and Matthias Kappler,
“Android in Practice”, Manning Publications, 2012.

15. Unit -1
• Android is an open-source software stack that
includes the operating system, middleware,
and key mobile applications, along with a set
of API libraries for writing applications that
can shape the look, feel, and function of the
devices on which they run.

16. • The iPhone is a fully proprietary hardware and
software platform released by a single
company (Apple), whereas Android is an
open-source software stack produced and
supported by the Open Handset Alliance
(OHA) and designed to operate on any
compatible device.

17. Introduction
• Small, stylish, and versatile, modern mobile
devices have become powerful tools that
incorporate touch screens, cameras, media
players, Global Positioning System (GPS)
receivers, and Near Field Communications
(NFC) hardware.
• mobile phones have become about much
more than simply making calls.

18. Introduction
• Android has expanded beyond its roots as a
mobile phone operating system, providing a
consistent platform for application
development across an increasingly wide
range of hardware.
• In Android, native and third-party applications
are written with the same APIs and executed
on the same run time.

19. • APIs are mechanisms that enable two
software components to communicate with
each other using a set of definitions and
protocols. For example, the weather bureau's
software system contains daily weather data.
The weather app on your phone “talks” to
this system via APIs and shows you daily
weather updates on your phone.

20. Android is an ecosystem
• A free, open-source operating system for
embedded devices
• An open-source development platform for
creating applications
• Devices, particularly mobile phones, that
run the Android operating system and the
applications created for it

21. necessary and dependent parts
• A Compatibility Definition Document (CDD) and Compatibility Test Suite (CTS)
that describe the capabilities required for a device to support the software stack.
• A Linux operating system kernel that provides a low-level interface with the
hardware, memory management, and process control, all optimized for mobile
and embedded devices.
Open-source libraries for application development, including SQLite, WebKit,
OpenGL, and a media manager.
• A run time used to execute and host Android applications, including the Dalvik
Virtual Machine (VM) and the core libraries that provide Android-specific
functionality. The run time is designed to be small and efficient for use on mobile
devices.
• An application framework that agnostically exposes system services to the
application layer, including the window manager and location manager,
databases, telephony, and sensors.
• A user interface framework used to host and launch applications.
• A set of core pre-installed applications
• A software development kit (SDK) used to create applications, including the
related tools, plug-ins, and documentation.

22. features
• Access to Hardware, Including Camera, GPS, and Sensors
• Data Transfers Using Wi-Fi, Bluetooth, and NFC
• Maps, Geocoding, and Location-Based Services
• Background Services
• SQLite Database for Data Storage and Retrieval
• Shared Data and Inter-Application Communication
• Using Widgets and Live Wallpaper to Enhance the Home
Screen
• Extensive Media Support and 2D/3D Graphics
• Cloud to Device Messaging
• Optimized Memory and Process Management
• Like Java and .NET, Android uses its own run time and VM
to manage

23. INTRODUCING THE OPEN HANDSET
ALLIANCE
• The Open Handset Alliance (OHA) is a collection
of more than 80 technology companies, including
hardware manufacturers, mobile carriers,
software developers, semiconductor companies,
and commercialization companies.
• Of particular note are the prominent mobile
technology companies, including Samsung,
Motorola, HTC, T-Mobile, Vodafone, ARM, and
Qualcomm.

24. Tomorrow Work in Lab
• WHAT DOES ANDROID RUN ON?
• WHY DEVELOP FOR MOBILE?
• WHY DEVELOP FOR ANDROID?
• Factors Driving Android’s Adoption
• What Android Has That Other Platforms Don’t
Have?
• Eclipse and Android Studio (Android SDK)
• Steps to start

25. Evolution Of Android

26. INTRODUCING THE DEVELOPMENT
FRAMEWORK
• Android applications normally are written
using Java as the programming language but
executed by means of a custom VM called
Dalvik, rather than a traditional Java VM.

27. The Android SDK includes
• The Android APIs — Android API libraries that provide
developer access to the Android stack.
• Development tools —let you compile and debug your
applications
• The Android Virtual Device Manager and emulator —
The emulator runs within an Android Virtual Device
(AVD) that simulates a device hardware configuration.
• Full documentation
• Sample code
• Online support

28. Eclipse
• For those of you using Eclipse, Android has
released the Android Development Tools (ADT)
plugin that simplifies project creation and tightly
integrates Eclipse with the Android emulator and
the build and debugging tools.

29. Android Software Stack

30. The Dalvik Virtual Machine
• key elements of Android is the Dalvik VM
• Rather than using a traditional Java VM such as Java
ME, Android uses its own custom VM designed to
ensure that multiple instances run efficiently on a
single device
• The Dalvik VM uses the device’s underlying Linux kernel
to handle low-level functionality, including security,
threading, and process and memory management.
• It’s also possible to write C/C++ applications that run
closer to the underlying Linux OS.
• If the speed and efficiency of C/C++ is required for your
application, Android provides a native development kit
(NDK).

31. Dalvik
• All Android hardware and system service access is managed
using Dalvik as a middle tier.
• By using a VM to host application execution, developers
have an abstraction layer that ensures they should never
have to worry about a particular hardware implementation.
• The Dalvik VM executes Dalvik executable files, a format
optimized to ensure minimal memory footprint.
• You create .dex executables by transforming Java language
compiled classes using the tools supplied within the SDK.

32. DVM

33. Why Linux kernel for android?
• Linux is open-source, Google’s Android developers
could modify the Linux kernel to fit their needs.
• Linux gives the Android developers a pre-built,
already maintained operating system kernel to start
with so they don’t have to write their own kernel.
• Features:
⮚ Security
⮚ Memory management
⮚ Process management
⮚ Network stack

34. Core Building Blocks
• The core building blocks or fundamental
components of android are
– activities,
– views,
– intents,
– services,
– content providers,
– fragments and AndroidManifest.xml.