MOOC Seminar Report

on

Android Mobile Application Development

(CSE V Semester MOOC Seminar SCS-501)

2021-2022

Submitted to: Submitted by:

Mr. Akash Chauhan Mr. Ansh Riyal
Roll no: 1918240

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

GRAPHIC ERA HILL UNIVERSITY, DEHRADUN
CERTIFICATE
 (from Internal Co-ordinator of MOOC i.e. Class Coordinator)

Certified that Mr. Ansh Riyal (Roll No.- 1918240) have Completed

MOOC Seminar on the topic “Android Mobile Application

Development” from SWAYAM under the guidance of Professor Dr.

Himanshu N. Patel for fulfilment of CSE V Semester MOOC Seminar

(SCS-501) in Graphic Era Hill University, Dehradun. Students have

successfully Completed this Course as best of my knowledge.

Date: 12-11-2021

(Dr. Akash Chauhan)

Class Coordinator

CC-CSE-K-V- Sem

CSE Department

GEHU, Dehradun
CERTIFICATE
 ACKNOWLEDGMENT

I would like to express our gratitude to The Almighty , the most

Beneficent and the most Merciful, for Successful completion of MOOC

Seminar.(optional)

I wish to thank our parents for their continuing support and

encouragement. We also wish to thank them for providing us with the

opportunity to reach this far in our studies. (optional)

I would like to thank particularly my Supervisor Mr. XYZ for his

patience, support and encouragement throughout the completion of this Course.

I also acknowledge to my Class coordinator Dr. Akash Chauhan Sir who help

me to understand this course. At last but not the least I greatly indebted to all

other persons who directly or indirectly helped me during this course.

Mr. Ansh Riyal

Roll No.- 1918240

CSE-K-V-Sem

Session: 2020-2021

GEHU, Dehradun
 TABLE OF CONTENTS

-Week-1

Android Software Development, building a sample Android application

using Android Studio.

-Week-2

Android Project Structure, Android Manifest File and its common

settings.

-Week-3

Activities, Services, Intents.

-Week-4

Permissions, Application resources.

-Week-5

Basic User Interface Screen elements, Designing User Interfaces with

 Layouts.

-Week-6

Using Content Providers, Handling Persisting Data.

Prerequisites
● Android studio – Android Studio is the primary starting point for
constructing Android Applications
● Android device or Emulator – You will want either a physical Android
device, or the Android Emulator. Either way, reading through this
tutorial will aid you in understanding the basic connection points of
an Android application.
● Source code – Source code snippets include:
● AndroidManifest.xml snippet — This file is the application
deployment descriptor for Android applications.
● MainActivity.java — This implements an Android activity, the
primary entry point to the sample application of this tutorial.
● Activity_main.xml — This contains definitions for the visual
elements, or resources, for use by Android activities.
● AndroidManifest.xml complete — This lists a full
AndroidManfest.xml file, along with a description of each of the
important elements.
 Android terminology
● Android is an open source operating environment targeted for mobile
devices. Increasingly, Android is found in applications beyond
“smartphones”. These include wearable technology, appliances such
as projectors, speakers and televisions, and even automobiles.
● Emulator is a software tool representative of another system. Often,
an emulator is an environment that runs on a personal computer (PC,
Mac, Linux machine) that emulates another environment, such as a
mobile-computing device.
● Linux is an open source operating system kernel at the heart of many
computing platforms, including servers, desktop computers,
networking appliances, and mobile-computing devices. Android runs
on top of a Linux kernel.
● Android Run Time (ART) is an operating environment found in the
Android stack, which executes application code at runtime. The
Android Run Time replaces the “legacy” Dalvik Virtual Machine (VM)
from earlier versions of Android which operated in a manner similar to
a compliant Java VM.
 The Intent
Since its inception, Android has become a dominant force in the mobile
phone space. Its application model is unique in that applications are not
monolithic, menu-laden applications that require a great deal of clicking and
tapping to operate. Sure, there are menus and buttons to be tapped, but
Android has an innovative design element to its architecture known as an
intent.

An intent is a construct that permits an application to issue a request, which

is somewhat like a help-wanted sign. It might look like these:

● “Wanted: An application to help me look up a contact”

● “Wanted: An application to help me display this image”
● “Wanted: An application to perform this geographic-based search.”

In a similar and complementary fashion, applications can register

themselves as capable and interested in satisfying various requests or
intents. To follow the classified advertising paradigm, these might look like
this:

● “Available: Application ready and willing to present contact records in clear,

concise manner”
● “Available: Application ready and willing to perform a geographic search.”
Types of Android applications
● Activity
● Service
● Receiver
● ContentProvider

Activity apps
The activity is the most visible and prominent form of an Android
application. An activity presents the UI to an application, along with the
assistance of a class known as a view. The view class is implemented as
various UI elements, such as text boxes, labels, buttons, and other UIs
typical in computing platforms, mobile or otherwise. An application may
contain one or more activities. An activity is typically defined on a
one-to-one relationship with the screens found in an application.

An application moves from one activity to another by calling a method

known as startActivity() or startSubActivity(). The former method is used
when the application desires to simply “switch” to the new activity. The
latter is used when a synchronous call/response paradigm is desired. In
both cases, an intent is passed as an argument to the called method.

Service and receiver apps

Like other multi-tasked computing environments, there are applications
running “in the background” that perform various duties. Android calls
these types of applications services. The service is an Android application
that has no UI.

The receiver is an application component that receives requests to process

intents. Like the service, a receiver does not, in normal practice, have a UI
element. Receivers are typically registered in the AndroidManifest.xml file.

ContentProvider apps
The ContentProvider is the Android mechanism for data-store
abstraction. Let’s look at a specific type of data found on a mobile
device: the address book or contacts database. The address book
contains all the contacts and phone numbers a person might
require when using a mobile phone.

The ContentProvider is a mechanism to abstract access to a

particular data store. In many ways, the ContentProvider acts in the
role of a database server. Operations to read and write content to a
particular data store should be passed through an appropriate
ContentProvider, rather than accessing a file or database directly.
There may be both “clients” and “implementations” of the
ContentProvider

Android Views
Android views are the UI mechanism for putting things on the screen of
an Android device. The Android activity employs views to display UI
elements. Some of the more popular layout designs include:

● LinearVertical – Each subsequent element follows its predecessor

by flowing beneath it in a single column.
● LinearHorizontal – Each subsequent element follows its
predecessor by flowing to the right in a single row.
● Table – A series of rows and columns, similar to an HTML table.
Each cell can hold one view element.
● Constraint – Each element is “constrained” to an aspect of the
display such as the top or side of the screen or another element.
This layout aids in the construction of “responsive” applications
 and is the heir-apparent to the legacy Relative Layout introduced in
earlier versions of the Android platform.

---View elements consist of familiar UI elements, including:

● Button
● ImageView
● EditText to gather input with various filters such as Date or Numeric
● TextView (similar to a label, displays static text)
● CheckBox
● Radio Button
● Spinner (similar to a “drop-down” combo box)
● AutoComplete (EditText with auto text-complete feature)

REFERENCE

Developing your first Android application – IBM

Developer

Android App Development Fundamentals for

Beginners - GeeksforGeeks