0% found this document useful (0 votes)

115 views288 pages

Mobile Programming Basics

Uploaded by

limit less

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

115 views288 pages

Mobile Programming Basics

Uploaded by

limit less

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 288

Unit -1

Introduction to Mobile and Mobile Programming [2 Hrs]

Mobile Device and its Features

Mobile device is a general term for any handheld computer or smartphone. The term is
interchangeable with 'handheld,' 'handheld device,' and 'handheld computer.' Tablets, e-
readers, smartphones, PDAs and portable music players with smart capabilities are all mobile
devices. It is a computer which is small enough to hold and operate in the hand.

A mobile device has the following features:

• It’s portable.
• It’s personal.
• It’s with you almost all the time.
• It’s easy and fast to use.
• It has some kind of network connection.

i) Portable
A mobile device has to be portable, meaning that we can carry it without any special
considerations. We can take it to the gym, to the university, to work; we can carry it with us
everywhere, all the time.

ii) Personal
We’ve all heard it: “Don’t touch my phone!” A mobile device is absolutely personal. My mobile
is mine; it’s not property of the family, nor is it managed by the company who manufactured
it. I choose the ringtone, the visual theme, the games and applications installed, and which
calls I should accept. My wife has her own mobile device, and so do my kids. This personal
feature will be very important in our projects. You can browse a desktop website from any
computer—your familiar home PC, your computer at work, or even a desktop at a hotel or
Internet café—and numerous people may have access to those machines. However, you will
almost always browse a mobile website from the same device, and you are likely to be the
only person who uses that device.

iii) Companion
Your mobile device can be with you anytime! Even in the bathroom, you probably have your
mobile phone with you. You may forget to take lots of things with you from your home in the
morning, but you won’t forget your wallet, your keys, and your mobile device. The
opportunity to be with the user all the time, everywhere, is really amazing.

iv) Easy usage

A notebook (or even a netbook) is portable; it can be with you at any time and it has a network
connection, but if you want to use it, you need to sit down and perhaps find a table. Therefore,
it’s not a mobile device for the purposes of this book. A mobile device needs to be easy and
quick to use. I don’t want to wait two minutes for Windows to start; I don’t want to sit down.
If I’m walking downtown, I want to be able to find out when the next train will be departing
without having to stop.

1
v) Connected device
A mobile device should be able to connect to the Internet when you need it to. This can be a
little difficult sometimes, so we will differentiate between fully connected devices that can
connect any time in a couple of seconds and limited connected devices that usually can
connect to the network but sometimes cannot.
A classic iPod (non-Touch) doesn’t have a network connection, so it’s out of our list too, like
the notebooks.

Categories of Mobile Device

There are several categories of mobile devices. Devices can be categorized on the basis of
several parameters like size, speed, functionality, etc. Some of the categories are discussed
below:

i) Mobile Phones
Those devices which have call and SMS support can be categorized as mobile phones. We still
have mobile phones in some markets. They don’t have web browsers or connectivity, and
they don’t have any installation possibilities.
After some years, because of device recycling, such phones will probably not be on the market
anymore. The Nokia 1100 was the most widely distributed device in the world, with over 200
million sold since its launch in 2003. In terms of features, it offers nothing but an inbuilt
flashlight. The problem is that we can’t create web content for it. Some companies may
continue to make very low-end entry devices in the future, but hopefully Nokia and most
other vendors will stop creating this kind of device. Even newer, cheaper mobile devices now
have inbuilt browser support.
This is because the mobile ecosystem (vendors, carriers, integrators, and developers) wants
to offer services to users, and a browser is the entry point. For example, through its OVI
Services Nokia offers OVI Mail, an email service for non-Internet users in emerging markets.
Thanks to this service, many, many people who have never before had access to email can
gain that access, with a mobile device costing very low amount. This widespread solution
meets a real need for many people in emerging markets, like some countries in Africa and
Latin America.

ii) Low-end mobile devices

Low-end mobile devices have a great advantage: they have web support. They typically have
only a very basic browser, but this is the gross market. People who buy these kinds of devices
don’t tend to be heavy Internet users, but this may change quickly with the advent of social
networks and Web 2.0 services. If your friends can post pictures from their mobile devices,
you’ll probably want to do the same, so you may upgrade your phone whenever you can.
Nokia, Motorola, Kyocera, LG, Samsung, and Sony Ericsson have devices for this market. They
do not have touch support, have limited memory, and include only a very basic camera and a
basic music player.

iii) Mid-end mobile devices

This is the mass-market option for a good mobile web experience. Mid-end devices maintain
the balance between a good user experience and moderate cost. We can find a lot of devices
in this market sector.

2
In this category, devices typically offer a medium-sized screen, basic HTML-browser support,
sometimes 3G, a decent camera, a music player, games, and application support.
One of the key features of mid-end devices is the operating system (OS). They don’t have a
well-known OS; they have a proprietary one without any portability across vendors. Native
applications generally aren’t available publicly and some runtime, like Java ME, is the
preferred way to develop installed applications. The same vendors develop these devices as
the low-end devices.

iv) High-end mobile devices

Originally the same category as smartphones, high-end devices are generally non-multi touch
but have advanced features (like an accelerometer, a good camera, and Bluetooth) and good
web support (but not the best in the market). They are better than mid-end devices but not
on a par with smartphones.
The enhanced user experience on smartphones is one of the key differences. The other
difference is that high-end devices generally are not sold with flat Internet rates. The user can
get a flat-rate plan, but he’ll have to go out and find it himself.

v) Smartphones
This is the most difficult category to define. Why aren’t some mid-end and high-end devices
considered “smart” enough to be in this category? The definition of smart evolves every year.
Even the simplest mobile device on the market today would have been considered very smart
15 years ago.
A smartphone, as defined today, has a multitasking operating system, a full desktop browser,
Wireless LAN (WLAN, also known as Wi-Fi) and 3G connections, a music player, and several
of the following features:
• GPS (Global Positioning System) or A-GPS (Assisted Global Positioning System)
• Digital compass
• Video-capable camera
• TV out
• Bluetooth
• Touch support
• 3D video acceleration
• Accelerometer

vi) Non-phone devices

Those devices which doesn’t contains call and SMS feature falls into this category. For
example, Apple’s iPod Touch and iPad are devices in this category. They aren’t phones, but
they can be personal, are portable and easy to use, can be kept with you most of the time,
and have WLAN connections, so they fall into the category of limited connected devices. They
both also have a great mobile browser—the same one as the iPhone—so they will be in our
list of devices to be considered for development.

vii) Small Personal Object Technology (SPOTs)

This may sound like a sci-fi category, but every year sci-fi gets nearer to us. The only difference
between SPOTs and the other devices we’ve considered is their size: a SPOT may be a watch,

3
or even a pair of glasses. The LG GD910 in Figure 1-1 is a watch with 3G support. It’s on the
market now, so it’s not sci-fi.
“OK,” you may be thinking, “but are we really going to create a website for a one-inch
screen?” Maybe not. But we can create small widgets to update information presented to the
users, and this falls under the category of mobile web work.

viii) Tablets, netbooks, and notebooks

These devices have at minimum a nine-inch display, and they are more like desktops than
mobile devices. Some have desktop operating systems and desktop browsers, while others,
such as the iPad, have mobile software. If a device has a full operating system, you will need
to install antivirus protection and a firewall on it, so it won’t meet the easy usage criterion for
a mobile device. Also remember that you can’t use a netbook while walking.

History of Mobile Devices

Mobile phones, particularly the smartphones that have become our inseparable companions
today, are relatively new. However, the history of mobile phones goes back to 1908 when a
US Patent was issued in Kentucky for a wireless telephone.
Mobile phones were invented as early as the 1940s when engineers working at AT&T
developed cells for mobile phone base stations. The very first mobile phones were not really
mobile phones at all. They were two-way radios that allowed people like taxi drivers and the
emergency services to communicate. Instead of relying on base stations with separate cells
(and the signal being passed from one cell to another), the first mobile phone networks
involved one very powerful base station covering a much wider area.
Motorola, on 3 April 1973 were first company to mass produce the first handheld mobile
phone. These early mobile phones are often referred to as 0G mobile phones, or Zero
Generation mobile phones. Most phones today rely on 3G or 4G mobile technology.

4
Following are the landmarks in mobile history:
• 1926: The first successful mobile telephony service was offered to first class
passengers on the Deutsche Reichsbahn on the route between Berlin and Hamburg.
• 1946: The first calls were made on a car radiotelephone in Chicago. Due to the small
number of radio frequencies available, the service quickly reached capacity.
• 1956: The first automated mobile phone system for private vehicles launched in
Sweden. The device to install in the car used vacuum tube technology with rotary dial
and weighed 40Kg.
• 1969: The Nordic Mobile Telephone (NMT) Group was established. It included
engineers representing Sweden, Denmark, Norway and Finland. Its purpose was to
develop a mobile phone system that, unlike the systems being introduced in the US,
focused on accessibility.
• 1973: Dr Martin Cooper general manager at Motorola communications system
division made the first public mobile phone call on a device that weighed 1.1Kg.
• 1982: Engineers and administrators from eleven European countries gathered in
Stockholm to consider whether a Europe wide digital cellular phone system was
technically and politically possible. The group adopted the Nordic model of
cooperation and laid the foundation of an international standard.
• 1985: Comedian Ernie Wise made the first “public” mobile phone call in the UK from
outside the Dicken’s Pub in St Catherine’s dock to Vodafone’s HQ. He made the call in
full Dickensian coachman’s garb.
• 1987: The Technical specifications for the GSM standard are approved. Based on
digital technology, it focused on interoperability across national boundaries and
consequent different frequency bands, call quality and low costs.
• 1992: The world’s first ever SMS message was sent in the UK. Neil Papworth, aged 22
at the time was a developer for a telecom contractor tasked with developing a
messaging service for Vodafone. The text message read “Merry Christmas” and was
sent to Richard Jarvis, a director at Vodafone, who was enjoying his office Christmas
party.
• 1996/97: UK phone ownership stood at 16% of households. A decade later the figure
was 80%. The explosion in growth was in part driven the launch of the first pay as you
go, non-contract phone service, Vodafone Prepaid, in 1996.
• 1998: The first downloadable content sold to mobile phones was the ringtone,
launched by Finland's Radiolinja, laying the groundwork for an industry that would
eventually see the Crazy Frog ringtone rack up total earnings of half a billion dollars
and beat stadium-filling sob-rockers Coldplay to the number one spot in the UK charts.
• 1999: Emoji’s were invented by Shigetaka Kurita in Japan. Unlike their all-text
predecessor’s emoticons, emoji’s are pictures.
• 2000: The all-conquering Nokia 3310 crash landed on shop shelves. Naturally it was
unscathed and went on to sell 126 million units. Over in Japan, the first commercially
available camera phones The Sharp J-SH04, launched in November 2000 in Japan. The
only snag? you could only use it in Japan. Europe wouldn’t get its first camera phone
until the arrival of the Nokia 6750 in 2002.
• 2003: The 3G standard started to be adopted worldwide, kicking off the age of mobile
internet and paving the way for the rise of smartphones. Nepal was one of the first
countries in southern Asia to launch 3G services. One of Nepal’s first companies to
offer the service, Ncell, also covered Mount Everest with 3G.
5
• 2007: The iPhone debuted. Solely available on O2 at launch in the UK and priced at a
then eye-watering $499.
• 2008: The first Android phone turned up, in the form of the T-Mobile G1. Now dubbed
the O.G of Android phones, it was a long way from the high-end Android smartphones
we use today. Not least because it retained a physical keyboard and a BlackBerry-style
trackball for navigation. This year also saw the advent of both Apple’s App Store and
Android Market, later renamed Google Play Store.
• 2009: O2 publicly announced that it had successfully demonstrated a 4G connection
using six LTE masts in Slough, UK. The technology, which was supplied by Huawei,
achieved a peak downlink rate of 150Mbps.
• 2010: Samsung launched its first Galaxy S smartphone. Usurping former Android
giants, HTC, the Samsung Galaxy S range is still the most popular Android brand.
• 2017: The Nokia 3310 had a revival, sporting a fresh version equipped with basic web
browsing, a colourful screen and even a camera. Despite this, it still retained our
favourite features from the original 3310, including the iconic design, super-long
battery life and even an updated version of Snake.

Following are some of the popular mobile devices of their time:

S.N. Year Name of Device
1 1985 Motorola Dynatac 8000X
2 1992 Nokia 1011
3 1996 Motorola StarTAC
4 1997 The Hagenuk GlobalHandy
5 1998 Siemens S10
6 1998 Nokia 5110
7 1999 Nokia 7110
8 1999 Motorola Timeport
9 2000 Nokia 9210 Communicator
10 2000 Sharp J-SH04
11 2000 Nokia 3310
12 2003 Nokia 1100
13 2003 Blackberry 6210
14 2004 Motorola Razr V3

Brands, Models and Platforms

There are several brands, models and platforms currently available. Writing a book about
brands and models is very difficult. The market changes a lot every year. Some of the brands,
models and platforms are discussed below:

Apple
We are going to start with Apple, not because its devices are the best or because it has the
greatest market share, but because Apple has caused a revolution in the market. It changed
the way mobile devices are seen by users, and it is the reason why many developers (web or
not) have turned their attention to the mobile world.
Apple, a well-known desktop computer company, entered the mobile world with a
revolutionary device: the iPhone. Luckily for us, all of Apple’s devices are quite similar. They

6
have a multi touch screen, a 3.5ʺ screen size, WLAN connections, and Safari on iOS (formerly
Mobile Safari) as the browser.
Apple’s devices have a great feature: an operating system called iOS (formerly iPhone OS) that
is based on Mac OS X (a Unix-based desktop OS). Up to this writing, even the first version of
the iPhone can be upgraded to the latest operating system version. By default, the iPhone
and iPod Touch are charged using USB; when you charge your device, iTunes (the Apple
software for managing your device’s content and music) will detect automatically if an OS
update is available for your device, and you can install the update in minutes without any
technical skill needed. That is why today, for a mobile web developer, it’s more important to
know what OS version an Apple device has installed than which device it is. For those of us
whose aim is to create great web experiences for the iPhone, it doesn’t matter if the device
is an iPhone (the basic phone), an iPhone 3GS (S for speed, a device with more power and
speed), an iPhone 4 or an iPod Touch (like the iPhone without the phone). Even within each
device type, we have many generations.
Today, we can develop applications for iOS devices on only two platforms: using mobile web
techniques, and using the framework built using Objective-C or Swift.

Nokia
Nokia was the most popular brand and had the largest market share in mobile devices and
smartphones worldwide. Nokia has devices in all the mobile categories, from very low-end
devices to very high-end smartphones.
Nokia has the best support for developers, compared to all the other companies. Hundreds
of documents and a huge amount of sample code, ideas, and best practices for many
technologies, including technologies used for mobile web development are available on its
website for developers, Forum Nokia.
The bad news for developers is that hundreds of different Nokia devices are available today.
The good news is that they are very well organized by platform into different series, making
it easier for us to develop, test, and port our web applications to most of them.

BlackBerry
Research in Motion (RIM) is the Canadian manufacturer of the BlackBerry devices, mobile
devices focused on being “always connected” with push technologies that are primarily used
by corporate users who need to remain connected to intranets and corporate networks. RIM
calls all its devices “smartphones.”
RIM has few devices aimed at the mass market, so most of them have QWERTY keyboards
and aren’t designed for gaming. Many of them have proprietary input devices, like a scroll
wheel or a touchpad; some touch-enabled devices have also been launched in the last few
years. All BlackBerrys have the RIM OS, a proprietary operating system compatible with Java
ME with extensions, and, of course, a mobile browser. We can categorize the devices by
operating system version.
BlackBerry has become very popular in the corporate market because of its integration with
Exchange and other corporate servers. A BlackBerry user can browse the Internet via the
corporate Internet connection though a proxy, and many other manufacturers, such as Nokia,
LG, HTC, and Sony Ericsson, support the BlackBerry email client.

7
Samsung
Samsung has many devices on the market, most of which are divided into three different
series: native devices, Symbian devices, and Windows devices. At the end of 2009, Samsung
surprised the market with a new platform for the devices launching from 2010: Bada.
Samsung’s native devices are low- and mid-end mobile devices with a proprietary OS including
a browser and Java ME support, and typically a camera and a music player. Prior to 2010, the
smartphones and high-end devices were divided into two categories by operating system
Symbian and Windows Mobile each having its own set of features.
The latest devices on the market have touch support, with a UI layer installed over the
operating system. For newer devices, there is one feature that is available on all the three
platforms: Samsung Widgets. These are small applications created using mobile web
technologies that can operate on all the operating systems Samsung uses.
Starting in 2010, Samsung had delivered mobile devices with Bada, Android, and Windows
Phone.

Sony Ericsson
Ericsson built many mobile phones in the 1990s, and in 2001 it merged with Sony and created
the Sony Ericsson company. Today, Sony Ericsson produces a range of low and mid-end
devices and a couple of smartphones. Sony Ericsson, like Samsung, has decided to offer
devices with different operating systems. It offers low- and mid-end devices using a
proprietary Sony Ericsson operating system, as well as Windows Mobile devices, Android
devices, and Symbian devices.
Before 2009, the Symbian devices used UIQ as the UI layer for the operating system. Since
2009, there are Symbian Foundation devices using the same UI layer as Nokia’s and Samsung’s
devices. So, in terms of developing web applications for them, they are very similar. The
proprietary OS devices support Java ME and Flash Lite development (and also both at the
same time, thanks to a project called Capuchin), and they are divided in series according to
the Java ME APIs they support.
So, today we have Sony Ericsson devices from Java Platform 1 (JP-1) to Java Platform 8 (JP-8),
with each category differing in terms of the API support and the screen resolution. All the
devices have a camera, a music player and, of course, a web browser built in. The Symbian
Foundation–based devices are touch-enabled.

Motorola
For many years, Motorola was a leading manufacturer of low- and mid-end devices.
Motorola’s devices were the first mobile devices on the market, and the company pioneered
the clamshell design with the classic Motorola StarTac. Motorola’s mobile devices have
traditionally used either a proprietary operating system (like the well-known Motorola v3),
Symbian UIQ, Windows Mobile, or a Linux-based operating system the company created for
its devices. On the proprietary OS–based devices, Java ME and the browser were the only
supported development platforms. The Linux-based OS supports Java ME, web, and native
development.

8
The Windows-based Motorola devices, like the Motorola Q, which has a QWERTY keyboard,
are intended for the corporate market. The company also has some touch devices on the
market, all with a built-in camera and music player, and some mobile devices for the two-way
radio market, like the Nextel network. These devices have a proprietary OS and the model
names usually start with an “i.”
There are no series divisions in Motorola, unlike in the Nokia and Sony Ericsson lines, so we
will need to use other information (such as the browser used in each device) to test and make
decisions about the devices.

LG Mobile
LG Mobile has many low to high-end devices on the market today. Some are based on a
proprietary OS with Java ME, Flash, and web support. Some them support web widgets based
on WebKit. Most of the new one’s are based on Android.
LG participated in the creation of the Symbian Foundation and has two Symbian devices based
on the S60 platform, but later on it decided to support Android, which we can see many
Android-based LG devices currently.

HTC
HTC has become very popular in the mobile market since it created the first and second
Android devices in the world and the first Google phone, the Nexus One. But HTC doesn’t only
create Android devices; it also produces a lot of Windows Mobile ones. Many HTC devices
have touch support, and a key feature is that HTC tries to emulate the same user experience
on all its devices. We can think of HTC devices as either Android devices or Windows devices;
that’s the only distinction that’s needed.

9
This simplicity is reflected in the HTC website for developers: it only contains kernel files for
Android devices and links to the Android and Windows Mobile generic websites.

Android
Android is an open source, Linux-based operating system created and maintained by a group
of software and hardware companies and operators called the Open Handset Alliance. Google
mainly maintains it, so it is sometimes known as the “Google Mobile Operating System.” As
with any open source software, any manufacturer could theoretically remove all the Google-
specific stuff from the operating system before installing it on their devices. However, as of
this writing no vendor has done this, which is why every Android device is very “Google
friendly.”
Android is a software stack including a Linux-core, multitasking operating system based on
the concept of a virtual machine that executes bytecode, similar to .NET or JVM (Java Virtual
Machine). Google chose Java as the main language to compile (not compatible with Java ME)
with Web 2.0 users in mind. Android includes a full HTML browser based on WebKit and, in
fact, is very similar to the iPhone Safari browser, and all Android devices to date ship with
Google Maps, Google Calendar, and an email client and provide connections to many free
Google web services. It’s not an obligation, but as of today every Android device is touch-
based, and many of them have a QWERTY physical keyboard, GPS, a digital compass, and an
accelerometer.

Following is the list of android versions:

Version Name Version Number Initial Release Date Api Level

No version name 1.0 September 23, 2008 1
1.1 February 9, 2009 2
Cupcake 1.5 April 27, 2009 3
Donut 1.6 September 15, 2009 4
Eclair 2.0 – 2.1 October 26, 2009 5–7
Froyo 2.2 – 2.2.3 May 20, 2010 8
Gingerbread 2.3 – 2.3.7 December 6, 2010 9 – 10
Honeycomb 3.0 – 3.2.6 February 22, 2011 11 – 13
Ice Cream Sandwich 4.0 – 4.0.4 October 18, 2011 14 – 15
Jelly Bean 4.1 – 4.3.1 July 9, 2012 16 – 18
KitKat 4.4 – 4.4.4 October 31, 2013 19 – 20
Lollipop 5.0 – 5.1.1 November 12, 2014 21 – 22
Marshmallow 6.0 – 6.0.1 October 5, 2015 23
Nougat 7.0 – 7.1.2 August 22, 2016 24 – 25
Oreo 8.0 – 8.1 August 21, 2017 26 – 27
Pie 9.0 August 6, 2018 28
Android 10 10.0 September 3, 2019 29

(Source: Wikipedia)

10
Windows Mobile
One of the older mobile operating systems on the market is Windows Mobile (formerly
Windows CE for Pocket PC and Smartphones). For many years, its market included the well-
known Pocket PCs as Personal Digital Assistants (PDAs) without phone features. The “mobile
revolution” pushed Microsoft to create a smartphone version of its mobile operating system,
now called Windows Mobile, which is available in two flavours: The Professional (formerly
Pocket PC) and Smartphone editions.
Windows Mobile has its own unique features, like Android, and as developers we can consider
it as a platform without regard to who the device manufacturer is. Windows Mobile devices
are produced by HP, Toshiba, Motorola, Sony Ericsson, Samsung and Palm.

Palm
USRobotics bought Palm Computing Inc. in 1995. At the time, it was the pioneer launching
PDA devices. USRobotics later merged with 3Com, and as 3Com was dedicated to network
cards and accessories, Palm Inc. was created as a subsidiary. Palm Inc. was very successful,
and other manufacturers (including IBM) created other devices licensing its Palm OS. In 1998,
a couple of Palm’s directors left to create another company, HandSpring, which releases the
Treo devices to the market. Half PDA and half mobile phone, they can be considered the first
smartphones on the market.
A few years later, Palm decided to divide the company into a hardware manufacturer,
palmOne, and an operating system developer, PalmSource. This idea didn’t work out:
customers didn’t accept the palmOne trademark, so the company again acquired the Palm
trademark and the operating system became the Garnet OS. In the meantime, Palm acquired
HandSpring, so now we have Palm Treo devices.
In 2005, ACCESS (who also had other mobile technologies) acquired PalmSource and the
operating system. Suddenly, the new-old Palm company made a difficult decision: it started
to manufacture Treo devices with Windows Mobile, killing all hopes for the future of the
Garnet OS (formerly Palm OS).
The Treo series was the only type of Palm device that survived in the mobile world, and
BlackBerrys, the Nokia E Series, and other devices soon pushed Palm to the bottom of the
market. In response, Palm created another operating system for mobile devices, aimed at
being a web-oriented platform for iPhone-killer devices. webOS came to the market in 2009
with the first device, the Palm Pre. Other devices, such as the Palm Pixi, followed.
The company didn’t go so-well in the market, so in 2010, Palm was acquired by HP, who
promised evolution of webOS, so we should expect HP netbooks, tablets and more mobile
phones with this operating system in the following years.
Palm’s new webOS devices are touch and multitouch devices with a very smooth user
interface, excellent web support, and all the functions of a modern mobile device. The
operating system and all the device applications are web-based. That’s because any “native”
application developed for webOS is created using web technologies.

11
Symbian Foundation
Today there are many Symbian Foundation–based devices on the market (from Nokia, Sony
Ericsson, and Samsung), all with similar operating system features. The Symbian Foundation’s
OS allows us to develop applications using the native C++ framework, Java ME, Adobe Flash,
web applications, widgets using web technologies, Python, and Qt, a free C-based framework
owned by Nokia.
The open source OS is versioned as Symbian^1, Symbian^2, Symbian^3, etc. As with Android
and Windows Mobile devices, if we are talking about a Symbian device we know that it will
be very similar to all other Symbian devices, no matter which manufacturer created it.

Introduction to Mobile Programming

Mobile programming is a set of processes and procedures involved in writing software for
small, wireless computing devices. It is the act or process by which mobile apps are developed
for mobile devices, such as personal digital assistants, enterprise digital assistants or mobile
phones.
There are two dominant platforms in the modern smartphone market. One is the iOS platform
from Apple Inc. The iOS platform is the operating system that powers Apple's popular line of
iPhone smartphones. The second is Android from Google. The Android operating system is
used not only by Google devices but also by many other OEMs to build their own smartphones
and other smart devices. An original equipment manufacturer (OEM) is a company that
produces parts and equipment that may be marketed by another manufacturer.

There are several languages used for mobile programming. Languages like Java, Kotlin, C#,
Python etc. are popular for android platform and Objective-C, Swift etc. are popular languages
for iOS platform. Programmers can select any of the language of their choice for writing
mobile programs.

12
There are four major development approaches when building mobile applications:
• Native Mobile Applications
• Cross-Platform Native Mobile Applications
• Hybrid Mobile Applications
• Progressive Web Applications

Native Applications
Native mobile applications are written in the programming language and frameworks
provided by the platform owner and running directly on the operating system of the device
such as iOS and Android.

Cross-Platform Applications
Cross-platform native mobile applications can be written in variety of different programming
languages and frameworks, but they are compiled into a native application running directly
on the operating system of the device.

Hybrid-Web Applications
Hybrid mobile applications are built with standard web technologies - such as JavaScript, CSS,
and HTML5 - and they are bundled as app installation packages. Contrary to the native apps,
hybrid apps work on a 'web container' which provides a browser runtime and a bridge for
native device APIs via Apache Cordova.

Progressive Web Applications

WAs offer an alternative approach to traditional mobile app development by skipping app
store delivery and app installations. PWAs are web applications that utilize a set of browser
capabilities - such as working offline, running a background process, and adding a link to the
device home screen - to provide an 'app like' user experience.

Mobile Application Development Lifecycle

There are two interlinked core components of a mobile application: 1) the mobile application
“Front-End” that resides on the mobile device, and 2) the services “Back-End” that supports
the mobile front-end.

Figure 1-4. Mobile Application Development Life Cycle

13
• The mobile front-end is the visual and interactive part of the application the user
experiences. It usually resides on the device, or there is at least an icon representing
the app that is visible on the home screen or is pinned in the application catlog of the
device. The application can be downloaded from the platform app store, side-loaded
directly onto the device, or can be reached through the device’s browser.
• Regardless of what front-end platform or development methodology is being used,
delivering high-quality mobile applications that delight and retain users requires
reliable back-end services.
• Given the critical importance of back-end services for the success of the mobile
application, the developers have several important architectural decisions that they
must consider. These decisions include which services should they build themselves
and which third party services should they leverage, and then should they run and
maintain their own services or should they take advantage of 3rd party services.

Exercise

1. What do you mean by mobile device? Explain its features.

2. Explain different categories of mobile devices.
3. Explain about history of mobile device in detail.
4. Explain different brands, models and platforms of mobile devices in detail.
5. What do you mean by mobile programming? Explain life cycle of mobile application
development.
6. List and explain any five popular programming languages used for developing mobile
applications.
7. What are different mobile app development approaches? Explain in detail.

14
Unit -2
Introduction to Android Programming [4 Hrs]

Android Platform
Android is a mobile operating system currently developed by Google, based on the Linux
kernel and designed primarily for touchscreen mobile devices such as smartphones and
tablets. And as we said before, Android offers a unified approach to application development
for mobile devices.
Android is an open-source operating system named Android. Google has made the code for
all the low-level "stuff" as well as the needed middleware to power and use an electronic
device, and gave Android freely to anyone who wants to write code and build the operating
system from it. There is even a full application framework included, so third-party apps can
be built and installed, then made available for the user to run as they like.
The "proper" name for this is the Android Open Source Project, and this is what people mean
when they say things like Android is open and free. Android, in this iteration, is free for anyone
to use as they like.

History of Android
The history and versions of android are interesting to know. The code names of android
ranges from A to P currently, such as Aestro, Blender, Cupcake, Donut, Eclair, Froyo,
Gingerbread, Honeycomb, Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marhmallow,
Nougat, Oreo and Pie. Let's understand the android history in a sequence.
• Initially, Andy Rubin founded Android Incorporation in Palo Alto, California, United
States in October, 2003.
• In 17th August 2005, Google acquired android Incorporation. Since then, it is in the
subsidiary of Google Incorporation.
• The key employees of Android Incorporation are Andy Rubin, Rich Miner, Chris
White and Nick Sears.
• Originally intended for camera but shifted to smart phones later because of low
market for camera only.
• Android is the nick name of Andy Rubin given by co-workers because of his love to
robots.
• In 2007, Google announces the development of android OS.
• In 2008, HTC launched the first android mobile.

Environment Setup
In order to write an Android application, we are going to need a development environment.
Google has made a very useful tool for all Android Developers, the Android Studio. Android
Studio is the official IDE for Android development, and with a single download includes
everything you need to begin developing Android apps.
Included in the download kit, are the Software Development Kit (SDK), with all the Android
libraries we may need, and the infrastructure to download the many Android emulator
instances, so that we can initially run our application, without needing a real device. So, we
are going to download and install Android Studio.

1
Step 1 - First we have to have installed the Java Development Kit (JDK) from Oracle. If you do
not, please you should download the latest JDK from the https://www.oracle.com/. After
downloading JDK, please install it in your system.

Step 2 – After installing JDK, now it’s the time for you to setup environment variables. For this
procedure, right click This PC (My Computer) -> Properties -> Advanced System Settings ->
Environment Variables -> New. Now setup new environment variable as follows:

Figure 2-1. Setting up environment variable

Here, variable value must be the path where JDK is installed. Now click OK.

Step 3 – Now download the latest android studio and install in your system. After installation
following window appears in your computer screen.

Figure 2-2. First look of android studio after installation

Congratulations! Android Studio has been successfully installed in your computer system.

2
Creating an Android Project
The first step is to create an Android project. An Android project contains the files that make
up an application. To create a new project, open Android Studio and choose File -> New ->
New Project to open the new application wizard.

Figure 2-3. Creating a new Application

Notice that the package name you entered uses a “reverse DNS” convention in which the
domain name of your organization is reversed and suffixed with further identifiers. This
convention keeps package names unique and distinguishes applications from each other on
a device and on Google Play.
Click Next.

Figure 2-4. Setup device and SDK

3
Here we can select different devices and minimum SDK for or project. This setup configures
your application to work with different versions of Android. We are using default settings for
our project.
Android updates its tools several times a year, so your wizard may look slightly different from
what we are showing you. This is usually not a problem; the choices to make should stay
pretty much the same.
Click Next.

Figure 2-5. Creating a new Activity

4
Here we can see different templates for our Application. We can use these templates as per
the requirement. Since we are developing our first application, we start by adding no activity
in our project.
Click Finish.

Now, our project has just been created!

Laying Out the User Interface

After creating a new project, firstly we design user interface for our project. In Android project
we can design user interface using xml. In Android Studio, all xml files, images, audio, video,
animations, colours etc. that are used for designing the interface are kept inside res
(Resources) folder.
We need to create sub-folder named as layout to store different layout resource files. Layout
resource files are the pages that we design for our application.
Figure 2-6. Creating layout directory

5
Now select Resource type layout and Click OK.

Creating a new Layout Resource File

Now we are going to create a file where we add different design components like image,
button, label etc. In this example we are creating a new layout file containing a label with a
text “Hello World!”.

Figure 2-7. Adding new layout resource file

6
Now we need to write name of file. In this example I am giving name as first. For designing a
page, we can use different types of layout like Linear, Relative, Constraint etc. In this case, I
am using Linear Layout. We will discuss about different types of layout in coming chapters.
Click OK.
Note: Name of all the files under resource folder must be in lower case.

Adding Label with text “Hello World!”

Following code will add Label under Linear Layout in our page.
first.xml
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:orientation="vertical" android:layout_width="match_parent"
android:layout_height="match_parent">

</LinearLayout>

Our activity(page) layout defines two widgets: a LinearLayout and a TextView.

7
Widgets are the building blocks you use to compose a user interface. A widget can show text
or graphics, interact with the user, or arrange other widgets on the screen. Buttons, text input
controls, and check boxes are all types of widgets.

Figure 2-8. Widgets as seen on screen

The View Hierarchy

Your widgets exist in a hierarchy of View objects called the view hierarchy. To demonstrate
view hierarchy now I am going to create another layout file named as “second.xml” which
contains the following widgets:
• a vertical LinearLayout
• a TextView
• a horizontal LinearLayout
• two Buttons

Figure 2-9. Arrangement of widgets to demonstrate view hierarchy

8
second.xml

<?xml version="1.0" encoding="utf-8"?>

9
</LinearLayout>
</LinearLayout>

Figure 2-10. Hierarchical layout of widgets and attributes

The root element of this layout’s view hierarchy is a LinearLayout. As the root element, the
LinearLayout must specify the Android resource XML namespace at
http://schemas.android.com/ apk/res/android.
LinearLayout inherits from a subclass of View named ViewGroup. A ViewGroup is a widget
that contains and arranges other widgets. You use a LinearLayout when you want widgets
arranged in a single column or row. Other ViewGroup subclasses are FrameLayout,
TableLayout, and RelativeLayout.
When a widget is contained by a ViewGroup, that widget is said to be a child of the
ViewGroup. The root LinearLayout has two children: a TextView and another LinearLayout.
The child LinearLayout has two Button children of its own.

Widgets Attributes
Let’s discuss some of the attributes that you have used to configure your widgets:

android:layout_width and android:layout_height

The android:layout_width and android:layout_height attributes are required for almost
every type of widget. They are typically set to either match_parent or wrap_content:
• match_parent view will be as big as its parent

10
• wrap_content view will be as big as its contents require
(You may see fill_parent in some places. This deprecated value is equivalent to
match_parent.)

android:orientation
The android:orientation attribute on the two LinearLayout widgets determines whether their
children will appear vertically or horizontally. The root LinearLayout is vertical; its child
LinearLayout is horizontal.

android:text
The TextView and Button widgets have android:text attributes. This attribute tells the widget
what text to display. Notice that the values of these attributes are not literal strings. They are
references to string resources.
A string resource is a string that lives in a separate XML file called a strings file. You can give a
widget a hard-coded string, like android:text="True", but it is usually not a good idea. Placing
strings into a separate file and then referencing them is better.

Creating String Resources

Since string resources we are referencing in second.xml do not exist yet. Now, we need to fix
that by adding strings to string.xml file. Every project includes a default strings file named
strings.xml. In the package explorer, find the res/values directory, reveal its contents, and
open strings.xml.
Now add following lines of code in strings.xml file.

<resources>
<string name="app_name">My Application</string>
<string name="text_question">Android Studio is better than
Eclipse</string>
<string name="text_true">True</string>
<string name="text_false">False</string>
</resources>

Previewing the Layout

Your layout is now complete, and you can preview the layout in the preview section of
Android Studio. If your application is error free, following output will be displayed:

Figure 2-11. Layout Preview

11
Creating a New Class
Since for creating a page that can be displayed in an application we need layout resource file
for designing the page and a class file written using object oriented programming language
like Java, Kotlin, C# etc. that extends Activity class. In simple words, we can say that for
creating pages we need class file that extends Activity class. In a class file we link layout file
which we have designed and add events and other functionality to different widgets and
views that we have created in layout resource file. For creating class file we are using Java
programming language in our example.

Figure 2-12. Creating a new class file

12
Add following lines of code in newly created java file:

Second.java

package com.example.raazu.myapplication;

import android.app.Activity;
import android.os.Bundle;

public class Second extends Activity{

@Override
public void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.second);
}
}

This file has one Activity methods: onCreate(Bundle).

The onCreate(Bundle) method is called when an instance of the activity subclass is created.
When an activity is created, it needs a user interface to manage. To get the activity its user
interface, you call the following Activity method:
public void setContentView(int layoutResID)

This method inflates a layout and puts it on screen. When a layout is inflated, each widget in
the layout file is instantiated as defined by its attributes. You specify which layout to inflate
by passing in the layout’s resource ID.

Resource and Resource ID’s

A layout is a resource. A resource is a piece of your application that is not code – things like
image files, audio files, and XML files.
Resources for your project live in a subdirectory of the res directory. In the package explorer,
you can see that second.xml lives in res/layout/. Your strings file, which contains string
resources, lives in res/values/.
To access a resource in code, you use its resource ID. The resource ID for your layout is
R.layout.second. Your strings also have resource IDs. You have not yet referred to a string in
code, but if you did, it would look like this:
setTitle(R.string.app_name);

You can get ID’s of your resources inside R.java file.

13
Setting Up the Project
Now this is a final step to configure before running your application. Add your newly created
activity in AndroidMainfest.xml file. Following lines of code will add and configure your
activity to android manifest.

AndroidManifest.xml

</application>
</manifest>

14
The manifest file describes essential information about your app to the Android build tools,
the Android operating system, and Google Play.

Among many other things, the manifest file is required to declare the following:
• The app's package name, which usually matches your code's namespace. The Android
build tools use this to determine the location of code entities when building your
project. When packaging the app, the build tools replace this value with the
application ID from the Gradle build files, which is used as the unique app identifier
on the system and on Google Play.
• The components of the app, which include all activities, services, broadcast receivers,
and content providers. Each component must define basic properties such as the
name of its Kotlin or Java class. It can also declare capabilities such as which device
configurations it can handle, and intent filters that describe how the component can
be started.
• The permissions that the app needs in order to access protected parts of the system
or other apps. It also declares any permissions that other apps must have if they want
to access content from this app.
• The hardware and software features the app requires, which affects which devices can
install the app from Google Play.

Intent filters
App activities, services, and broadcast receivers are activated by intents. An intent is a
message defined by an Intent object that describes an action to perform, including the data
to be acted upon, the category of component that should perform the action, and other
instructions.
When an app issues an intent to the system, the system locates an app component that can
handle the intent based on intent filter declarations in each app's manifest file. The system
launches an instance of the matching component and passes the Intent object to that
component. If more than one app can handle the intent, then the user can select which app
to use.
An app component can have any number of intent filters (defined with the <intent-filter>
element), each one describing a different capability of that component.
If activity is defined with <intent-filter> element in manifest file than that activity will be
launched as the first activity of application.

Running on the Emulator

To run an Android application, you need a device – either a hardware device or a virtual
device. Virtual devices are powered by the Android emulator, which ships with the developer
tools.
An Android Virtual Device (AVD) is a configuration that defines the characteristics of an
Android phone, tablet, Wear OS, Android TV, or Automotive OS device that you want to
simulate in the Android Emulator. The AVD Manager is an interface you can launch from
Android Studio that helps you create and manage AVDs.

15
1. To open the AVD Manager, do one of the following:
• Select Tools > Android > AVD Manager.
• Click AVD Manager in the toolbar.

Figure 2-13. Opening AVD Manager

2. Click Create Virtual Device, at the bottom of the AVD Manager dialog.
The Select Hardware page appears.

Figure 2-14. Selecting the Hardware

16
3. Select a hardware profile, and then click Next.
If you don't see the hardware profile you want, you can create or import a hardware
profile.
The System Image page appears.

Figure 2-15. Configuring System Image

4. Select the system image for a particular API level, and then click Next.
• The Recommended tab lists recommended system images. The other tabs
include a more complete list. The right pane describes the selected system
image. x86 images run the fastest in the emulator.
• If you see Download next to the system image, you need to click it to
download the system image. You must be connected to the internet to
download it.

17
Figure 2-16. Verifying Configuration

5. The Verify Configuration page appears.

Change AVD properties as needed, and then click Finish.

Now your AVD has been configured successfully.

Following are the steps used to run your application on emulator:

1. Click Run App from toolbar.

Figure 2-17. Running Application

2. Following screen will appear. Choose your virtual device from the list and press OK
button.

18
Figure 2-18. Selecting Deployment Device

3. Now your app will start running and after some time following output will be displayed
in your emulator.

19
Figure 2-19. Displaying output in emulator

Exercise

1. What is android platform? Explain about history of android platform in detail.

2. List and explain different versions of android in detail.
3. How we can setup environment for android? Explain.
4. What do you mean by view hierarchy? Explain with the help of suitable example.
5. Define widget. Explain different widget attributes with example.
6. How can we create string resources? Explain with the help of suitable example.
7. Write a set of codes for creating activity. Also link xml file “activity_main.xml” to this
activity.
8. Explain about manifest file. How can we add activity in manifest? Explain with
example.
9. What is the role of intent-filter for any activity? Explain.
10. Explain the procedure for creating an AVD. Also write steps for running application on
Emulator.

20
Unit -3
Designing the User Interface [5 Hrs]

Android Layout Types

A layout defines the structure for a user interface in your app, such as in an activity. All
elements in the layout are built using a hierarchy of View and ViewGroup objects. A View
usually draws something the user can see and interact with. Whereas a ViewGroup is an
invisible container that defines the layout structure for View and other ViewGroup objects,
as shown in figure.

Figure 3-1. Illustration of a view hierarchy, which defines a UI layout

The View objects are usually called "widgets" and can be one of many subclasses, such as
Button or TextView. The ViewGroup objects are usually called "layouts" can be one of many
types that provide a different layout structure, such as LinearLayout or ConstraintLayout .

You can declare a layout in two ways:

• Declare UI elements in XML. Android provides a straightforward XML vocabulary
that corresponds to the View classes and subclasses, such as those for widgets and
layouts. You can also use Android Studio's Layout Editor to build your XML layout
using a drag-and-drop interface.
• Instantiate layout elements at runtime. Your app can create View and ViewGroup
objects (and manipulate their properties) programmatically.

Following are the different types of layout used for designing the User Interface.

LinearLayout
LinearLayout is a view group that aligns all children in a single direction, vertically or
horizontally. You can specify the layout direction with the android:orientation attribute.

1
Figure 3-2. Representation of LinearLayout

All children of a LinearLayout are stacked one after the other, so a vertical list will only have
one child per row, no matter how wide they are, and a horizontal list will only be one row
high (the height of the tallest child, plus padding). A LinearLayout respects margins
between children and the gravity (right, center, or left alignment) of each child.

Following code snippet will demonstrate LinearLayout.

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

Above code will produce following output.

2
Figure 3-3. Output produced for LinearLayout

Following are some attributes used with LinearLayout:

android:baselineAligned When set to false, prevents the layout from aligning its
children's baselines.
android:baselineAlignedChildIndex When a linear layout is part of another layout that is
baseline aligned, it can specify which of its children to
baseline align to (that is, which child TextView).
android:divider Drawable to use as a vertical divider between buttons.
android:gravity Specifies how an object should position its content, on
both the X and Y axes, within its own bounds.
android:measureWithLargestChild When set to true, all children with a weight will be
considered having the minimum size of the largest child.
android:orientation Should the layout be a column or a row? Use "horizontal"
for a row, "vertical" for a column.
android:weightSum Defines the maximum weight sum.

Layout Weight
LinearLayout also supports assigning a weight to individual children with the
android:layout_weight attribute. This attribute assigns an "importance" value to a view in
terms of how much space it should occupy on the screen. A larger weight value allows it to
expand to fill any remaining space in the parent view. Child views can specify a weight

3
value, and then any remaining space in the view group is assigned to children in the
proportion of their declared weight. Default weight is zero.

Equal distribution
To create a linear layout in which each child uses the same amount of space on the screen,
set the android:layout_height of each view to "0dp" (for a vertical layout) or the
android:layout_width of each view to "0dp" (for a horizontal layout). Then set the
android:layout_weight of each view to "1".

Unequal distribution
You can also create linear layouts where the child elements use different amounts of space
on the screen:
• If there are three text fields and two of them declare a weight of 1, while the other
is given no weight, the third text field without weight doesn't grow. Instead, this
third text field occupies only the area required by its content. The other two text
fields, on the other hand, expand equally to fill the space remaining after all three
fields are measured.
• If there are three text fields and two of them declare a weight of 1, while the third
field is then given a weight of 2 (instead of 0), then it's now declared more
important than both the others, so it gets half the total remaining space, while the
first two share the rest equally.

Following code snippet demonstrate layout_weight attribute. Here we are creating two
TextViews. First TextView have weight equal to 2 and Second TextView have weight equal
to 1. Total weight of LinearLayout is 3.

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

Above code will produce following output:

4
Figure 3-4. Output demonstrating layout_weight attribute

RelativeLayout
RelativeLayout is a view group that displays child views in relative positions. The position
of each view can be specified as relative to sibling elements (such as to the left-of or below
another view) or in positions relative to the parent RelativeLayout area (such as aligned to
the bottom, left or center).

Figure 3-5. Representation of RelativeLayout

5
A RelativeLayout is a very powerful utility for designing a user interface because it can
eliminate nested view groups and keep your layout hierarchy flat, which improves
performance. If you find yourself using several nested LinearLayout groups, you may be
able to replace them with a single RelativeLayout.

Following are some attributes used with RelativeLayout:

android:layout_above Positions the bottom edge of this view above

the given anchor view ID.
android:layout_alignBaseline Positions the baseline of this view on the
baseline of the given anchor view ID.
android:layout_alignBottom Makes the bottom edge of this view match the
bottom edge of the given anchor view ID.
android:layout_alignEnd Makes the end edge of this view match the end
edge of the given anchor view ID.
android:layout_alignLeft Makes the left edge of this view match the left
edge of the given anchor view ID.
android:layout_alignParentBottom If true, makes the bottom edge of this view
match the bottom edge of the parent.
android:layout_alignParentEnd If true, makes the end edge of this view match
the end edge of the parent.
android:layout_alignParentLeft If true, makes the left edge of this view match
the left edge of the parent.
android:layout_alignParentRight If true, makes the right edge of this view match
the right edge of the parent.
android:layout_alignParentStart If true, makes the start edge of this view match
the start edge of the parent.
android:layout_alignParentTop If true, makes the top edge of this view match
the top edge of the parent.
android:layout_alignRight Makes the right edge of this view match the
right edge of the given anchor view ID.
android:layout_alignStart Makes the start edge of this view match the
start edge of the given anchor view ID.
android:layout_alignTop Makes the top edge of this view match the top
edge of the given anchor view ID.
android:layout_alignWithParentIfMissing If set to true, the parent will be used as the
anchor when the anchor cannot be be found for
layout_toLeftOf, layout_toRightOf, etc.
android:layout_below Positions the top edge of this view below the
given anchor view ID.
android:layout_centerHorizontal If true, centers this child horizontally within its
parent.
android:layout_centerInParent If true, centers this child horizontally and
vertically within its parent.

6
android:layout_centerVertical If true, centers this child vertically within its
parent.
android:layout_toEndOf Positions the start edge of this view to the end
of the given anchor view ID.
android:layout_toLeftOf Positions the right edge of this view to the left
of the given anchor view ID.
android:layout_toRightOf Positions the left edge of this view to the right
of the given anchor view ID.
android:layout_toStartOf Positions the end edge of this view to the start
of the given anchor view ID.

Following code snippet will demonstrate RelativeLayout:

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

Above code will produce following output:

7
Figure 3-6. Output demonstrating RelativeLayout

TableLayout
TableLayout is a layout that arranges its children into rows and columns. It consists of a
number of TableRow objects, each defining a row (actually, you can have other children,
which will be explained below). TableLayout containers do not display border lines for their
rows, columns, or cells. Each row has zero or more cells; each cell can hold one View object.
The table has as many columns as the row with the most cells. A table can leave cells empty.
Cells can span columns, as they can in HTML.

The children of a TableLayout cannot specify the layout_width attribute. Width is always
MATCH_PARENT. However, the layout_height attribute can be defined by a child; default
value is ViewGroup.LayoutParams.WRAP_CONTENT. If the child is a TableRow, then the
height is always ViewGroup.LayoutParams.WRAP_CONTENT.

Cells must be added to a row in increasing column order, both in code and XML. Column
numbers are zero-based. If you don't specify a column number for a child cell, it will auto
increment to the next available column. If you skip a column number, it will be considered
an empty cell in that row.

Although the typical child of a TableLayout is a TableRow, you can actually use any View
subclass as a direct child of TableLayout. The View will be displayed as a single row that
spans all the table columns.

8
Figure 3-7. Representation of TableLayout

Following are the attributes associated with TableLayout.

android:collapseColumns The zero-based index of the columns to collapse. The column

indices must be separated by a comma: 1, 2, 5. Illegal and
duplicate indices are ignored.
android:shrinkColumns The zero-based index of the columns to shrink. The column
indices must be separated by a comma: 1, 2, 5. Illegal and
duplicate indices are ignored. You can shrink all columns by using
the value "*" instead. Note that a column can be marked
stretchable and shrinkable at the same time.
android:stretchColumns The zero-based index of the columns to stretch. The column
indices must be separated by a comma: 1, 2, 5. Illegal and
duplicate indices are ignored. You can stretch all columns by
using the value "*" instead. Note that a column can be marked
stretchable and shrinkable at the same time.

9
Following code snippet will demonstrate TableLayout.

<?xml version="1.0" encoding="utf-8"?>

Above code will display following output:

10
Figure 3-8. Output demonstrating TableLayout

AbsoluteLayout
An Absolute Layout lets you specify exact locations (x/y coordinates) of its children.
Absolute layouts are less flexible and harder to maintain than other types of layouts
without absolute positioning.

Figure 3-9. Representation of AbsoluteLayout

11
Following are the important attributes specific to AbsoluteLayout.

android:layout_x This specifies the x-coordinate of the view.

android:layout_y This specifies the y-coordinate of the

view.

Following code snippet will demonstrate AbsoluteLayout:

<?xml version="1.0" encoding="utf-8"?>

</AbsoluteLayout>

Since AbsoluteLayout was deprecated in API level 3. So, we can use RelativeLayout,
LinearLayout or any other layout for better performance.

Above code will produce following output:

12
Figure 3-10. Output Demonstrating AbsoluteLayout

ConstraintLayout
Constraint layout is an advanced version of a Relative layout. It is used to reduce the child
view hierarchies and improve the performance. It is used to define a layout by assigning
constraints for every child view/widget relative to other views present.

A ConstraintLayout is similar to a RelativeLayout, but with more power. The aim of

ConstraintLayout is to improve the performance of the applications by removing the
nested views with a flat and flexible design.

The aim of the ConstraintLayout is to help reduce the number of nested views, which will
improve the performance of our layout files. The layout class also makes it easier for us to
define layouts than when using a RelativeLayout as we can now anchor any side of a view
with any side of another, rather than having to place a whole view to any side of another.

For example, the attributes of a relative layout allow us to position a view using:
• layout_toRightOf
• layout_toLeftOf
• layout_toTopOf
• layout_toBottomOf

13
However, the ConstraintLayout features several more attributes:
• layout_constraintTop_toTopOf — Align the top of the desired view to the top of
another.
• layout_constraintTop_toBottomOf — Align the top of the desired view to
the bottom of another.
• layout_constraintBottom_toTopOf — Align the bottom of the desired view to
the top of another.
• layout_constraintBottom_toBottomOf — Align the bottom of the desired view to
the bottom of another.
• layout_constraintLeft_toTopOf — Align the left of the desired view to the top of
another.
• layout_constraintLeft_toBottomOf — Align the left of the desired view to
the bottom of another.
• layout_constraintLeft_toLeftOf — Align the left of the desired view to the left of
another.
• layout_constraintLeft_toRightOf — Align the left of the desired view to
the right of another.
• layout_constraintRight_toTopOf — Align the right of the desired view to
the top of another.
• layout_constraintRight_toBottomOf — Align the right of the desired view to
the bottom of another.
• layout_constraintRight_toLeftOf — Align the right of the desired view to
the left of another.
• layout_constraintRight_toRightOf — Align the right of the desired view to
the right of another.
• If desired, attributes supporting start and end are also available in place
of left and right alignment.

Following code snippet will demonstrate constraint layout.

<?xml version="1.0" encoding="utf-8"?>

<android.support.constraint.ConstraintLayout
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:layout_width="match_parent"
android:layout_height="match_parent">

14
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Label 3"
android:textSize="20sp"
android:id="@+id/label3"
app:layout_constraintBottom_toTopOf="@+id/label2"
app:layout_constraintLeft_toRightOf="@+id/label2" />

</android.support.constraint.ConstraintLayout>

Note: Please add following dependency in your build.gradle file.

implementation 'com.android.support.constraint:constraint-layout:1.1.3'

Above code will produce following output:

Figure 3-11. Output Demonstrating ConstraintLayout

15
Android Widgets
Widgets are the building blocks you use to compose a user interface. A widget can show
text or graphics, interact with the user, or arrange other widgets on the screen. Buttons,
text input controls, and check boxes are all types of widgets. Some of the common widgets
used in android are discussed below:

TextView
It is a user interface element that displays text to the user. Following are the attributes
associated with TextView.

android:allowUndo Whether undo should be allowed for editable text.

android:autoLink Controls whether links such as urls and email addresses
are automatically found and converted to clickable links.
android:autoSizeMaxTextSize The maximum text size constraint to be used when auto-
sizing text.
android:autoSizeMinTextSize The minimum text size constraint to be used when auto-
sizing text.
android:autoSizePresetSizes Resource array of dimensions to be used in conjunction
with autoSizeTextType set to uniform.
android:autoSizeStepGranularity Specify the auto-size step size if autoSizeTextType is set
to uniform.
android:autoSizeTextType Specify the type of auto-size.
android:autoText If set, specifies that this TextView has a textual input
method and automatically corrects some common
spelling errors.
android:breakStrategy Break strategy (control over paragraph layout).
android:bufferType Determines the minimum type that getText() will return.
android:capitalize If set, specifies that this TextView has a textual input
method and should automatically capitalize what the
user types.
android:cursorVisible Makes the cursor visible (the default) or invisible.
android:digits If set, specifies that this TextView has a numeric input
method and that these specific characters are the ones
that it will accept.
android:drawableBottom The drawable to be drawn below the text.
android:drawableEnd The drawable to be drawn to the end of the text.
android:drawableLeft The drawable to be drawn to the left of the text.
android:drawablePadding The padding between the drawables and the text.
android:drawableRight The drawable to be drawn to the right of the text.
android:drawableStart The drawable to be drawn to the start of the text.
android:drawableTint Tint to apply to the compound (left, top, etc.)
drawables.
android:drawableTintMode Blending mode used to apply the compound (left, top,
etc.) drawables tint.
android:drawableTop The drawable to be drawn above the text.

16
android:editable If set, specifies that this TextView has an input method.
android:editorExtras Reference to an <input-extras> XML resource containing
additional data to supply to an input method, which is
private to the implementation of the input method.
android:elegantTextHeight Elegant text height, especially for less compacted
complex script text.
android:ellipsize If set, causes words that are longer than the view is wide
to be ellipsized instead of broken in the middle.
android:ems Makes the TextView be exactly this many ems wide.
android:enabled Specifies whether the widget is enabled.
android:fallbackLineSpacing Whether to respect the ascent and descent of the
fallback fonts that are used in displaying the text.
android:firstBaselineToTopHeight Distance from the top of the TextView to the first text
baseline.
android:fontFamily Font family (named by string or as a font resource
reference) for the text.
android:fontFeatureSettings Font feature settings.
android:fontVariationSettings Font variation settings.
android:freezesText If set, the text view will include its current complete text
inside of its frozen icicle in addition to meta-data such as
the current cursor position.
android:gravity Specifies how to align the text by the view's x- and/or y-
axis when the text is smaller than the view.
android:height Makes the TextView be exactly this tall.
android:hint Hint text to display when the text is empty.
android:hyphenationFrequency Frequency of automatic hyphenation.
android:imeActionId Supply a value for EditorInfo.actionId used when an
input method is connected to the text view.
android:imeActionLabel Supply a value for EditorInfo.actionLabel used when an
input method is connected to the text view.
android:imeOptions Additional features you can enable in an IME associated
with an editor to improve the integration with your
application.
android:includeFontPadding Leave enough room for ascenders and descenders
instead of using the font ascent and descent strictly.
android:inputMethod If set, specifies that this TextView should use the
specified input method (specified by fully-qualified class
name).
android:inputType The type of data being placed in a text field, used to help
an input method decide how to let the user enter text.
android:justificationMode Mode for justification.
android:lastBaselineToBottomHeight Distance from the bottom of the TextView to the last
text baseline.
android:letterSpacing Text letter-spacing.
android:lineHeight Explicit height between lines of text.

17
android:lineSpacingExtra Extra spacing between lines of text.
android:lineSpacingMultiplier Extra spacing between lines of text, as a multiplier.
android:lines Makes the TextView be exactly this many lines tall.
android:linksClickable If set to false, keeps the movement method from being
set to the link movement method even if autoLink
causes links to be found.
android:marqueeRepeatLimit The number of times to repeat the marquee animation.
android:maxEms Makes the TextView be at most this many ems wide.
android:maxHeight Makes the TextView be at most this many pixels tall.
android:maxLength Set an input filter to constrain the text length to the
specified number.
android:maxLines Makes the TextView be at most this many lines tall.
android:maxWidth Makes the TextView be at most this many pixels wide.
android:minEms Makes the TextView be at least this many ems wide.
android:minHeight Makes the TextView be at least this many pixels tall.
android:minLines Makes the TextView be at least this many lines tall.
android:minWidth Makes the TextView be at least this many pixels wide.
android:numeric If set, specifies that this TextView has a numeric input
method.
android:password Whether the characters of the field are displayed as
password dots instead of themselves.
android:phoneNumber If set, specifies that this TextView has a phone number
input method.
android:privateImeOptions An addition content type description to supply to the
input method attached to the text view, which is private
to the implementation of the input method.
android:scrollHorizontally Whether the text is allowed to be wider than the view
(and therefore can be scrolled horizontally).
android:selectAllOnFocus If the text is selectable, select it all when the view takes
focus.
android:shadowColor Place a blurred shadow of text underneath the text,
drawn with the specified color.
android:shadowDx Horizontal offset of the text shadow.
android:shadowDy Vertical offset of the text shadow.
android:shadowRadius Blur radius of the text shadow.
android:singleLine Constrains the text to a single horizontally scrolling line
instead of letting it wrap onto multiple lines, and
advances focus instead of inserting a newline when you
press the enter key.
android:text Text to display.
android:textAllCaps Present the text in ALL CAPS.
android:textAppearance Base text color, typeface, size, and style.
android:textColor Text color.
android:textColorHighlight Color of the text selection highlight.
android:textColorHint Color of the hint text.

18
android:textColorLink Text color for links.
android:textCursorDrawable Reference to a drawable that will be drawn under the
insertion cursor.
android:textFontWeight Weight for the font used in the TextView.
android:textIsSelectable Indicates that the content of a non-editable text can be
selected.
android:textScaleX Sets the horizontal scaling factor for the text.
android:textSelectHandle Reference to a drawable that will be used to display a
text selection anchor for positioning the cursor within
text.
android:textSelectHandleLeft Reference to a drawable that will be used to display a
text selection anchor on the left side of a selection
region.
android:textSelectHandleRight Reference to a drawable that will be used to display a
text selection anchor on the right side of a selection
region.
android:textSize Size of the text.
android:textStyle Style (normal, bold, italic, bold|italic) for the text.
android:typeface Typeface (normal, sans, serif, monospace) for the text.
android:width Makes the TextView be exactly this wide.

Following code snippet will demonstrate TextView:

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

Above code will produce following output:

19
Figure 3-12. Output Demonstrating TextView

EditText
A user interface element for entering and modifying text. When you define an edit text
widget, you must specify the inputType attribute. For example, for plain text input set
inputType to "text".
Choosing the input type configures the keyboard type that is shown, acceptable characters,
and appearance of the edit text. For example, if you want to accept a secret number, like
a unique pin or serial number, you can set inputType to "numericPassword". An inputType
of "numericPassword" results in an edit text that accepts numbers only, shows a numeric
keyboard when focused, and masks the text that is entered for privacy.

We can use same set of attributes that we have used for TextView.

Following code snipped will demonstrate EditText:

<?xml version="1.0" encoding="utf-8"?>

<EditText
android:layout_width="match_parent"
android:layout_height="wrap_content"

20
android:layout_alignParentTop="true"
android:layout_centerHorizontal="true"
android:layout_marginTop="49dp"
android:hint="Enter Text Here"
android:inputType="text"
android:textColor="#3F51B5"
android:textColorHint="#3F51B5"
android:textSize="20sp"
android:textAlignment="center"
android:tooltipText="Enter Text" />

</RelativeLayout>

Above code will produce following output:

Figure 3-13. Output Demonstrating EditText

21
Button
It is a user interface element the user can tap or click to perform an action. Following are
the attributes associated with Button.

Attributes Inherited from TextView – Almost all attributes of TextView can be used for
Button.

Other Attributes:

android:accessibilityHeading Whether or not this view is a heading for

accessibility purposes.
android:accessibilityLiveRegion Indicates to accessibility services whether the user
should be notified when this view changes.
android:accessibilityPaneTitle The title this view should present to accessibility as
a pane title.
android:accessibilityTraversalAfter Sets the id of a view after which this one is visited in
accessibility traversal.
android:accessibilityTraversalBefore Sets the id of a view before which this one is visited
in accessibility traversal.
android:alpha alpha property of the view, as a value between 0
(completely transparent) and 1 (completely
opaque).
android:autofillHints Describes the content of a view so that a autofill
service can fill in the appropriate data.
android:autofilledHighlight Drawable to be drawn over the view to mark it as
autofilled
May be a reference to another resource, in the form
"@[+][package:]type/name" or a theme attribute in
the form "?[package:]type/name".
android:background A drawable to use as the background.
android:backgroundTint Tint to apply to the background.
android:backgroundTintMode Blending mode used to apply the background tint.
android:clickable Defines whether this view reacts to click events.
android:contentDescription Defines text that briefly describes content of the
view.
android:contextClickable Defines whether this view reacts to context click
events.
android:defaultFocusHighlightEnabled Whether this View should use a default focus
highlight when it gets focused but doesn't
have R.attr.state_focused defined in its
background.
android:drawingCacheQuality Defines the quality of translucent drawing caches.
android:duplicateParentState When this attribute is set to true, the view gets its
drawable state (focused, pressed, etc.) from its
direct parent rather than from itself.

22
android:elevation base z depth of the view.
android:fadeScrollbars Defines whether to fade out scrollbars when they
are not in use.
android:fadingEdgeLength Defines the length of the fading edges.
android:filterTouchesWhenObscured Specifies whether to filter touches when the view's
window is obscured by another visible window.
android:fitsSystemWindows Boolean internal attribute to adjust view layout
based on system windows such as the status bar.
android:focusable Controls whether a view can take focus.
android:focusableInTouchMode Boolean that controls whether a view can take focus
while in touch mode.
android:focusedByDefault Whether this view is a default-focus view.
android:forceHasOverlappingRendering Whether this view has elements that may overlap
when drawn.
android:foreground Defines the drawable to draw over the content.
android:foregroundGravity Defines the gravity to apply to the foreground
drawable.
android:foregroundTint Tint to apply to the foreground.
android:foregroundTintMode Blending mode used to apply the foreground tint.
android:hapticFeedbackEnabled Boolean that controls whether a view should have
haptic feedback enabled for events such as long
presses.
android:id Supply an identifier name for this view, to later
retrieve it
with View.findViewById() or Activity.findViewById().
android:importantForAccessibility Describes whether or not this view is important for
accessibility.
android:importantForAutofill Hints the Android System whether the view node
associated with this View should be included in a
view structure used for autofill purposes.
android:importantForContentCapture Hints the Android System whether the view node
associated with this View should be use for content
capture purposes.
android:isScrollContainer Set this if the view will serve as a scrolling container,
meaning that it can be resized to shrink its overall
window so that there will be space for an input
method.
android:keepScreenOn Controls whether the view's window should keep
the screen on while visible.
android:keyboardNavigationCluster Whether this view is a root of a keyboard navigation
cluster.
android:layerType Specifies the type of layer backing this view.
android:layoutDirection Defines the direction of layout drawing.
android:longClickable Defines whether this view reacts to long click
events.

23
android:minHeight Defines the minimum height of the view.
android:minWidth Defines the minimum width of the view.
android:nextClusterForward Defines the next keyboard navigation cluster.
android:nextFocusDown Defines the next view to give focus to when the next
focus is View.FOCUS_DOWN If the reference refers
to a view that does not exist or is part of a hierarchy
that is invisible, a RuntimeException will result
when the reference is accessed.
android:nextFocusForward Defines the next view to give focus to when the next
focus is View.FOCUS_FORWARD If the reference
refers to a view that does not exist or is part of a
hierarchy that is invisible, a RuntimeException will
result when the reference is accessed.
android:nextFocusLeft Defines the next view to give focus to when the next
focus is View.FOCUS_LEFT.
android:nextFocusRight Defines the next view to give focus to when the next
focus is View.FOCUS_RIGHT If the reference refers
to a view that does not exist or is part of a hierarchy
that is invisible, a RuntimeException will result
when the reference is accessed.
android:nextFocusUp Defines the next view to give focus to when the next
focus is View.FOCUS_UP If the reference refers to a
view that does not exist or is part of a hierarchy that
is invisible, a RuntimeException will result when the
reference is accessed.
android:onClick Name of the method in this View's context to invoke
when the view is clicked.
android:outlineAmbientShadowColor Sets the color of the ambient shadow that is drawn
when the view has a positive Z or elevation value.
android:outlineSpotShadowColor Sets the color of the spot shadow that is drawn
when the view has a positive Z or elevation value.
android:padding Sets the padding, in pixels, of all four edges.
android:paddingBottom Sets the padding, in pixels, of the bottom edge;
see R.attr.padding.
android:paddingEnd Sets the padding, in pixels, of the end edge;
see R.attr.padding.
android:paddingHorizontal Sets the padding, in pixels, of the left and right
edges; see R.attr.padding.
android:paddingLeft Sets the padding, in pixels, of the left edge;
see R.attr.padding.
android:paddingRight Sets the padding, in pixels, of the right edge;
see R.attr.padding.
android:paddingStart Sets the padding, in pixels, of the start edge;
see R.attr.padding.

24
android:paddingTop Sets the padding, in pixels, of the top edge;
see R.attr.padding.
android:paddingVertical Sets the padding, in pixels, of the top and bottom
edges; see R.attr.padding.
android:requiresFadingEdge Defines which edges should be faded on scrolling.
android:rotation rotation of the view, in degrees.
android:rotationX rotation of the view around the x axis, in degrees.
android:rotationY rotation of the view around the y axis, in degrees.
android:saveEnabled If false, no state will be saved for this view when it is
being frozen.
android:scaleX scale of the view in the x direction.
android:scaleY scale of the view in the y direction.
android:screenReaderFocusable Whether this view should be treated as a focusable
unit by screen reader accessibility tools.
android:scrollIndicators Defines which scroll indicators should be displayed
when the view can be scrolled.
android:scrollX The initial horizontal scroll offset, in pixels.
android:scrollY The initial vertical scroll offset, in pixels.
android:scrollbarAlwaysDrawHorizontalTrack Defines whether the horizontal scrollbar track
should always be drawn.
android:scrollbarAlwaysDrawVerticalTrack Defines whether the vertical scrollbar track should
always be drawn.
android:scrollbarDefaultDelayBeforeFade Defines the delay in milliseconds that a scrollbar
waits before fade out.
android:scrollbarFadeDuration Defines the delay in milliseconds that a scrollbar
takes to fade out.
android:scrollbarSize Sets the width of vertical scrollbars and height of
horizontal scrollbars.
android:scrollbarStyle Controls the scrollbar style and position.
android:scrollbarThumbHorizontal Defines the horizontal scrollbar thumb drawable.
android:scrollbarThumbVertical Defines the vertical scrollbar thumb drawable.
android:scrollbarTrackHorizontal Defines the horizontal scrollbar track drawable.
android:scrollbarTrackVertical Defines the vertical scrollbar track drawable.
android:scrollbars Defines which scrollbars should be displayed on
scrolling or not.
android:soundEffectsEnabled Boolean that controls whether a view should have
sound effects enabled for events such as clicking
and touching.
android:stateListAnimator Sets the state-based animator for the View.
android:tag Supply a tag for this view containing a String, to be
retrieved later with View.getTag() or searched for
with View.findViewWithTag().
android:textAlignment Defines the alignment of the text.
android:textDirection Defines the direction of the text.
android:theme Specifies a theme override for a view.

25
android:tooltipText Defines text displayed in a small popup window on
hover or long press.
android:transformPivotX x location of the pivot point around which the view
will rotate and scale.
android:transformPivotY y location of the pivot point around which the view
will rotate and scale.
android:transitionName Names a View such that it can be identified for
Transitions.
android:translationX translation in x of the view.
android:translationY translation in y of the view.
android:translationZ translation in z of the view.
android:visibility Controls the initial visibility of the view.

Following code snipped will demonstrate Button.

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

Above code will produce following output:

26
Figure 3-14. Output Demonstrating Button

CheckBox
A checkbox is a specific type of two-states button that can be either checked or unchecked.
Following are the attributes associated with CheckBox.

Attributes Inherited from TextView – Almost all attributes of TextView can be used for
Button.

Other Attributes:

android:accessibilityHeading Whether or not this view is a heading for

27
android:alpha alpha property of the view, as a value between 0
(completely transparent) and 1 (completely
opaque).
android:autofillHints Describes the content of a view so that a autofill
service can fill in the appropriate data.
android:autofilledHighlight Drawable to be drawn over the view to mark it as
autofilled
May be a reference to another resource, in the form
"@[+][package:]type/name" or a theme attribute in
the form "?[package:]type/name".
android:background A drawable to use as the background.
android:backgroundTint Tint to apply to the background.
android:backgroundTintMode Blending mode used to apply the background tint.
android:clickable Defines whether this view reacts to click events.
android:contentDescription Defines text that briefly describes content of the
view.
android:contextClickable Defines whether this view reacts to context click
events.
android:defaultFocusHighlightEnabled Whether this View should use a default focus
highlight when it gets focused but doesn't
have R.attr.state_focused defined in its background.
android:drawingCacheQuality Defines the quality of translucent drawing caches.
android:duplicateParentState When this attribute is set to true, the view gets its
drawable state (focused, pressed, etc.) from its
direct parent rather than from itself.
android:elevation base z depth of the view.
android:fadeScrollbars Defines whether to fade out scrollbars when they
are not in use.
android:fadingEdgeLength Defines the length of the fading edges.
android:filterTouchesWhenObscured Specifies whether to filter touches when the view's
window is obscured by another visible window.
android:fitsSystemWindows Boolean internal attribute to adjust view layout
based on system windows such as the status bar.
android:focusable Controls whether a view can take focus.
android:focusableInTouchMode Boolean that controls whether a view can take focus
while in touch mode.
android:focusedByDefault Whether this view is a default-focus view.
android:forceHasOverlappingRendering Whether this view has elements that may overlap
when drawn.
android:foreground Defines the drawable to draw over the content.
android:foregroundGravity Defines the gravity to apply to the foreground
drawable.
android:foregroundTint Tint to apply to the foreground.
android:foregroundTintMode Blending mode used to apply the foreground tint.

28
android:hapticFeedbackEnabled Boolean that controls whether a view should have
haptic feedback enabled for events such as long
presses.
android:id Supply an identifier name for this view, to later
retrieve it
with View.findViewById() or Activity.findViewById().
android:importantForAccessibility Describes whether or not this view is important for
accessibility.
android:importantForAutofill Hints the Android System whether the view node
associated with this View should be included in a
view structure used for autofill purposes.
android:importantForContentCapture Hints the Android System whether the view node
associated with this View should be use for content
capture purposes.
android:isScrollContainer Set this if the view will serve as a scrolling container,
meaning that it can be resized to shrink its overall
window so that there will be space for an input
method.
android:keepScreenOn Controls whether the view's window should keep
the screen on while visible.
android:keyboardNavigationCluster Whether this view is a root of a keyboard navigation
cluster.
android:layerType Specifies the type of layer backing this view.
android:layoutDirection Defines the direction of layout drawing.
android:longClickable Defines whether this view reacts to long click
events.
android:minHeight Defines the minimum height of the view.
android:minWidth Defines the minimum width of the view.
android:nextClusterForward Defines the next keyboard navigation cluster.
android:nextFocusDown Defines the next view to give focus to when the next
focus is View.FOCUS_DOWN If the reference refers
to a view that does not exist or is part of a hierarchy
that is invisible, a RuntimeException will result when
the reference is accessed.
android:nextFocusForward Defines the next view to give focus to when the next
focus is View.FOCUS_FORWARD If the reference
refers to a view that does not exist or is part of a
hierarchy that is invisible, a RuntimeException will
result when the reference is accessed.
android:nextFocusLeft Defines the next view to give focus to when the next
focus is View.FOCUS_LEFT.
android:nextFocusRight Defines the next view to give focus to when the next
focus is View.FOCUS_RIGHT If the reference refers to
a view that does not exist or is part of a hierarchy

29
that is invisible, a RuntimeException will result when
the reference is accessed.

android:nextFocusUp Defines the next view to give focus to when the next
focus is View.FOCUS_UP If the reference refers to a
view that does not exist or is part of a hierarchy that
is invisible, a RuntimeException will result when the
reference is accessed.
android:onClick Name of the method in this View's context to invoke
when the view is clicked.
android:outlineAmbientShadowColor Sets the color of the ambient shadow that is drawn
when the view has a positive Z or elevation value.
android:outlineSpotShadowColor Sets the color of the spot shadow that is drawn
when the view has a positive Z or elevation value.
android:padding Sets the padding, in pixels, of all four edges.
android:paddingBottom Sets the padding, in pixels, of the bottom edge;
see R.attr.padding.
android:paddingEnd Sets the padding, in pixels, of the end edge;
see R.attr.padding.
android:paddingHorizontal Sets the padding, in pixels, of the left and right
edges; see R.attr.padding.
android:paddingLeft Sets the padding, in pixels, of the left edge;
see R.attr.padding.
android:paddingRight Sets the padding, in pixels, of the right edge;
see R.attr.padding.
android:paddingStart Sets the padding, in pixels, of the start edge;
see R.attr.padding.
android:paddingTop Sets the padding, in pixels, of the top edge;
see R.attr.padding.
android:paddingVertical Sets the padding, in pixels, of the top and bottom
edges; see R.attr.padding.
android:requiresFadingEdge Defines which edges should be faded on scrolling.
android:rotation rotation of the view, in degrees.
android:rotationX rotation of the view around the x axis, in degrees.
android:rotationY rotation of the view around the y axis, in degrees.
android:saveEnabled If false, no state will be saved for this view when it is
being frozen.
android:scaleX scale of the view in the x direction.
android:scaleY scale of the view in the y direction.
android:screenReaderFocusable Whether this view should be treated as a focusable
unit by screen reader accessibility tools.
android:scrollIndicators Defines which scroll indicators should be displayed
when the view can be scrolled.
android:scrollX The initial horizontal scroll offset, in pixels.

30
android:scrollY The initial vertical scroll offset, in pixels.
android:scrollbarAlwaysDrawHorizontalT Defines whether the horizontal scrollbar track
rack should always be drawn.
android:scrollbarAlwaysDrawVerticalTra Defines whether the vertical scrollbar track should
ck always be drawn.
android:scrollbarDefaultDelayBeforeFad Defines the delay in milliseconds that a scrollbar
e waits before fade out.
android:scrollbarFadeDuration Defines the delay in milliseconds that a scrollbar
takes to fade out.
android:scrollbarSize Sets the width of vertical scrollbars and height of
horizontal scrollbars.
android:scrollbarStyle Controls the scrollbar style and position.
android:scrollbarThumbHorizontal Defines the horizontal scrollbar thumb drawable.
android:scrollbarThumbVertical Defines the vertical scrollbar thumb drawable.
android:scrollbarTrackHorizontal Defines the horizontal scrollbar track drawable.
android:scrollbarTrackVertical Defines the vertical scrollbar track drawable.
android:scrollbars Defines which scrollbars should be displayed on
scrolling or not.
android:soundEffectsEnabled Boolean that controls whether a view should have
sound effects enabled for events such as clicking and
touching.
android:stateListAnimator Sets the state-based animator for the View.
android:tag Supply a tag for this view containing a String, to be
retrieved later with View.getTag() or searched for
with View.findViewWithTag().
android:textAlignment Defines the alignment of the text.
android:textDirection Defines the direction of the text.
android:theme Specifies a theme override for a view.
android:tooltipText Defines text displayed in a small popup window on
hover or long press.
android:transformPivotX x location of the pivot point around which the view
will rotate and scale.
android:transformPivotY y location of the pivot point around which the view
will rotate and scale.
android:transitionName Names a View such that it can be identified for
Transitions.
android:translationX translation in x of the view.
android:translationY translation in y of the view.
android:translationZ translation in z of the view.
android:visibility Controls the initial visibility of the view.

31
Following code snippet will demonstrate CheckBox:

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

Above code will produce following output:

Figure 3-15. Output Demonstrating CheckBox

32
RadioButton
A radio button is a two-states button that can be either checked or unchecked. When the
radio button is unchecked, the user can press or click it to check it. However, contrary to a
CheckBox, a radio button cannot be unchecked by the user once checked.
Radio buttons are normally used together in a RadioGroup. When several radio buttons
live inside a radio group, checking one radio button unchecks all the others.

Following are the attributes of RadioButton:

Attributes Inherited from TextView – Almost all attributes of TextView can be used for
Button.

Other Attributes:

android:accessibilityHeading Whether or not this view is a heading for

accessibility purposes.
android:accessibilityLiveRegion Indicates to accessibility services whether the user
should be notified when this view changes.
android:accessibilityPaneTitle The title this view should present to accessibility as
a pane title.
android:accessibilityTraversalAfter Sets the id of a view after which this one is visited in
accessibility traversal.
android:accessibilityTraversalBefore Sets the id of a view before which this one is visited
in accessibility traversal.
android:alpha alpha property of the view, as a value between 0
(completely transparent) and 1 (completely
opaque).
android:autofillHints Describes the content of a view so that a autofill
service can fill in the appropriate data.
android:autofilledHighlight Drawable to be drawn over the view to mark it as
autofilled
May be a reference to another resource, in the
form "@[+][package:]type/name" or a theme
attribute in the form "?[package:]type/name".
android:background A drawable to use as the background.
android:backgroundTint Tint to apply to the background.
android:backgroundTintMode Blending mode used to apply the background tint.
android:clickable Defines whether this view reacts to click events.
android:contentDescription Defines text that briefly describes content of the
view.
android:contextClickable Defines whether this view reacts to context click
events.
android:defaultFocusHighlightEnabled Whether this View should use a default focus
highlight when it gets focused but doesn't

33
have R.attr.state_focused defined in its
background.

android:drawingCacheQuality Defines the quality of translucent drawing caches.

android:duplicateParentState When this attribute is set to true, the view gets its
drawable state (focused, pressed, etc.) from its
direct parent rather than from itself.
android:elevation base z depth of the view.
android:fadeScrollbars Defines whether to fade out scrollbars when they
are not in use.
android:fadingEdgeLength Defines the length of the fading edges.
android:filterTouchesWhenObscured Specifies whether to filter touches when the view's
window is obscured by another visible window.
android:fitsSystemWindows Boolean internal attribute to adjust view layout
based on system windows such as the status bar.
android:focusable Controls whether a view can take focus.
android:focusableInTouchMode Boolean that controls whether a view can take
focus while in touch mode.
android:focusedByDefault Whether this view is a default-focus view.
android:forceHasOverlappingRendering Whether this view has elements that may overlap
when drawn.
android:foreground Defines the drawable to draw over the content.
android:foregroundGravity Defines the gravity to apply to the foreground
drawable.
android:foregroundTint Tint to apply to the foreground.
android:foregroundTintMode Blending mode used to apply the foreground tint.
android:hapticFeedbackEnabled Boolean that controls whether a view should have
haptic feedback enabled for events such as long
presses.
android:id Supply an identifier name for this view, to later
retrieve it
with View.findViewById() or Activity.findViewById().

android:importantForAccessibility Describes whether or not this view is important for

accessibility.
android:importantForAutofill Hints the Android System whether the view node
associated with this View should be included in a
view structure used for autofill purposes.
android:importantForContentCapture Hints the Android System whether the view node
associated with this View should be use for content
capture purposes.
android:isScrollContainer Set this if the view will serve as a scrolling
container, meaning that it can be resized to shrink
its overall window so that there will be space for an
input method.

34
android:keepScreenOn Controls whether the view's window should keep
the screen on while visible.
android:keyboardNavigationCluster Whether this view is a root of a keyboard navigation
cluster.
android:layerType Specifies the type of layer backing this view.
android:layoutDirection Defines the direction of layout drawing.
android:longClickable Defines whether this view reacts to long click
events.
android:minHeight Defines the minimum height of the view.
android:minWidth Defines the minimum width of the view.
android:nextClusterForward Defines the next keyboard navigation cluster.
android:nextFocusDown Defines the next view to give focus to when the
next focus is View.FOCUS_DOWN If the reference
refers to a view that does not exist or is part of a
hierarchy that is invisible, a RuntimeException will
result when the reference is accessed.
android:nextFocusForward Defines the next view to give focus to when the
next focus is View.FOCUS_FORWARD If the
reference refers to a view that does not exist or is
part of a hierarchy that is invisible,
a RuntimeException will result when the reference
is accessed.
android:nextFocusLeft Defines the next view to give focus to when the
next focus is View.FOCUS_LEFT.
android:nextFocusRight Defines the next view to give focus to when the
next focus is View.FOCUS_RIGHT If the reference
refers to a view that does not exist or is part of a
hierarchy that is invisible, a RuntimeException will
result when the reference is accessed.
android:nextFocusUp Defines the next view to give focus to when the
next focus is View.FOCUS_UP If the reference refers
to a view that does not exist or is part of a hierarchy
that is invisible, a RuntimeException will result
when the reference is accessed.
android:onClick Name of the method in this View's context to
invoke when the view is clicked.
android:outlineAmbientShadowColor Sets the color of the ambient shadow that is drawn
when the view has a positive Z or elevation value.
android:outlineSpotShadowColor Sets the color of the spot shadow that is drawn
when the view has a positive Z or elevation value.
android:padding Sets the padding, in pixels, of all four edges.
android:paddingBottom Sets the padding, in pixels, of the bottom edge;
see R.attr.padding.
android:paddingEnd Sets the padding, in pixels, of the end edge;
see R.attr.padding.

35
android:paddingHorizontal Sets the padding, in pixels, of the left and right
edges; see R.attr.padding.
android:paddingLeft Sets the padding, in pixels, of the left edge;
see R.attr.padding.
android:paddingRight Sets the padding, in pixels, of the right edge;
see R.attr.padding.
android:paddingStart Sets the padding, in pixels, of the start edge;
see R.attr.padding.
android:paddingTop Sets the padding, in pixels, of the top edge;
see R.attr.padding.
android:paddingVertical Sets the padding, in pixels, of the top and bottom
edges; see R.attr.padding.
android:requiresFadingEdge Defines which edges should be faded on scrolling.
android:rotation rotation of the view, in degrees.
android:rotationX rotation of the view around the x axis, in degrees.
android:rotationY rotation of the view around the y axis, in degrees.
android:saveEnabled If false, no state will be saved for this view when it
is being frozen.
android:scaleX scale of the view in the x direction.
android:scaleY scale of the view in the y direction.
android:screenReaderFocusable Whether this view should be treated as a focusable
unit by screen reader accessibility tools.
android:scrollIndicators Defines which scroll indicators should be displayed
when the view can be scrolled.
android:scrollX The initial horizontal scroll offset, in pixels.
android:scrollY The initial vertical scroll offset, in pixels.
android:scrollbarAlwaysDrawHorizonta Defines whether the horizontal scrollbar track
lTrack should always be drawn.
android:scrollbarAlwaysDrawVerticalTr Defines whether the vertical scrollbar track should
ack always be drawn.
android:scrollbarDefaultDelayBeforeFa Defines the delay in milliseconds that a scrollbar
de waits before fade out.
android:scrollbarFadeDuration Defines the delay in milliseconds that a scrollbar
takes to fade out.
android:scrollbarSize Sets the width of vertical scrollbars and height of
horizontal scrollbars.
android:scrollbarStyle Controls the scrollbar style and position.
android:scrollbarThumbHorizontal Defines the horizontal scrollbar thumb drawable.
android:scrollbarThumbVertical Defines the vertical scrollbar thumb drawable.
android:scrollbarTrackHorizontal Defines the horizontal scrollbar track drawable.
android:scrollbarTrackVertical Defines the vertical scrollbar track drawable.
android:scrollbars Defines which scrollbars should be displayed on
scrolling or not.

36
android:soundEffectsEnabled Boolean that controls whether a view should have
sound effects enabled for events such as clicking
and touching.
android:stateListAnimator Sets the state-based animator for the View.
android:tag Supply a tag for this view containing a String, to be
retrieved later with View.getTag() or searched for
with View.findViewWithTag().
android:textAlignment Defines the alignment of the text.
android:textDirection Defines the direction of the text.
android:theme Specifies a theme override for a view.
android:tooltipText Defines text displayed in a small popup window on
hover or long press.
android:transformPivotX x location of the pivot point around which the view
will rotate and scale.
android:transformPivotY y location of the pivot point around which the view
will rotate and scale.
android:transitionName Names a View such that it can be identified for
Transitions.
android:translationX translation in x of the view.
android:translationY translation in y of the view.
android:translationZ translation in z of the view.
android:visibility Controls the initial visibility of the view.

Following code will demonstrate RadioButton.

<?xml version="1.0" encoding="utf-8"?>

<RadioButton
android:layout_width="wrap_content"
android:layout_height="wrap_content"

37
android:text="Female"
android:textSize="20sp"/>

</RadioGroup>

</LinearLayout>

Above code will produce following output:

Figure 3-16. Output Demonstrating Button

Spinner
It is a view that displays one child at a time and lets the user pick among them. The items
in the Spinner come from the String array or Adapter associated with this view.
Following are some important attributes associated with spinner.

android:dropDownHorizontalOffset Amount of pixels by which the drop down should be

offset horizontally.
android:dropDownSelector List selector to use for spinnerMode="dropdown"
display.
android:dropDownVerticalOffset Amount of pixels by which the drop down should be
offset vertically.
android:dropDownWidth Width of the dropdown in spinnerMode="dropdown".

38
android:gravity Gravity setting for positioning the currently selected
item.
android:popupBackground Background drawable to use for the dropdown in
spinnerMode="dropdown".
android:prompt The prompt to display when the spinner's dialog is
shown.
android:spinnerMode Display mode for spinner options.
android:entries Used for loading string array.

Following example will demonstrate Spinner. In this example for collection of items to be
loaded in Spinner we are creating string array in strings.xml file. We can also load items
collection programmatically.

strings.xml

<string-array name="spinner_items">
<item>Item 1</item>
<item>Item 2</item>
<item>Item 3</item>
<item>Item 4</item>
</string-array>

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

Above code will produce following output:

39
Figure 3-17. Output Demonstrating Spinner

We can also array of elements in Spinner programmatically using adapter as follows:

Spinner spinner=findViewById(R.id.spinner);
String items[]={"Item 1","Item 2","Item 3","Item 4"};

ArrayAdapter<String> arrayAdapter=new ArrayAdapter<String>

(this,R.layout.support_simple_spinner_dropdown_item,items);
spinner.setAdapter(arrayAdapter);

Event Handling
Events are a useful way to collect data about a user's interaction with interactive
components of Applications. Like button presses or screen touch etc. The Android
framework maintains an event queue as first-in, first-out (FIFO) basis. You can capture
these events in your program and take appropriate action as per requirements.
There are following three concepts related to Android Event Management −
• Event Listeners − An event listener is an interface in the View class that contains a
single callback method. These methods will be called by the Android framework
when the View to which the listener has been registered is triggered by user
interaction with the item in the UI.

40
• Event Listeners Registration − Event Registration is the process by which an Event
Handler gets registered with an Event Listener so that the handler is called when
the Event Listener fires the event.
• Event Handlers − When an event happens and we have registered an event listener
for the event, the event listener calls the Event Handlers, which is the method that
actually handles the event.

Event Listeners & Event Handlers

Event Handler Event Listener & Description

OnClickListener()
onClick() This is called when the user either clicks or touches or focuses upon
any widget like button, text, image etc. You will use onClick() event
handler to handle such event.

OnLongClickListener()
onLongClick()
This is called when the user either clicks or touches or focuses upon
any widget like button, text, image etc. for one or more seconds.
You will use onLongClick() event handler to handle such event.

OnFocusChangeListener()
onFocusChange()
This is called when the widget looses its focus ie. user goes away
from the view item. You will use onFocusChange() event handler to
handle such event.

OnFocusChangeListener()
onKey()
This is called when the user is focused on the item and presses or
releases a hardware key on the device. You will use onKey() event
handler to handle such event.

OnTouchListener()
onTouch()
This is called when the user presses the key, releases the key, or any
movement gesture on the screen. You will use onTouch() event
handler to handle such event.

OnMenuItemClickListener()
onMenuItemClick()
This is called when the user selects a menu item. You will use
onMenuItemClick() event handler to handle such event.

onCreateContextMenuItemListener()
onCreateContextMenu()
This is called when the context menu is being built(as the result of
a sustained "long click)

41
Following example will demonstrate onClick() event. For this we are creating a Button and
while clicking Button a Toast message will be displayed on screen.

Button btn=findViewById(R.id.button1);
//adding click event and listener
btn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
//displaying message
Toast.makeText(getApplicationContext(),"Button Clicked !",
Toast.LENGTH_SHORT).show();
}
});

Above code will produce following output:

Figure 3-18. Output Demonstrating onCLick() Event

42
Working with String and String Array
A string resource provides text strings for your application with optional text styling and
formatting. String is a XML resource that provides a single string while String array is a
XML resource that provides an array of strings.

Using String

XML file saved at res/values/strings.xml:

<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="semester">Sixth </string>
</resources>

This layout XML applies a string to a View as follows:

This application code retrieves a string as follows:

String string = getString(R.string.semester);

Using String Array

XML file saved at res/values/strings.xml:

<?xml version="1.0" encoding="utf-8"?>
<resources>
<string-array name="semesters">
<item>First</item>
<item>Second</item>
<item>Third</item>
<item>Fourth</item>
</string-array>
</resources>

This layout XML applies a string to a View as follows:

This application code retrieves a string array as follows:

Resources res = getResources();
String[] planets = res.getStringArray(R.array.semesters);

43
Working with Colors
A color resource provides set of colors that you can use all over your application.

XML file saved at res/values/colors.xml:

<?xml version="1.0" encoding="utf-8"?>
<resources>
<color name="colorPrimary">#3F51B5</color>
<color name="colorPrimaryDark">#303F9F</color>
<color name="colorAccent">#FF4081</color>
</resources>

This layout XML applies a colors to a View as follows:

Working with Drawable

A drawable resource is a general concept for a graphic that can be drawn to the screen and
which you can retrieve with APIs such as getDrawable(int) or apply to another XML
resource with attributes such as android:drawable and android:icon.
A bitmap file is a .png, .jpg, or .gif file. Android creates a Drawable resource for any of these
files when you save them in the res/drawable/ directory.

With an image saved at res/drawable/myimage.png, this layout XML applies the image to
a View:
<ImageView
android:layout_height="wrap_content"
android:layout_width="wrap_content"
android:src="@drawable/myimage" />

The following application code retrieves the image as a Drawable:

Resources res = getResources();
Drawable drawable = ResourcesCompat.getDrawable(res,
R.drawable.myimage, null);

Adding Icon to the Project

With an image saved at res/drawable/myicon.png, you can add this image as icon to the
project in android manifest file:

android:icon="@drawable/myicon"

44
Exercise

1. What do you mean by layout? List and explain different types of layout used in
android with their major attributes.
2. Differentiate LinearLayout and RelativeLayout with example.
3. Differentiate RelativeLayout and ConstraintLayout with example.
4. Compare AbsoluteLayout with other types of layout.
5. Explain any five widgets with their attributes in detail.
6. What do you mean by event? Explain event handling in detail.
7. How can you use string and string array in android? Explain.
8. How can you use color in android? Explain.
9. Differentiate string and string array with example.
10. Explain the procedure for adding and displaying image in imageview. Also write
code snippet to add icon to your project.
11. Design a signup form using Relative, Linear, Absolute and Constraint Layout.
12. Design a simple UI for Book Entry in library.
13. Design a simple UI for patient registration in hospital.
14. Display the following data using TableLayout.
Student Id Name Address Gender
001 Ram Sharma Birtamode Male
002 Gita Sharma Kathmandu Female
15. Design a simple calculator UI using TableLayout.

45
Unit -4
Android Activity [4 Hrs]
The Activity Life Cycle
Every instance of Activity has a lifecycle. During this lifecycle, an activity transitions
between three possible states: running, paused, and stopped. For each transition, there is
an Activity method that notifies the activity of the change in its state.
As a user navigates through, out of, and back to your app, the Activity instances in your app
transition through different states in their lifecycle. The Activity class provides a number of
callbacks that allow the activity to know that a state has changed: that the system is
creating, stopping, or resuming an activity, or destroying the process in which the activity
resides.
Within the lifecycle callback methods, you can declare how your activity behaves when the
user leaves and re-enters the activity. For example, if you're building a streaming video
player, you might pause the video and terminate the network connection when the user
switches to another app. When the user returns, you can reconnect to the network and
allow the user to resume the video from the same spot. In other words, each callback
allows you to perform specific work that's appropriate to a given change of state. Doing
the right work at the right time and handling transitions properly make your app more
robust and performant. For example, good implementation of the lifecycle callbacks can
help ensure that your app avoids:
• Crashing if the user receives a phone call or switches to another app while using
your app.
• Consuming valuable system resources when the user is not actively using it.
• Losing the user's progress if they leave your app and return to it at a later time.
• Crashing or losing the user's progress when the screen rotates between landscape
and portrait orientation.

To navigate transitions between stages of the activity lifecycle, the Activity class provides
a core set of six callbacks: onCreate(), onStart(), onResume(), onPause(), onStop(), and
onDestroy(). The system invokes each of these callbacks as an activity enters a new state.

Figure 4-1 shows the activity lifecycle, states, and methods.

1
Figure 4-1. A simplified illustration of the activity lifecycle
onCreate()
You must implement this callback, which fires when the system first creates the activity.
On activity creation, the activity enters the Created state. In the onCreate() method, you
perform basic application startup logic that should happen only once for the entire life of
the activity.
@Override
protected void onCreate(Bundle b) {
super.onCreate(b);
//your stuffs
}

2
onStart()
When the activity enters the Started state, the system invokes this callback. The onStart()
call makes the activity visible to the user, as the app prepares for the activity to enter the
foreground and become interactive. For example, this method is where the app initializes
the code that maintains the UI.
The onStart() method completes very quickly and, as with the Created state, the activity
does not stay resident in the Started state. Once this callback finishes, the activity enters
the Resumed state, and the system invokes the onResume() method.

@Override
protected void onStart()
{
super.onStart();
//your stuffs
}

onResume()
When the activity enters the Resumed state, it comes to the foreground, and then the
system invokes the onResume() callback. This is the state in which the app interacts with
the user. The app stays in this state until something happens to take focus away from the
app. Such an event might be, for instance, receiving a phone call, the user’s navigating to
another activity, or the device screen’s turning off.

@Override
protected void onResume() {
super.onResume();
//your stuffs
}

onPause()
The system calls this method as the first indication that the user is leaving your activity
(though it does not always mean the activity is being destroyed); it indicates that the
activity is no longer in the foreground (though it may still be visible if the user is in multi-
window mode). Use the onPause() method to pause or adjust operations that should not
continue (or should continue in moderation) while the Activity is in the Paused state, and
that you expect to resume shortly. There are several reasons why an activity may enter this
state. For example:
• Some event interrupts app execution, as described in the onResume() section. This
is the most common case.
• In Android 7.0 (API level 24) or higher, multiple apps run in multi-window mode.
Because only one of the apps (windows) has focus at any time, the system pauses
all of the other apps.
• A new, semi-transparent activity (such as a dialog) opens. As long as the activity is
still partially visible but not in focus, it remains paused.

3
@Override
protected void onPause() {
super.onPause();
//your stuffs
}

onStop()
When your activity is no longer visible to the user, it has entered the Stopped state, and
the system invokes the onStop() callback. This may occur, for example, when a newly
launched activity covers the entire screen. The system may also call onStop() when the
activity has finished running, and is about to be terminated.
You should also use onStop() to perform relatively CPU-intensive shutdown operations. For
example, if you can't find a more opportune time to save information to a database, you
might do so during onStop().

@Override
protected void onStop() {
super.onStop();
//your stuffs
}

onDestroy()
onDestroy() is called before the activity is destroyed. The system invokes this callback
either because:
• the activity is finishing (due to the user completely dismissing the activity or due to
finish() being called on the activity), or
• the system is temporarily destroying the activity due to a configuration change
(such as device rotation or multi-window mode)

If the activity is finishing, onDestroy() is the final lifecycle callback the activity receives. If
onDestroy() is called as the result of a configuration change, the system immediately
creates a new activity instance and then calls onCreate() on that new instance in the new
configuration. The onDestroy() callback should release all resources that have not yet been
released by earlier callbacks such as onStop().

@Override
protected void onDestroy() {
super.onDestroy();
//your stuffs
}

Following example will demonstrate lifecycle of android:

4
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.util.Log;

public class MainActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
//displaying message in Log
Log.d("Lifecycle Test", "Activity Created");
}

@Override
protected void onStart()
{
super.onStart();
Log.d("Lifecycle Test", "Activity Started");
}

@Override
protected void onResume() {
super.onResume();
Log.d("Lifecycle Test", "Activity Resumed");
}

@Override
protected void onRestart() {
super.onRestart();
Log.d("Lifecycle Test", "Activity Restarted");
}

@Override
protected void onPause() {
super.onPause();
Log.d("Lifecycle Test", "Activity Paused");
}

@Override
protected void onStop() {
super.onStop();
Log.d("Lifecycle Test", "Activity Stopped");
}

@Override
protected void onDestroy() {
super.onDestroy();
Log.d("Lifecycle Test", "Activity Destroyed");
}

5
Now go to Logcat present inside Android Monitor: Scroll up and you will notice three
methods which were called: Activity Created, Activity started and Activity resumed.

Now press the back button on the Emulator and exit the App. Go to Logcat again and scroll
down to bottom. You will see 3 more methods were called: Activity paused, Activity
stopped and Activity is being destroyed.

Creating Multiple Activities

So far we have created and tested only a single activity. Now we are going to create
multiple activities and also going to learn about linking different activities.
For this purpose, I am going create two activities having the name “FirstActivity” and
“SecondActivity”. FirstActivity contains TextView and Button. On the other hand,
SecondActivity contains a TextView.

FirstActivity.java

import android.app.Activity;
import android.os.Bundle;

public class FirstActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
}
}

6
SecondActivity.java

import android.app.Activity;
import android.os.Bundle;

public class SecondActivity extends Activity {

@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.second_activity);
}
}

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

second_activity.xml

<?xml version="1.0" encoding="utf-8"?>

7
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="This is Second Activity"
android:textSize="20sp"
android:textStyle="bold"
android:layout_gravity="center"
android:layout_marginTop="100dp"
android:id="@+id/text2"
/>

</LinearLayout>

Above xml code produces following design:

Figure 4-2. Representing FirstActivity and SecondActivity

Declaring Activities in Manifest

Since we have already discussed about declaring activity in manifest file. Previously we got
only single activity to be declared in manifest file. But now we are going to discuss about
the process of declaring both the activities “FirstActivity” and “SecondActivity” in manifest
file.

8
AndroidManifest.xml

<?xml version="1.0" encoding="utf-8"?>

</application>

</manifest>

In above manifest file, FirstActivity contains <intent-filter> so, FirstActivity will be

launched first when we run our application.

Connecting Activities with Intents

An intent is an object that a component can use to communicate with the OS. The only
components you have seen so far are activities, but there are also services, broadcast
receivers, and content providers.

Intents are multi-purpose communication tools, and the Intent class provides different
constructors depending on what you are using the intent to do.

In this case, you are using an intent to tell the ActivityManager which activity to start, so
you will use this constructor:
public Intent(Context packageContext, Class<?> cls)

The Class object specifies the activity that the ActivityManager should start. The Context
object tells the ActivityManager which package the Class object can be found in.

9
Figure 4-3. The intent: telling ActivityManager what to do

Following code snippet opens SecondActivity using Intent when user clicks Button in
FirstActivity:

Passing Data Between Activities

Between activities data can be passed and received by using Intent extras. Extras are
arbitrary data that the calling activity can include with an intent. The OS forwards the
intent to the recipient activity, which can then access the extra and retrieve the data.

An extra is structured as a key-value pair. To add an extra to an intent, you use

Intent.putExtra(…). In particular, you will be calling

public Intent putExtra(String name, boolean value)

Intent.putExtra(…) comes in many flavors, but it always has two arguments. The first
argument is always a String key, and the second argument is the value, whose type will
vary.

Let’s learn this with the help of an example. Suppose if we want to pass data like id, name
and address of student from FirstActivity to SecondActivity then we can use Intent extras
as follows:

10
FirstActivity.java

public class FirstActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);

Button btn=findViewById(R.id.button1);
btn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent i=new Intent(FirstActivity.this,
SecondActivity.class);
//passing data using putExtra
i.putExtra("id",001);
i.putExtra("name","Ram");
i.putExtra("address","KTM");
startActivity(i);
}
});
}
}

SecondActivity.java

public class SecondActivity extends Activity {

@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.second_activity);

//receiving data
Intent i=getIntent();
int id=i.getIntExtra("id",0);
//second argument is default value
String name=i.getStringExtra("name");
String address=i.getStringExtra("address");

//Displaying received data in TextView

TextView txt=findViewById(R.id.text2);

txt.setText("Id="+id+"\n"+"Name="+name+"\n"+"Address="+
address);
}
}

Following output will be displayed in SecondActivity.

11
Figure 4-4. Output displayed in SecondActivity

Getting Result Back form Child Activity

In previous example, we pass data from FirstActivity to SecondActivity. Now if we want to
pass data from SecondActivity back to FirstActivity then we should use following
procedure:
• First open SecondActivity form FirstActivity using following Activity method:
public void startActivityForResult(Intent intent, int requestCode)

The first parameter is the same intent as before. The second parameter is the
request code. The request code is a user-defined integer that is sent to the child
activity and then received back by the parent. It is used when an activity starts more
than one type of child activity and needs to tell who is reporting back.

• Now pass data from SecondActivity to FirstActivity using following methods. There
are two methods you can call in the child activity to send data back to the parent:
public final void setResult(int resultCode)
public final void setResult(int resultCode, Intent data)

• And finally, receive data in FirstActivity by overriding onActivityResult(…) method.

12
Following example will demonstrate this procedure. Here we are adding a Button in
SecondActivity. When user clicks this Button a message “Hello First Activity!” will be sent
to FirstActivity. This message will be displayed in TextView of FirstActivity.

FirstActivity.java

public class FirstActivity extends Activity {

TextView txt;
Button btn;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);

txt=findViewById(R.id.text1);
btn=findViewById(R.id.button1);

btn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent i=new Intent(FirstActivity.this,
SecondActivity.class);
//starting activity with result code 2
startActivityForResult(i,2);
}
});
}

// Call Back method to get the Message form other Activity

@Override
protected void onActivityResult(int requestCode, int
resultCode, Intent data)
{
super.onActivityResult(requestCode, resultCode, data);
// check if the request code is same as what is passed
here it is 2
if(requestCode==2)
{
String message=data.getStringExtra("message");
txt.setText(message);
}
}
}

SecondActivity.java

public class SecondActivity extends Activity {

Button btn;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.second_activity);

btn=findViewById(R.id.button2);

13
btn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent i=new Intent();
i.putExtra("message","Hello First Activity!");
setResult(2,i);
finish();//finishing activity
}
});

}
}

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

second_activity.xml

<?xml version="1.0" encoding="utf-8"?>

14
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="This is Second Activity"
android:textSize="20sp"
android:textStyle="bold"
android:layout_gravity="center"
android:layout_marginTop="100dp"
android:id="@+id/text2"
/>

</LinearLayout>

After clicking Button in SecondActivity following output will be produced in FirstActivity:

Figure 4-5. Output displayed in FirstActivity after Button click in SecondActivity

15
Getting and Setting Data to/from Layout File
To demonstrate this topic, now we are going to create an activity containing some
important widgets like TextView, Button, EditText, RadioButton and Spinner. First we try
to get all data that we have inputted using these widgets. After getting all data we will
display all received data in a TextView.

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

<RadioGroup
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@+id/edtName"
android:id="@+id/radGroup"

16
android:orientation="horizontal"
android:layout_toRightOf="@+id/txtGender">

</RelativeLayout>

17
FirstActivity.java

public class FirstActivity extends Activity {

EditText edtId,edtName;
RadioButton radMale,radFemale;
Spinner spProgram;
Button btnSubmit;
TextView txtResult;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);

edtId=findViewById(R.id.edtId);
edtName=findViewById(R.id.edtName);
radMale=findViewById(R.id.radMale);
radFemale=findViewById(R.id.radFemale);
spProgram=findViewById(R.id.spProgram);
btnSubmit=findViewById(R.id.btnSubmit);
txtResult=findViewById(R.id.txtResult);

btnSubmit.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
//getting data from edit text
String id=edtId.getText().toString();
String name=edtName.getText().toString();
//getting data from radio button
String gender="";
if(radMale.isChecked())
gender="Male";
else
gender="Female";
//getting data from spinner
String program=spProgram.getSelectedItem().toString();

//displaying data in text view

txtResult.setText("Student Id="+id+"\n"+"Student Name="
+name+"\n"+"Gender="+gender+"\n"+"Program="+program);
}
});

}
}

Above code will produce following output:

18
Figure 4-6. Output demonstrating getting and setting data to/from xml file

Now we are going to look another example where user input two numbers using EditText.
When user clicks a Button then our application performs addition of two numbers and
displays result in a TextView.

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

<EditText
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_below="@+id/edtFirst"

19
android:layout_margin="5dp"
android:hint="Enter Second Number"
android:inputType="number"
android:id="@+id/edtSecond" />

</RelativeLayout>

FirstActivity.java

public class FirstActivity extends Activity {

EditText edtFirst,edtSecond;
Button btnCalculate;
TextView txtResult;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);

edtFirst=findViewById(R.id.edtFirst);
edtSecond=findViewById(R.id.edtSecond);
btnCalculate=findViewById(R.id.btnCalculate);
txtResult=findViewById(R.id.txtResult);

btnCalculate.setOnClickListener(new View.OnClickListener()
{
@Override
public void onClick(View view) {
//getting data from edit text
int first,second,result;
first=Integer.parseInt(edtFirst.getText().toString());
second=Integer.parseInt(edtSecond.getText().toString());
result=first+second;
//displaying result in TextView
txtResult.setText("Result="+result);
}
});
}
}

Above code will produce following output:

20
Figure 4-7. Output demonstrating addition of two numbers

Exercise

1. What do you mean by android activity? Explain android activity life cycle in detail.
2. How can you declare multiple activities in manifest? Explain.
3. What do you mean by intent? Explain.
4. How can you pass data between multiple activities using intent? Explain.
5. Develop an android application which get result back from a child activity.
6. Develop an android application to calculate simple interest. Your application should
contain fields to input principal, rate, time and button for event handling. Calculate
and display result in a TextView.
7. Develop an android application to calculate area and perimeter of rectangle. Your
application should contain fields to input length and breadth and two buttons for
calculating area and perimeter. Calculate and display result in a TextView.
8. Design a signup form using any layout of your choice.
- Your design must include important widgets like TextView, EditText, Button,
RadioButton, CheckBox, Spinner etc.
- When user clicks a Button display inputted data in a TextView.
9. Develop a simple calculator application with two input fields for inputting numbers
and four Buttons for performing addition, subtraction, multiplication and division.
Display the result in a TextView.
10. Develop an android application to input your name, address, gender and other
personal information. Pass and display this information in another activity.

21
Unit -5
UI Fragments, Menus and Dialogs [6 Hrs]
Introduction to Fragments
Android Fragment is the part of activity, which is also known as sub-activity. There can be
more than one fragment in an activity. Fragments represent multiple screen inside one
activity.

A Fragment represents a behaviour or a portion of user interface in a FragmentActivity.

You can combine multiple fragments in a single activity to build a multi-pane UI and reuse
a fragment in multiple activities. You can think of a fragment as a modular section of an
activity, which has its own lifecycle, receives its own input events, and which you can add
or remove while the activity is running (sort of like a "sub activity" that you can reuse in
different activities).

A fragment must always be hosted in an activity and the fragment's lifecycle is directly
affected by the host activity's lifecycle. For example, when the activity is paused, so are all
fragments in it, and when the activity is destroyed, so are all fragments. However, while an
activity is running (it is in the resumed lifecycle state), you can manipulate each fragment
independently, such as add or remove them. When you perform such a fragment
transaction, you can also add it to a back stack that's managed by the activity—each back
stack entry in the activity is a record of the fragment transaction that occurred. The back
stack allows the user to reverse a fragment transaction (navigate backwards), by pressing
the Back button.

The Need for UI Flexibility

Android introduced fragments in Android 3.0 (API level 11), primarily to support more
dynamic and flexible UI designs on large screens, such as tablets. Because a tablet's screen
is much larger than that of a handset, there's more room to combine and interchange UI
components. Fragments allow such designs without the need for you to manage complex
changes to the view hierarchy. By dividing the layout of an activity into fragments, you
become able to modify the activity's appearance at runtime and preserve those changes in
a back stack that's managed by the activity.

You should design each fragment as a modular and reusable activity component. That is,
because each fragment defines its own layout and its own behavior with its own lifecycle
callbacks, you can include one fragment in multiple activities, so you should design for
reuse and avoid directly manipulating one fragment from another fragment. This is
especially important because a modular fragment allows you to change your fragment
combinations for different screen sizes. When designing your application to support both
tablets and handsets, you can reuse your fragments in different layout configurations to
optimize the user experience based on the available screen space. For example, on a
handset, it might be necessary to separate fragments to provide a single-pane UI when
more than one cannot fit within the same activity.

1
For example, a news application can use one fragment to show a list of articles on the left
and another fragment to display an article on the right—both fragments appear in one
activity, side by side, and each fragment has its own set of lifecycle callback methods and
handle their own user input events. Thus, instead of using one activity to select an article
and another activity to read the article, the user can select an article and read it all within
the same activity, as illustrated in the tablet layout in figure 5-1.

Figure 5-1. An example of how two UI modules defined by fragments can be combined
into one activity for a tablet design, but separated for a handset design.

For example—to continue with the news application example—the application can embed
two fragments in Activity A, when running on a tablet-sized device. However, on a handset-
sized screen, there's not enough room for both fragments, so Activity A includes only the
fragment for the list of articles, and when the user selects an article, it starts Activity B,
which includes the second fragment to read the article. Thus, the application supports both
tablets and handsets by reusing fragments in different combinations, as illustrated in above
figure.

Lifecycle of Fragment
The lifecycle of android fragment is like the activity lifecycle. There are 12 lifecycle methods
for fragment. It is shown below:

2
Figure 5-2. The lifecycle of a fragment (while its activity is running).

3
S.N. Method Description
1) onAttach(Activity) it is called only once when it is attached
with activity.
2) onCreate(Bundle) It is used to initialize the fragment.
3) onCreateView(LayoutInflater, creates and returns view hierarchy.
ViewGroup, Bundle)
4) onActivityCreated(Bundle) It is invoked after the completion of
onCreate() method.
5) onViewStateRestored(Bundle) It provides information to the fragment that
all the saved state of fragment view
hierarchy has been restored.
6) onStart() makes the fragment visible.
7) onResume() makes the fragment interactive.
8) onPause() is called when fragment is no longer
interactive.
9) onStop() is called when fragment is no longer visible.
10) onDestroyView() allows the fragment to clean up resources.
11) onDestroy() allows the fragment to do final clean-up of
fragment state.
12) onDetach() It is called immediately prior to the
fragment no longer being associated with
its activity.

Creating a UI Fragment
Fragment can be created in UI resource file as follows:

Creating a Fragment Class

To create a fragment, extend the Fragment class, then override key lifecycle methods to
insert your app logic, similar to the way you would with an Activity class.

One difference when creating a Fragment is that you must use the onCreateView() callback
to define the layout. In fact, this is the only callback you need in order to get a fragment
running. For example, here's a simple fragment that specifies its own layout:

4
public class Fragment1 extends Fragment {
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup
container,Bundle savedInstanceState) {
// Inflate the layout for this fragment
return inflater.inflate(R.layout.article_view, container,
false);
}
}

Example of Fragment
Following example creates two fragments named as Fragment1 and Fragment2. After
creating fragments, we will add these two fragments in activity named as FirstActivity and
display them.
Firstly, we start by creating two fragments,

fragment1.xml

<?xml version="1.0" encoding="utf-8"?>

fragment2.xml

<?xml version="1.0" encoding="utf-8"?>

5
Fragment1.java

public class Fragment1 extends Fragment {

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup
container, Bundle savedInstanceState) {
// Inflate the layout for this fragment
View view= inflater.inflate(R.layout.fragment1, container,
false);
return view;
}
}

Fragment2.java

public class Fragment2 extends Fragment {

Now we are going to add these fragments to Activity.

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

6
FirstActivity.java

public class FirstActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
}
}

Above code will produce following output:

Figure 5-3. Output Demonstrating Fragments.

7
Wiring Widgets in Fragment
To demonstrate this topic, now I am going to create a fragment named as Fragment1 and
add this fragment to Activity named as FirstActivity. Additionally, to show wiring of widgets
inside fragment I will create UI for adding two numbers using two EditText, one Button and
one TextView for displaying result.
So, Let’s begin by creating fragment.

fragment1.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

Fragment1.java

public class Fragment1 extends Fragment {

EditText edtFirst,edtSecond;
Button btnCalculate;
TextView txtResult;
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup
container, Bundle savedInstanceState) {

8
// Inflate the layout for this fragment
View view= inflater.inflate(R.layout.fragment1, container,
false);

//wiring up widgets
edtFirst=view.findViewById(R.id.edtFirst);
edtSecond=view.findViewById(R.id.edtSecond);
btnCalculate=view.findViewById(R.id.btnCalculate);
txtResult=view.findViewById(R.id.txtResult);

btnCalculate.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
int first,second, result;
first=Integer.parseInt(edtFirst.getText().toString());
second=Integer.parseInt(edtSecond.getText().toString());
result=first+second;
txtResult.setText("Result="+result);
}
});

return view;
}
}

Now add above fragment to Activity.

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

FirstActivity.java

public class FirstActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
}
}

9
Above code will produce following output:

Figure 5-4. Output demonstrating wiring of widgets in Fragment.

Introduction to Fragment Manager

When the Fragment class was introduced in Honeycomb, the Activity class was changed to
include a piece called the FragmentManager. The FragmentManager is responsible for
managing your fragments and adding their views to the activity’s view hierarchy.

We can use FragmentManager to manage fragments as follows:

FragmentManager fm = getFragmentManager();

The FragmentManager handles two things: a list of fragments and a back stack of fragment
transactions. It is shown below:

10
Figure 5-5. The FragmentManager

Fragment transactions are used to add, remove, attach, detach, or replace fragments in
the fragment list. They are the heart of how you use fragments to compose and recompose
screens at runtime. The FragmentManager maintains a back stack of fragment transactions
that you can navigate.
The FragmentManager.beginTransaction() method creates and returns an instance of
FragmentTransaction. The FragmentTransaction class uses a fluent interface - methods
that configure FragmentTransaction return a FragmentTransaction instead of void, which
allows you to chain them together. So the highlighted code in Listing 7.12 says, “Create a
new fragment transaction, include one add operation in it, and then commit it.”

The process is shown below:

Fragment fragment=new Fragment1();

FragmentManager manager = getFragmentManager();
FragmentTransaction transaction = manager.beginTransaction();
transaction.add(R.id.myfragment, fragment);
transaction.commit();

Following example will demonstrate the use of FragmentManager. Here, we are creating
two Fragments and one Activity. Activity contains two buttons for switching fragments i.e,
if first Button is clicked Fragment1 is displayed and if second Button is clicked Fragment2
is displayed on screen.
So, let’s begin by creating two fragments.

fragment1.xml

<?xml version="1.0" encoding="utf-8"?>

<LinearLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:orientation="vertical"
android:background="#AEB6BF"
android:layout_width="match_parent"

11
android:layout_height="match_parent">
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="I am inside Fragment 1"
android:layout_gravity="center"
android:textSize="20sp"
android:layout_marginTop="20sp"
android:textStyle="bold" />
</LinearLayout>

fragment2.xml

<?xml version="1.0" encoding="utf-8"?>

Fragment1.java

public class Fragment1 extends Fragment {

Fragment2.java

public class Fragment2 extends Fragment {

12
Now it’s time to create Activity with two Buttons as follows.

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

FirstActivity.java

public class FirstActivity extends Activity {

Button btnFirst,btnSecond;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);

btnFirst=findViewById(R.id.btnFirst);
btnSecond=findViewById(R.id.btnSecond);

btnFirst.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Fragment fragment=new Fragment1();
FragmentManager manager = getFragmentManager();
FragmentTransaction transaction =
manager.beginTransaction();
transaction.replace(R.id.myfragment, fragment);
transaction.commit();
}
});

btnSecond.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {

13
Fragment fragment=new Fragment2();
FragmentManager manager = getFragmentManager();
FragmentTransaction transaction =
manager.beginTransaction();
transaction.replace(R.id.myfragment, fragment);
transaction.commit();
}
});
}
}

Above code will produce following output:

Figure 5-6. Output demonstrating FragmentManager

Difference between Activity and Fragment

Following are the major differences between Activity and Fragment:

S.N. Activity Fragment

1) Activity is an application component Fragment is a part of an activity, which
that gives a user interface where the contributes its own UI to that activity.
user can interact.
2) Activity is not dependent on Fragment is dependent on Activity, it
Fragment. can't exist independently.
3) Without using fragment in Activity we Using multiple fragments in a single
can't create multi-pane UI. activity we can create multi-pane UI.
4) For Activity, we just need to mention For fragment it’s not required.
in Manifest.
5) Activity is heavy weight. Fragment is light weight.

14
6) Activity use a lot of memory. Fragment doesn’t use any memory
because it resides on Activity.
7) Activity is the UI of an application Fragment is the part of the Activity, it is
through which user can interact. an sub-Activity inside activity which has
its own Life Cycle which runs parallel to
the Activities Life Cycle.
8) Lifecycle of Activity: Lifecycle of Fragment:

9) Lifecycle methods of Activity are Lifecycle methods of Fragments are

hosted by OS. hosted by are hosted by hosting activity.
10) When an activity is placed to the back When an fragment is placed to the
stack of activities the user can activity we have to request the instance
navigate back to the previous activity to be saved by calling addToBackstack()
by just pressing the back button. during the fragment transaction.

Menus
Menus are a common user interface component in many types of applications. To provide
a familiar and consistent user experience, you can use the Menu to present user actions
and other options in your activities.

15
Figure 5-7. Example of Menu

Types of Menu
In Android there are three types of fundamental menus. They are options menu, contextual
menu and popup menu.

Options Menu
The options menu is the primary collection of menu items for an activity. It's where you
should place actions that have a global impact on the app, such as "Search," "Compose
email," and "Settings." Menu shown in above diagram is an example of options menu.

Context Menu
Android context menu appears when user press long clicks on the element. It is also known
as floating menu. It affects the selected content while doing action on it. It doesn't support
item shortcuts and icons.

16
Figure 5-8. Example of Context Menu

Popup Menu
A popup menu displays a list of items in a vertical list that's anchored to the view that
invoked the menu. It's good for providing an overflow of actions that relate to specific
content or to provide options for a second part of a command. Actions in a popup menu
should not directly affect the corresponding content—that's what contextual actions are
for. Rather, the popup menu is for extended actions that relate to regions of content in
your activity.
Android Popup Menu displays the menu below the anchor text if space is available
otherwise above the anchor text. It disappears if you click outside the popup menu.

Figure 5-9. Example of Popup Menu

17
Implementing menu in an Application
For all menu types, Android provides a standard XML format to define menu items. Instead
of building a menu in your activity's code, you should define a menu and all its items in an
XML menu resource. You can then inflate the menu resource (load it as a Menu object) in
your activity or fragment.

Using a menu resource is a good practice for a few reasons:

• It's easier to visualize the menu structure in XML.
• It separates the content for the menu from your application's behavioural code.
• It allows you to create alternative menu configurations for different platform
versions, screen sizes, and other configurations by leveraging the app resources
framework.

To define the menu, create an XML file inside your project's res/menu/ directory and build
the menu with the following elements:

<menu>
• Defines a Menu, which is a container for menu items. A <menu> element must be
the root node for the file and can hold one or more <item> and <group> elements.

<item>
• Creates a Menu Item, which represents a single item in a menu. This element may
contain a nested <menu> element in order to create a submenu.

<group>
• An optional, invisible container for <item> elements. It allows you to categorize
menu items so they share properties such as active state and visibility.

mymenu.xml

<?xml version="1.0" encoding="utf-8"?>

</menu>

The <item> element supports several attributes you can use to define an item's appearance
and behavior. The items in the above menu include the following attributes:

18
android:id
• A resource ID that's unique to the item, which allows the application to recognize
the item when the user selects it.

android:icon
• A reference to a drawable to use as the item's icon.

android:title
• A reference to a string to use as the item's title.

android:showAsAction
• Specifies when and how this item should appear as an action item in the app bar.

Creating Options Menu

We can create options menu by overriding onCreateOptionsMenu() method. For handling
clicks we must override onOptionsItemSelected() method. It is shown by the following
example.

FirstActivity.java

public class FirstActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
}

//adding options menu

@Override
public boolean onCreateOptionsMenu(Menu menu) {
MenuInflater inflater = getMenuInflater();
inflater.inflate(R.menu.mymenu, menu);
return true;
}

//handling clicks
@Override
public boolean onOptionsItemSelected(MenuItem item) {
// Handle item selection
switch (item.getItemId()) {
case R.id.item1:
//your stuffs
return true;
case R.id.item2:
//your stuffs
return true;
default:
return super.onOptionsItemSelected(item);
}
}
}

19
first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

Above code produces following output:

Figure 5-10. Output Demonstrating Options Menu

20
Creating Context Menu
To provide a floating context menu:
1. Register the View to which the context menu should be associated by calling
registerForContextMenu() and pass it the View.
2. Implement the onCreateContextMenu() method in your Activity or Fragment.
3. For event handling on click implement onContextItemSelected().

FirstActivity.java

public class FirstActivity extends AppCompatActivity {

Button btnClick;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);

btnClick=findViewById(R.id.btnClick);

//registering view for context menu

registerForContextMenu(btnClick);

@Override
public void onCreateContextMenu(ContextMenu menu, View v,
ContextMenu.ContextMenuInfo menuInfo) {
super.onCreateContextMenu(menu, v, menuInfo);
MenuInflater inflater = getMenuInflater();
inflater.inflate(R.menu.mymenu, menu);
}

@Override
public boolean onContextItemSelected(MenuItem item) {
switch (item.getItemId()) {
case R.id.item1:
//your stuffs
return true;
case R.id.item2:
//your stuffs
return true;
default:
return super.onContextItemSelected(item);
}
}
}

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

21
<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Show context menu"
android:layout_centerHorizontal="true"
android:layout_marginTop="20sp"
android:id="@+id/btnClick"
android:textSize="20sp" />

</RelativeLayout>

Above code produces following output:

Figure 5-11. Output Demonstrating Context Menu

Creating Popup Menu

If you define your menu in XML, here's how you can show the popup menu:
• Instantiate a PopupMenu with its constructor, which takes the current application
Context and the View to which the menu should be anchored.
• Use MenuInflater to inflate your menu resource into the Menu object returned by
PopupMenu.getMenu().
• Call PopupMenu.show().

22
To perform an action when the user selects a menu item, you must implement the
PopupMenu.OnMenuItemClickListener interface and register it with your PopupMenu by
calling setOnMenuItemclickListener(). When the user selects an item, the system calls the
onMenuItemClick() callback in your interface.

FirstActivity.java

public class FirstActivity extends Activity implements

PopupMenu.OnMenuItemClickListener{
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
}
//showing popup menu
public void showMenu(View v) {
PopupMenu popup = new PopupMenu(this, v);
// This activity implements OnMenuItemClickListener
popup.setOnMenuItemClickListener(this);
popup.inflate(R.menu.mymenu);
popup.show();
}
//handling clicks
@Override
public boolean onMenuItemClick(MenuItem item) {
switch (item.getItemId()) {
case R.id.item1:
//your stuffs
return true;
case R.id.item2:
//your stuffs
return true;
default:
return false;
}
}
}

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

23
Above code produces following output.

Figure 5-12. Output Demonstrating Popup Menu

Dialogs
A dialog is a small window that prompts the user to make a decision or enter additional
information. A dialog does not fill the screen and is normally used for modal events that
require users to take an action before they can proceed.

Figure 5-13. Example of a Dialog

Following are the different types of dialogs:

AlertDialog
• A dialog that can show a title, up to three buttons, a list of selectable items, or a
custom layout.

24
DatePickerDialog or TimePickerDialog
• A dialog with a pre-defined UI that allows the user to select a date or time.

Custom Dialog
• A custom dialog built by programmer as per the requirement.

Creating a Dialog Fragment

We can create a wide variety of dialog designs—including custom layouts, by extending
DialogFragment and creating a AlertDialog in the onCreateDialog() callback method.
For example, here's a basic AlertDialog that's managed within a DialogFragment:

public class MyActivity extends DialogFragment {

@Override
public Dialog onCreateDialog(Bundle savedInstanceState) {
// Use the Builder class for convenient dialog construction
AlertDialog.Builder builder = new AlertDialog.Builder
(getActivity());
builder.setMessage(“Do you want to Exit?”)
.setPositiveButton(“YES”, new
DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int id) {
// your stuffs
}
})
.setNegativeButton(“NO”, new
DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int id) {
// User cancelled the dialog
}
});
// Create the AlertDialog object and return it
return builder.create();
}
}

Figure 5-14. Output Demonstrating DialogFragment

25
Building an Alert Dialog
There are three regions of an alert dialog:
Title
This is optional and should be used only when the content area is occupied by a detailed
message, a list, or custom layout. If you need to state a simple message or question (such
as the dialog in figure 1), you don't need a title.
Content area
This can display a message, a list, or other custom layout.
Action buttons
There should be no more than three action buttons in a dialog.

FirstActivity.java

public class FirstActivity extends Activity{

Button btnClick;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
btnClick=findViewById(R.id.btnClick);

btnClick.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
showDialog();
}
});

public void showDialog(){

AlertDialog.Builder builder = new AlertDialog.Builder
(FirstActivity.this);
builder.setTitle("Exit App");
builder.setMessage("Do you want to exit App?");
builder.setCancelable(true);

builder.setPositiveButton(
"Yes",
new DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int id) {
//your stuffs
}
});
builder.setNegativeButton(
"No",
new DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int id) {
dialog.cancel();
}
});
AlertDialog alert = builder.create();
alert.show();
}
}

26
first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

Above code produces following output:

Figure 5-15. Output Demonstrating Alert Dialog

27
Building Custom Dialog and Setting Dialog Content
To demonstrate this topic, I am going to create a custom layout file for a dialog. This file
contains two EditText for inputting two numbers and a Button. After clicking Button sum
of these numbers will be displayed in a TextView.
So, let’s begin by creating custom layout for dialog.

custom_dialog.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

first_activity.xml

<?xml version="1.0" encoding="utf-8"?>

<Button
android:layout_width="wrap_content"

28
android:layout_height="wrap_content"
android:text="Show Dialog"
android:layout_centerHorizontal="true"
android:layout_marginTop="20sp"
android:id="@+id/btnClick"
android:textSize="20sp" />

</RelativeLayout>

FirstActivity.java

public class FirstActivity extends Activity{

EditText edtFirst,edtSecond;
Button btnClick,btnCalculate;
TextView txtResult;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.first_activity);
btnClick=findViewById(R.id.btnClick);

btnClick.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
showDialog();
}
});

public void showDialog(){

AlertDialog.Builder builder = new AlertDialog.Builder
(FirstActivity.this);
builder.setTitle("Calculate Sum");
builder.setCancelable(true);

// Inflate and set the layout for the dialog

// Pass null as the parent view because it’s going in the dialog
layout
LayoutInflater inflater = getLayoutInflater();
View view=inflater.inflate(R.layout.custom_dialog, null);
builder.setView(view);

}
});

29
AlertDialog alert = builder.create();
alert.show();
}
}

Above code produces following output:

Figure 5-16. Output Demonstrating Custom Dialog

Exercise

1. What do you mean by fragment? Explain lifecycle of fragment in detail.

2. What do you mean by UI flexibility? Why UI needs to be flexible? Explain how
fragments help to make UI flexible.
3. How can you create UI fragment? Explain with example.
4. How can you create fragment class? Explain with example.
5. Develop an android application to demonstrate fragments.
6. What do you mean by fragment manager? Explain with example.
7. Develop an android application to display multiple fragments in activity using
fragment manager.
8. Develop an android application to calculate simple interest using fragment.

30
9. Develop an android application to calculate area and perimeter of rectangle. Your
application must calculate and display area in one fragment and perimeter in
another fragment.
10. Differentiate activity and fragment with example.
11. What do you mean by menu? Explain its types.
12. Develop an android application to demonstrate options menu.
13. Develop an android application to demonstrate context menu.
14. Develop an android application to demonstrate popup menu.
15. What do you mean by dialog box? Explain its types.
16. How can you create a dialog fragment? Explain with example.
17. Develop an android application to demonstrate alert dialog.
18. How can you open custom dialog on button click? Explain with example.
19. Develop an android application to calculate simple interest in a dialog.
20. Develop an android application to calculate area and perimeter of a rectangle in a
dialog.

31
Unit – 6
ListView, GridView and RecyclerView [6 Hrs]

ListView
Android ListView is a view which groups several items and display them in vertical
scrollable list. The list items are automatically inserted to the list using an Adapter that
pulls content from a source such as an array or database.

Figure 6-1. A ListView

An adapter actually bridges between UI components and the data source that fill data into
UI Component. Adapter holds the data and send the data to adapter view, the view can
take the data from adapter view and shows the data on different views like as spinner, list
view, grid view etc.

The ListView and GridView are subclasses of AdapterView and they can be populated by
binding them to an Adapter, which retrieves data from an external source and creates a
View that represents each data entry.

To display a list, you can include a list view in your layout XML file:

1
Following are the attributes associated with ListView:

android:divider Drawable or color to draw between list items.

android:dividerHeight Height of the divider.
android:entries Reference to an array resource that will populate the
ListView.
android:footerDividersEnabled When set to false, the ListView will not draw the divider
before each footer view.
android:headerDividersEnabled When set to false, the ListView will not draw the divider after
each header view.

We can display items in ListView using ArrayAdapter as follows:

ArrayAdapter adapter = new ArrayAdapter<String>
(this,R.layout.ListView,R.id.TextView,StringArray);

• First argument this is the application context. Most of the case, keep it this.
• Second argument will be layout defined in XML file.
• Third argument is a TextView used for each string in the array.
• Final argument is an array of strings which will be populated in the TextView.

Once you have array adapter created, then simply call setAdapter() on
your ListView object as follows –

ListView listView = (ListView) findViewById(R.id.listview);

listView.setAdapter(adapter);

Features of ListView:
1. It displays a vertically-scrollable collection of views, where each view is positioned
immediately below the previous view in the list.
2. ListView uses Adapter classes which add the content from data source (such as
string array, array, database etc.)
3. ListView is a default scrollable which does not use other scroll view.
4. ListView is implemented by importing android.widget.ListView class.

Implementing ListView in an Application

Following example will demonstrate ListView. Here we are creating two layout file. One for
the ListView and another for list items to be displayed in a ListView. After creating layout
files, we use ArrayAdapter class to display String array in a ListView.

So, let’s begin by creating two layout files,

listview_example.xml

<?xml version="1.0" encoding="utf-8"?>

<RelativeLayout
xmlns:android="http://schemas.android.com/apk/res/android"

2
android:layout_width="match_parent"
android:layout_height="match_parent">

</RelativeLayout>

listview_items.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

Now we are creating a java file to for displaying String array in a ListView.

ListViewExample.java

public class ListViewExample extends AppCompatActivity {

ListView listView;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.listview_example);

listView=findViewById(R.id.mylist);
//creating string array
String names[]=
{"Ram","Shyam","Hari","Sita","Gita","Rita"};

//displaying list using ArrayAdapter

ArrayAdapter<String> adapter=new ArrayAdapter<String>
(this,R.layout.listview_items,R.id.text,names);
listView.setAdapter(adapter);

}
}

Above code produces following output:

3
Figure 6-2. Output Demonstrating ListView

Following code can be used for handling clicks in a ListView:

listView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
@Override
public void onItemClick(AdapterView<?> adapterView, View view, int
position, long l) {
//retrieving value
String value=adapter.getItem(position);
//displaying in Toast
Toast.makeText(getApplicationContext(),value,Toast.LENGTH_SHORT).
show();

}
});

Creating Custom ListView

After creating simple ListView, android also provides facilities to customize our ListView.
Like simple ListView, custom ListView also uses Adapter classes which added the content
from data source (such as string array, array, database etc). Adapter bridges data between
an AdapterViews and other Views.
To display a more custom view for each item in your dataset, extend ArrayAdapter and
create and configure the view for each data item in getView(...). Example is shown below:

4
custom_list.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

customlist_items.xml

<?xml version="1.0" encoding="utf-8"?>

5
MyListAdapter.java

public class MyListAdapter extends ArrayAdapter<String> {

Activity context;
String[] title;
String[] description;
int[] image;

public MyListAdapter(Activity context, String[] title, String[]

description, int[] image) {
//ArrayAdapter needs String so we are supplying title
super(context, R.layout.customlist_items,title);
this.context=context;
this.title=title;
this.description=description;
this.image=image;
}

public View getView(int position, View view, ViewGroup parent) {

LayoutInflater inflater=context.getLayoutInflater();
View rowView=inflater.inflate(R.layout.customlist_items,
null,true);

//wiring widgets
TextView txtTitle = (TextView) rowView.findViewById(R.id.title);
ImageView imageView = (ImageView) rowView.findViewById
(R.id.image);
TextView txtDescription = (TextView) rowView.findViewById
(R.id.description);

txtTitle.setText(title[position]);
imageView.setImageResource(image[position]);
txtDescription.setText(description[position]);

return rowView;

};
}

CustomListExample.java

public class CustomListExample extends AppCompatActivity {

ListView listView;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.custom_list);
listView=findViewById(R.id.mylist);

// creating arrays
String[] title={
"Title 1", "Title 2",
"Title 3", "Title 4"};
String[] description={
"This is description 1",
"This is description 2",
"This is description 3",
"This is description 4"
};

6
int[] image={
//Replace with different images
R.drawable.ic_launcher,
R.drawable.ic_launcher,
R.drawable.ic_launcher,
R.drawable.ic_launcher
};

//passing arrays to constructor of MyListAdapter

MyListAdapter adapter=new MyListAdapter
(this,title,description,image);
listView.setAdapter(adapter);

}
}

Above code produces following output:

Figure 6-3. Output Demonstrating Custom ListView

7
Handling clicks in Custom ListView

listView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
@Override
public void onItemClick(AdapterView<?> adapterView, View view, int
position, long l) {
//retrieving title and description
String title=adapter.title[position];
String descrption=adapter.description[position];

//handle click according to position

if(position==0){
//indicates first list item
}
if(position==1){
//indicated second list item
}

}
});

GridView
Android GridView shows items in two-dimensional scrolling grid (rows & columns). The
items in the grid come from the ListAdapter associated with this view.

Figure 6-4. GridView having 3 columns

8
Following are the attributes associated with GridView:

android:columnWidth Specifies the fixed width for each column.

android:gravity Specifies the gravity within each cell.
android:horizontalSpacing Defines the default horizontal spacing between columns.
android:numColumns Defines how many columns to show.
android:stretchMode Defines how columns should stretch to fill the available empty
space, if any.
android:verticalSpacing Defines the default vertical spacing between rows.

Features of GridView
1. GridView displays items in two-dimensional scrolling grid.
2. GridView uses Adapter classes which add the content from data source (such as
string array, array, database etc.)
3. GridView is a default scrollable which does not use other scroll view.
4. GridView is implemented by importing android.widget.GridView class.

Implementing GridView in an Application

Following example will demonstrate GridView. Here we are creating two layout file. One
for the GridView and another for grid items to be displayed in a GridView. After creating
layout files, we use ArrayAdapter class to display String array in a GridView.

So, let’s begin by creating two layout files,

gridview_example.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

gridview_items.xml

<?xml version="1.0" encoding="utf-8"?>

9
<TextView
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:textSize="20sp"
android:id="@+id/text"
android:textStyle="bold"
android:layout_margin="10dp" />

</RelativeLayout>

Now we are creating a java file to for displaying String array in a GridView.

GridViewExample.java

public class GridViewExample extends AppCompatActivity {

GridView gridView;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.gridview_example);

gridView =findViewById(R.id.mygrid);
//creating string array
String names[]=
{"Ram","Shyam","Hari","Sita","Gita"};

//displaying list using ArrayAdapter

ArrayAdapter<String> adapter=new ArrayAdapter<String>
(this,R.layout.gridview_items,R.id.text,names);
gridView.setAdapter(adapter);

}
}

Above code produces following output:

10
Figure 6-5. Output Demonstrating GridView

Following code can be used for handling clicks in a GridView:

gridView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
@Override
public void onItemClick(AdapterView<?> adapterView, View view, int
position, long l) {
//retrieving value
String value=adapter.getItem(position);
//displaying in Toast
Toast.makeText(getApplicationContext(),value,Toast.LENGTH_SHORT).
show();

}
});

Creating Custom GridView

After creating simple GridView, android also provides facilities to customize our GridView.
Like simple GridView, custom GridView also uses Adapter classes which added the content
from data source (such as string array, array, database etc). Adapter bridges data between
an AdapterViews and other Views.
To display a more custom view for each item in your dataset, extend ArrayAdapter and
create and configure the view for each data item in getView(...). Example is shown below:

11
custom_grid.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

customgrid_items.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

12
MyGridAdapter.java

public class MyGridAdapter extends ArrayAdapter<String> {

Activity context;
String[] title;
String[] description;
int[] image;

public MyGridAdapter(Activity context, String[] title, String[]

description, int[] image) {
//ArrayAdapter needs String so we are supplying title
super(context, R.layout.customgrid_items,title);
this.context=context;
this.title=title;
this.description=description;
this.image=image;
}

public View getView(int position, View view, ViewGroup parent) {

LayoutInflater inflater=context.getLayoutInflater();
View rowView=inflater.inflate(R.layout.customgrid_items,
null,true);

txtTitle.setText(title[position]);
imageView.setImageResource(image[position]);
txtDescription.setText(description[position]);

return rowView;

};
}

CustomGridExample.java

public class CustomGridExample extends AppCompatActivity {

GridView gridView;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.custom_grid);
gridView =findViewById(R.id.mygrid);

13
int[] image={
//Replace with different images
R.drawable.ic_launcher,
R.drawable.ic_launcher,
R.drawable.ic_launcher,
R.drawable.ic_launcher
};

//passing arrays to constructor of MyListAdapter

MyGridAdapter adapter=new MyGridAdapter
(this,title,description,image);
gridView.setAdapter(adapter);

}
}

Above code produces following output:

Figure 6-6. Output Demonstrating Custom GridView

14
Handling clicks in Custom GridView

gridView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
@Override
public void onItemClick(AdapterView<?> adapterView, View view, int
position, long l) {
//retrieving title and description
String title=adapter.title[position];
String descrption=adapter.description[position];

//handle click according to position

if(position==0){
//indicates first list item
}
if(position==1){
//indicated second list item
}

}
});

RecyclerView
The RecyclerView widget is a more advanced and flexible version of ListView. If your app
needs to display a scrolling list of elements based on large data sets (or data that frequently
changes), you should use RecyclerView. RecyclerView is mostly used to design the user
interface with the fine-grain control over the lists and grids of android application. It was
introduced in Marshmallow.

Figure 6-7. RecyclerView Displaying elements in List and Grid

In the RecyclerView model, several different components work together to display your
data. The overall container for your user interface is a RecyclerView object that you add to
your layout. The RecyclerView fills itself with views provided by a layout manager that you

15
provide. You can use one of our standard layout managers (such as LinearLayoutManager
or GridLayoutManager), or implement your own.

The views in the list are represented by view holder objects. These objects are instances of
a class you define by extending RecyclerView.ViewHolder. Each view holder is in charge of
displaying a single item with a view. For example, if your list shows music collection, each
view holder might represent a single album. The RecyclerView creates only as many view
holders as are needed to display the on-screen portion of the dynamic content, plus a few
extra. As the user scrolls through the list, the RecyclerView takes the off-screen views and
rebinds them to the data which is scrolling onto the screen.

The view holder objects are managed by an adapter, which you create by extending
RecyclerView.Adapter. The adapter creates view holders as needed. The adapter also
binds the view holders to their data. It does this by assigning the view holder to a position,
and calling the adapter's onBindViewHolder() method. That method uses the view holder's
position to determine what the contents should be, based on its list position.

This RecyclerView model does a lot of optimization work so you don't have to:
• When the list is first populated, it creates and binds some view holders on either
side of the list. For example, if the view is displaying list positions 0 through 9, the
RecyclerView creates and binds those view holders, and might also create and bind
the view holder for position 10. That way, if the user scrolls the list, the next
element is ready to display.
• As the user scrolls the list, the RecyclerView creates new view holders as necessary.
It also saves the view holders which have scrolled off-screen, so they can be reused.
If the user switches the direction they were scrolling, the view holders which were
scrolled off the screen can be brought right back. On the other hand, if the user
keeps scrolling in the same direction, the view holders which have been off-screen
the longest can be re-bound to new data. The view holder does not need to be
created or have its view inflated; instead, the app just updates the view's contents
to match the new item it was bound to.
• When the displayed items change, you can notify the adapter by calling an
appropriate RecyclerView.Adapter.notify…() method. The adapter's built-in code
then rebinds just the affected items.

Following is an attribute associated with RecyclerView:

• RecyclerView_layoutManager, used to defining the layout of RecyclerView i.e.,
LinearLayout or GridLayout.

Features of RecyclerView
1. RecyclerView widget is a more advanced and flexible version of ListView. So, we
can use RecyclerView to display large dataset.
2. RecyclerView contains integrated animations for adding, updating and removing
items.
3. RecyclerView enforces the recycling of views by using the ViewHolder pattern.
4. RecyclerView supports both grids and lists.
5. RecyclerView supports vertical and horizontal scrolling.

16
Implementing RecyclerView in Application
To access the RecyclerView widget, you need to add following dependency to your project
as follows:
1. Open the build.gradle file for your app module.
2. Add the support library to the dependencies section

dependencies {
implementation 'com.android.support:recyclerview-v7:28.0.0'
}

Now you can add the RecyclerView to your layout file as follows:

<android.support.v7.widget.RecyclerView
android:id="@+id/my_recycler_view"
android:scrollbars="vertical"
android:layout_width="match_parent"
android:layout_height="match_parent"/>

Once you have added a RecyclerView widget to your layout, obtain a handle to the object,
connect it to a layout manager, and attach an adapter for the data to be displayed:

public class MyActivity extends Activity {

private RecyclerView recyclerView;
private RecyclerView.Adapter mAdapter;
private RecyclerView.LayoutManager layoutManager;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.my_activity);
recyclerView = (RecyclerView) findViewById
(R.id.my_recycler_view);

// use a linear layout manager

layoutManager = new LinearLayoutManager(this);
recyclerView.setLayoutManager(layoutManager);

// specify an adapter (see also next example)

mAdapter = new MyAdapter(myDataset);
recyclerView.setAdapter(mAdapter);
}
// ...
}

17
To feed all your data to the list, you must extend the RecyclerView.Adapter class as
follows:
public class MyAdapter extends
RecyclerView.Adapter<MyAdapter.MyViewHolder> {
//add stuffs for displaying dataset in recyclerview
}

Following example demonstrates RecyclerView. Here, we are creating three arrays for
name, address and image. We are going to display these arrays in RecyclerView.

We are starting by creating layout file for placing RecyclerView.

recyclerview_example.xml

<?xml version="1.0" encoding="utf-8"?>

<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerview"
android:scrollbars="vertical"
android:layout_width="match_parent"
android:layout_height="match_parent"/>

</RelativeLayout>

Now we are creating layout file for placing RecyclerView items.

recyclerview_items.xml

<?xml version="1.0" encoding="utf-8"?>

<TextView

18
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:textSize="18sp"
android:id="@+id/txtAddress"
android:text="Address"
android:layout_toRightOf="@+id/image"
android:layout_below="@+id/txtName" />

</RelativeLayout>

Now it’s time to create java files. Here we need to java classes one will be the Activity and
another is needed for creating Adapter for RecycerView.

RecyclerViewExample.java

public class RecyclerViewExample extends AppCompatActivity {

RecyclerView recyclerView;
RecyclerView.Adapter adapter;
RecyclerView.LayoutManager layoutManager;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.recyclerview_example);
recyclerView=findViewById(R.id.recyclerview);

//creating array
String[] name={
"Ram","Shyam","Hari",
"Gita","Sita"
};
String[] address={
"Birtamode","Kathmandu","Pokhara",
"Birtamode","Kathmandu"
};
int[] image={
R.drawable.ic_launcher,R.drawable.ic_launcher,
R.drawable.ic_launcher,R.drawable.ic_launcher,
R.drawable.ic_launcher
};

//setting layout manager

layoutManager=new LinearLayoutManager(this);
recyclerView.setLayoutManager(layoutManager);

//passing array to Adapter class

adapter=new RecyclerViewAdapter(this,name,address,image);
recyclerView.setAdapter(adapter);

}
}

19
RecyclerViewAdapter.java

public class RecyclerViewAdapter extends

RecyclerView.Adapter<RecyclerViewAdapter.ViewHolder> {
Activity context;
int[] image;
String[] name;
String[] address;

public RecyclerViewAdapter(Activity context,String[] name,

String[] address, int[] image){
this.name=name;
this.address=address;
this.image=image;
this.context=context;
}

@Override
public ViewHolder onCreateViewHolder(ViewGroup parent, int
viewType) {
LayoutInflater layoutInflater = LayoutInflater.from
(context);
View listItem= layoutInflater.inflate
(R.layout.recyclerview_items, parent, false);
ViewHolder viewHolder = new ViewHolder(listItem);
return viewHolder;
}

@Override
public void onBindViewHolder(ViewHolder holder, int position){
holder.txtName.setText(name[position]);
holder.txtAddress.setText(address[position]);
holder.imageView.setImageResource(image[position]);
}

@Override
public int getItemCount() {
return name.length;
}

public static class ViewHolder extends RecyclerView.ViewHolder{

TextView txtName,txtAddress;
ImageView imageView;
public ViewHolder(View itemView) {
super(itemView);
txtName = itemView.findViewById(R.id.txtName);
txtAddress = itemView.findViewById(R.id.txtAddress);
imageView = itemView.findViewById(R.id.image);
}
}
}

20
Above code produces following output:

Figure 6-8. Output Demonstrating RecyclerView

Following code snipped can be used if you want to display items in grid layout.

//setting layout manager

layoutManager=new GridLayoutManager(this,3);
//3 represents no. of columns
recyclerView.setLayoutManager(layoutManager);

Displaying Data Using MVC Pattern in RecyclerView

For this purpose, we need a model where data is to be stored. So, now I am going to create
a model named as MyData.java which contains all required variables i.e., name, address
and image.

MyData.java

public class MyData {

private String name;

private String address;
private int image;

public MyData(String name,String address,int image){

this.name=name;
this.address=address;
this.image=image;

21
}
public String getName(){
return name;
}
public String getAddress(){
return address;
}
public int getImage(){
return image;
}
}

RecyclerViewExample.java

public class RecyclerViewExample extends AppCompatActivity {

//filling data in model

ArrayList<MyData> data=new ArrayList<>();
data.add(new MyData("Ram","Birtamode",R.drawable.ic_launcher));
data.add(new MyData("Shyam","Kathmandu",R.drawable.ic_launcher));
data.add(new MyData("Hari","Pokhara",R.drawable.ic_launcher));
data.add(new MyData("Gita","Birtamode",R.drawable.ic_launcher));
data.add(new MyData("Sita","Kathmandu",R.drawable.ic_launcher));

//setting layout manager

layoutManager=new LinearLayoutManager(this);
recyclerView.setLayoutManager(layoutManager);

//passing array to Adapter class

adapter=new RecyclerViewAdapter(this,data);
recyclerView.setAdapter(adapter);

}
}

RecyclerViewAdapter.java

public class RecyclerViewAdapter extends

RecyclerView.Adapter<RecyclerViewAdapter.ViewHolder> {
Activity context;
ArrayList<MyData> data;

public RecyclerViewAdapter(Activity context, ArrayList<MyData> data){

this.context=context;
this.data=data;
}

@Override
public ViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {
LayoutInflater layoutInflater = LayoutInflater.from(context);
View listItem= layoutInflater.inflate

22
(R.layout.recyclerview_items, parent, false);
ViewHolder viewHolder = new ViewHolder(listItem);
return viewHolder;
}

@Override
public void onBindViewHolder(ViewHolder holder, int position) {
MyData current=data.get(position);
holder.txtName.setText(current.getName());
holder.txtAddress.setText(current.getAddress());
holder.imageView.setImageResource(current.getImage());
}

@Override
public int getItemCount() {
return data.size();
}
public static class ViewHolder extends RecyclerView.ViewHolder {
TextView txtName,txtAddress;
ImageView imageView;
public ViewHolder(View itemView) {
super(itemView);
txtName = itemView.findViewById(R.id.txtName);
txtAddress = itemView.findViewById(R.id.txtAddress);
imageView = itemView.findViewById(R.id.image);
}
}
}

Above code will produce following output:

Figure 6-9. Output Demonstrating RecyclerView using MVC Pattern

23
Handling clicks in RecyclerView

@Override
public void onBindViewHolder(ViewHolder holder, int position) {
final MyData current=data.get(position);
holder.txtName.setText(current.getName());
holder.txtAddress.setText(current.getAddress());
holder.imageView.setImageResource(current.getImage());

//handling clicks
holder.imageView.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
//retieving data
String name=current.getName();
String address=current.getAddress();

Toast.makeText(context,name,Toast.LENGTH_SHORT).show();
}
});

Exercise

1. What do you mean by ListView? Explain its features.

2. What do you mean by GridView? Explain its features.
3. What do you mean by RecyclerView? Explain its features.
4. Differentiate ListView and GridView with example.
5. Differentiate ListView and RecyclerView with example.
6. Why RecyclerView is recommended over ListView? Explain with example.
7. Develop an android application to display id, name and address of 5 students using
ListView.
8. Develop an android application to display image, name and address of 5 students
using GridView.
9. Write a code snippet for retrieving data from ListView and GridView.
10. Develop an image gallery using GridView. Your gallery should display at least 5
drawable images. If any of the image is clicked it should be displayed in another
activity in large size.
11. Develop an android application for the same information given in question no. 7
using RecyclerView.
12. Develop an android application for the same information given in question no. 8
using RecyclerView (use MVC pattern).
13. Develop an android application for the same information given in question no. 10
using RecyclerView.
14. Write a code snippet for retrieving data from RecyclerView.

24
Unit – 7
Advanced Android Concepts [10 Hrs]

Local Database with SQLite

SQLite is an open-source relational database i.e. used to perform database operations on
android devices such as storing, manipulating or retrieving persistent data from the
database. It is very lightweight database that comes with Android OS. It supports all the
relational database features. In order to access this database, you don't need to establish
any kind of connections for it like JDBC, ODBC etc.

The version of SQLite depends on the version of Android. See the following table:

Android API SQLite Version

API 27 3.19
API 26 3.18
API 24 3.9
API 21 3.8
API 11 3.7
API 8 3.6
API 3 3.5
API 1 3.4

Features of SQLite:
Following is a list of features which makes SQLite popular among other lightweight
databases:
o SQLite is totally free: SQLite is open-source. So, no license is required to work with
it.
o SQLite is server less: SQLite doesn't require a different server process or system to
operate.
o SQLite is very flexible: It facilitates you to work on multiple databases on the same
session on the same time.
o Configuration Not Required: SQLite doesn't require configuration. No setup or
administration required.
o SQLite is a cross-platform DBMS: You don't need a large range of different
platforms like Windows, Mac OS, Linux, and Unix. It can also be used on a lot of
embedded operating systems like Symbian, and Windows CE.
o Storing data is easy: SQLite provides an efficient way to store data.
o Variable length of columns: The length of the columns is variable and is not fixed.
It facilitates you to allocate only the space a field needs. For example, if you have a
varchar (200) column, and you put a 10 characters' length value on it, then SQLite
will allocate only 20 characters' space for that value not the whole 200 space.
o Provide large number of API's: SQLite provides API for a large range of
programming languages. For example: .Net languages (Visual Basic, C#), PHP, Java,
Objective C, Python and a lot of other programming language.

1
o SQLite is written in ANSI-C and provides simple and easy-to-use API.
o SQLite is available on UNIX (Linux, Mac OS-X, Android, iOS) and Windows (Win32,
WinCE, WinRT).

SQL vs SQLite

S.N. SQL SQLite

SQL is a Structured Query Language used to SQLite is an Embeddable Relational Database
1 query a Relational Database System. It is Management System which is written in ANSI-
written in C language. C.
SQL is a standard which specifies how a SQLite is file-based. It is different from other
relational schema is created, data is inserted SQL databases because unlike most other SQL
2 or updated in the relations, transactions are databases, SQLite does not have a separate
started and stopped, etc. server process.
Main components of SQL are Data Definition SQLite supports many features of SQL and has
3 Language(DDL) , Data Manipulation high performance and does not support
Language(DML), Embedded SQL and stored procedures.
Dynamic SQL.
SQL is Structured Query Language which is SQLite is a portable database resource. You
4 used with databases like MySQL, Oracle, have to get an extension of SQLite in whatever
Microsoft SQL Server, IBM DB2, etc. It is not language you are programming in to access
a database itself. that database. You can access all of the
desktop and mobile applications.
A conventional SQL database needs to be SQLite database system doesn’t provide such
5 running as a service like Oracle DB to functionalities.
connect to and provide a lot of
functionalities.
SQL is a query language which is used by SQLite is a database management system
6 different SQL databases. It is not a database itself which uses SQL.
itself.

Advantages and Disadvantages of SQLite

Following are the advantages of using SQLite:
1. Lightweight
SQLite is a very light weighted database so, it is easy to use it as an embedded
software with devices like televisions, Mobile phones, cameras, home electronic
devices, etc.
2. Better Performance
Reading and writing operations are very fast for SQLite database. It is almost 35%
faster than File system. It only loads the data which is needed, rather than reading
the entire file and hold it in memory. If you edit small parts, it only overwrites the
parts of the file which was changed.

2
3. No Installation Needed
SQLite is very easy to learn. You don’t need to install and configure it. Just download
SQLite libraries in your computer and it is ready for creating the database.
4. Reliable
It updates your content continuously so, little or no work is lost in a case of power
failure or crash. SQLite is less bugs prone rather than custom written file I/O codes.
SQLite queries are smaller than equivalent procedural codes so, chances of bugs
are minimal.
5. Portable
SQLite is portable across all 32-bit and 64-bit operating systems and big- and little-
endian architectures. Multiple processes can be attached with same application file
and can read and write without interfering each other. It can be used with all
programming languages without any compatibility issue.
6. Accessible
SQLite database is accessible through a wide variety of third-party tools. SQLite
database's content is more likely to be recoverable if it has been lost. Data lives
longer than code.
7. Reduce Cost and Complexity
It reduces application cost because content can be accessed and updated using
concise SQL queries instead of lengthy and error-prone procedural queries. SQLite
can be easily extended in in future releases just by adding new tables and/or
columns. It also preserves the backwards compatibility.

Following are the disadvantages of using SQLite:

1. SQLite is used to handle low to medium traffic HTTP requests.
2. Database size is restricted to 2GB in most cases.

Establishing Connection
To use SQLite database in android two classes are used for creating database and
manipulating data. They are SQLiteOpenHelper and SQLiteDatabase class.

The SQLiteOpenHelper class is used for database creation and version management. For
performing any database operation, you have to provide the implementation
of onCreate() and onUpgrade() methods of SQLiteOpenHelper class.

There are many methods in SQLiteOpenHelper class. Some of them are as follows:

Method Description
public abstract void onCreate(SQLiteDatabase called only once when database is created for
db) the first time.
public abstract void onUpgrade(SQLiteDatabase called when database needs to be upgraded.
db, int oldVersion, int newVersion)
public synchronized void close () closes the database object.
public void onDowngrade(SQLiteDatabase db, called when database needs to be
int oldVersion, int newVersion) downgraded.

3
SQLiteDatabase class contains methods to be performed on SQLite database such as
create, update, delete, select etc. There are many methods in SQLiteDatabase class. Some
of them are as follows:

Method Description
void execSQL(String sql) executes the sql query not select query. Basically used for
creating database and tables.
long insert(String table, String inserts a record on the database. The table specifies the
nullColumnHack, ContentValues table name, nullColumnHack doesn't allow completely
values) null values. If second argument is null, android will store
null values if values are empty. The third argument
specifies the values to be stored.
int update(String table, updates a row.
ContentValues values, String
whereClause, String[] whereArgs)
Cursor rawQuery(String query, returns a cursor over the result set.
String[] selectionArgs)

Creating Database and Tables

Following code snippet will create SQLite Database and Table in android:

public class MyDbHelper extends SQLiteOpenHelper{

// Database Version
private static final int DATABASE_VERSION = 1;
// Database Name
private static final String DATABASE_NAME = "mydb";

public MyDbHelper(Context context) {

super(context, DATABASE_NAME, null, DATABASE_VERSION);
}

// Creating Tables
@Override
public void onCreate(SQLiteDatabase db) {
// create notes table
String createQuery="CREATE TABLE mytable(id INTEGER PRIMARY
KEY,name TEXT,address TEXT)";
db.execSQL(createQuery);
}

// Upgrading database
@Override
public void onUpgrade(SQLiteDatabase db, int oldVersion, int
newVersion) {
// Drop older table if existed
db.execSQL("DROP TABLE IF EXISTS " + DATABASE_NAME);
// Create tables again
onCreate(db);
}
}

4
Data Manipulation
Following code snippet can be used to perform various manipulation operation like insert,
update, select and delete.

//code to insert data

public void insertData(int id,String name, String address){
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues=new ContentValues();
contentValues.put("id",id);
contentValues.put("name",name);
contentValues.put("address",address);
//inserting row
db.insert("mytable",null,contentValues);
db.close();
}

//code to select data

public Cursor selectData(){
SQLiteDatabase db=this.getReadableDatabase();
String query="SELECT * FROM mytable";
Cursor cursor=db.rawQuery(query,null);
return cursor;
}

//code to update data

public void updateData(String id,String name, String address){
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues=new ContentValues();
contentValues.put("name",name);
contentValues.put("address",address);
//updating row
db.update("mytable",contentValues,"id=?",new String[]{id});
db.close();
}

//code to delete data

public void deleteData(String id) {
SQLiteDatabase db = this.getWritableDatabase();
//deleting row
db.delete("mytable","id=?",new String[]{id});
}

Following example will demonstrate the use of SQLite in Android. In this example, we are
creating three columns id, name and address in database table. Also we are creating
effective UI for showing different data manipulation operations.

So, let’s start by designing UI.

sqlite_example.xml

<?xml version="1.0" encoding="utf-8"?>

5
<EditText
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:hint="Enter Id"
android:inputType="number"
android:id="@+id/edtId" />

<TextView
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:text="Selected Data:"
android:layout_below="@+id/btnSelect"

6
android:layout_marginTop="10dp"
android:id="@+id/txtData"
android:textSize="18sp" />

</RelativeLayout>

Now we are creating Helper class for SQLite operations by extending SQLiteOpenHelpter
as follows:

public class MyDbHelper extends SQLiteOpenHelper{

// Database Version
private static final int DATABASE_VERSION = 1;
// Database Name
private static final String DATABASE_NAME = "mydb";

public MyDbHelper(Context context) {

super(context, DATABASE_NAME, null, DATABASE_VERSION);
}

//code to insert data

//code to select data

public Cursor selectData(){
SQLiteDatabase db=this.getReadableDatabase();
String query="SELECT * FROM mytable";
Cursor cursor=db.rawQuery(query,null);
return cursor;
}

//code to update data

public void updateData(String id,String name, String address){

7
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues=new ContentValues();
contentValues.put("name",name);
contentValues.put("address",address);
//updating row
db.update("mytable",contentValues,"id=?",new String[]{id});
db.close();
}

//code to delete data

public void deleteData(String id) {
SQLiteDatabase db = this.getWritableDatabase();
//deleting row
db.delete("mytable","id=?",new String[]{id});
}
}

Now finally we are creating Activity named as “SqliteExample.java” to perform various

data manipulation operations:

public class SqliteExample extends AppCompatActivity {

EditText edtId,edtName,edtAddress;
Button btnInsert,btnSelect,btnUpdate,btnDelete;
TextView txtData;
MyDbHelper myDbHelper;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.sqlite_example);

//creating object of MyDbHelper class

myDbHelper=new MyDbHelper(this);

edtId=findViewById(R.id.edtId);
edtName=findViewById(R.id.edtName);
edtAddress=findViewById(R.id.edtAddress);
btnInsert=findViewById(R.id.btnInsert);
btnUpdate=findViewById(R.id.btnUpdate);
btnSelect=findViewById(R.id.btnSelect);
btnDelete=findViewById(R.id.btnDelete);
txtData=findViewById(R.id.txtData);

btnInsert.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
int id=Integer.parseInt(edtId.getText().toString());
String name=edtName.getText().toString();
String address=edtAddress.getText().toString();
//calling insert function
myDbHelper.insertData(id,name,address);
Toast.makeText(getApplicationContext(),"Data Inserted
Successfully !", Toast.LENGTH_SHORT).show();
}
});

btnSelect.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
//retrieving data
int id=0;

8
String name="",address="";
//calling select function
Cursor cursor=myDbHelper.selectData();
while (cursor.moveToNext()){
id=cursor.getInt(0);
name=cursor.getString(1);
address=cursor.getString(2);
}
//displaying data in TextView
txtData.setText("Id="+id+"\t Name="+name+"\tAddress="
+address);
}
});

btnUpdate.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
String id=edtId.getText().toString();
String name=edtName.getText().toString();
String address=edtAddress.getText().toString();
//calling insert function
myDbHelper.updateData(id,name,address);
Toast.makeText(getApplicationContext(),"Data Updated
Successfully !",Toast.LENGTH_SHORT).show();
}
});

btnDelete.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
String id=edtId.getText().toString();
//calling delete function
myDbHelper.deleteData(id);
Toast.makeText(getApplicationContext(),"Data Deleted
Successfully !",Toast.LENGTH_SHORT).show();
}
});

}
}

Above code produces following output:

9
Figure 7-1. Output demonstrating various operation using SQLite

Displaying data in ListView

In above example, we have created TextView for displaying data. The problem with above
TextView is that we are able to display only one row at a time. To overcome this problem,
we can use widgets like ListView, GridView and RecyclerView to display multiple rows at a
time.
Here, in this example we are using ListView widget to display our data.

list_items.xml

<?xml version="1.0" encoding="utf-8"?>

<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:textSize="20sp"
android:layout_margin="10dp"
android:text="Id"
android:textStyle="bold"

10
android:id="@+id/txtId" />

</RelativeLayout>

sqlite_example.xml

<?xml version="1.0" encoding="utf-8"?>

11
<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_below="@+id/edtAddress"
android:layout_toRightOf="@+id/btnInsert"
android:id="@+id/btnSelect"
android:layout_marginLeft="10dp"
android:text="Select" />

</RelativeLayout>

ListAdapter.java

public class ListAdapter extends ArrayAdapter<String> {

Activity context;
ArrayList<Integer> id;
ArrayList<String> name;
ArrayList<String> address;

public ListAdapter(Activity context, ArrayList<Integer> id,

ArrayList<String> name, ArrayList<String> address) {
//ArrayAdapter needs String so we are supplying title
super(context, R.layout.list_items,name);
this.context=context;
this.id=id;
this.name=name;

12
this.address=address;
}

public View getView(int position, View view, ViewGroup parent) {

LayoutInflater inflater=context.getLayoutInflater();
View rowView=inflater.inflate(R.layout.list_items, null,true);
//wiring widgets
TextView txtId = (TextView) rowView.findViewById(R.id.txtId);
TextView txtName = (TextView) rowView.findViewById(R.id.txtName);
TextView txtAddress = (TextView) rowView.findViewById
(R.id.txtAddress);

txtId.setText(id.get(position).toString());
txtName.setText(name.get(position).toString());
txtAddress.setText(address.get(position).toString());

return rowView;

};
}

SqliteExample.java

public class SqliteExample extends AppCompatActivity {

EditText edtId,edtName,edtAddress;
Button btnInsert,btnSelect,btnUpdate,btnDelete;
MyDbHelper myDbHelper;
ListView listView;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.sqlite_example);

//creating object of MyDbHelper class

myDbHelper=new MyDbHelper(this);

btnSelect.setOnClickListener(new View.OnClickListener() {
@Override

13
public void onClick(View view) {
//creating dynamic array using Arraylist
//array is not suitable for this example
ArrayList<Integer> id=new ArrayList<>();
ArrayList<String> name=new ArrayList<>();
ArrayList<String> address=new ArrayList<>();
//calling select function
Cursor cursor=myDbHelper.selectData();
while (cursor.moveToNext()){
id.add(cursor.getInt(0));
name.add(cursor.getString(1));
address.add(cursor.getString(2));
}
ListAdapter adapter=new ListAdapter
(SqliteExample.this,id,name,address);
listView.setAdapter(adapter);
}
});

}
}

Above code produces following output:

14
Figure 7-2. Output demonstrating displaying retrieved data in ListView

Displaying data in RecyclerView

Like in ListView we can also plot retrieved data in RecyclerView as follows:

sqlite_example.xml

<?xml version="1.0" encoding="utf-8"?>

<EditText
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:hint="Enter Name"

15
android:layout_below="@+id/edtId"
android:id="@+id/edtName" />

<android.support.v7.widget.RecyclerView
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:id="@+id/recyclerview"
android:layout_below="@+id/txtData" />

</RelativeLayout>

16
DataModel.java

public class DataModel {

private int id;
private String name;
private String address;

public DataModel(int id, String name, String address){

this.id=id;
this.name=name;
this.address=address;
}

public int getId(){

return id;
}

public String getName(){

return name;
}

public String getAddress(){

return address;
}
}

RecyclerViewAdapter.java

public class RecyclerViewAdapter extends

RecyclerView.Adapter<RecyclerViewAdapter.ViewHolder> {
Activity context;
ArrayList<DataModel> data;

public RecyclerViewAdapter(Activity context, ArrayList<DataModel>

data){
this.context=context;
this.data=data;
}

@Override
public ViewHolder onCreateViewHolder(ViewGroup parent, int viewType)
{
LayoutInflater layoutInflater = LayoutInflater.from(context);
View listItem= layoutInflater.inflate(R.layout.list_items,
parent, false);
ViewHolder viewHolder = new ViewHolder(listItem);
return viewHolder;
}

@Override
public void onBindViewHolder(ViewHolder holder, int position) {
final DataModel current=data.get(position);
holder.txtId.setText(current.getId()+"");
holder.txtName.setText(current.getName());
holder.txtAddress.setText(current.getAddress());
}

17
@Override
public int getItemCount() {
return data.size();
}

public static class ViewHolder extends RecyclerView.ViewHolder {

TextView txtId,txtName,txtAddress;
ImageView imageView;
public ViewHolder(View itemView) {
super(itemView);
txtId = itemView.findViewById(R.id.txtId);
txtName = itemView.findViewById(R.id.txtName);
txtAddress = itemView.findViewById(R.id.txtAddress);
}
}
}

SqliteExample.java

public class SqliteExample extends AppCompatActivity {

EditText edtId,edtName,edtAddress;
Button btnInsert,btnSelect,btnUpdate,btnDelete;
MyDbHelper myDbHelper;
RecyclerView recyclerView;
RecyclerView.Adapter recyclerViewAdapter;
RecyclerView.LayoutManager layoutManager;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.sqlite_example);

//creating object of MyDbHelper class

myDbHelper=new MyDbHelper(this);

btnSelect.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {

18
ArrayList<DataModel> data=new ArrayList<>();
//calling select function
Cursor cursor=myDbHelper.selectData();
while (cursor.moveToNext()){
int id=cursor.getInt(0);
String name=cursor.getString(1);
String address=cursor.getString(2);
DataModel dataModel=new DataModel(id,name,address);
data.add(dataModel);
}
//plotting in recyclerview
layoutManager=new LinearLayoutManager
(SqliteExample.this);
recyclerView.setLayoutManager(layoutManager);
recyclerViewAdapter=new RecyclerViewAdapter
(SqliteExample.this,data);
recyclerView.setAdapter(recyclerViewAdapter);
}
});

}
}

Above code produces following output:

19
Figure 7-3. Output demonstrating displaying retrieved data in RecyclerView

Introduction to API
API is an abbreviation for Application Programming Interface which is a collection of
communication protocols and subroutines used by various programs to communicate
between them. A programmer can make use of various API tools to make its program easier
and simpler. Also, an API facilitates the programmers with an efficient way to develop their
software programs.

Thus in simpler terms, an API helps two programs or applications to communicate with
each other by providing them with necessary tools and functions. It takes the request from
the user and sends it to the service provider and then again sends the result generated
from the service provider to the desired user.

A developer extensively uses API’s in his software to implement various features by using
an API call without writing the complex codes for the same. We can create an API for an
operating system, database systems, hardware system, for a JavaScript file or similar object
oriented files. Also, an API is similar to a GUI (Graphical User Interface) with one major
difference. Unlike GUI’s, an API helps the software developers to access the web tools while
a GUI helps to make a program easier to understand by the users.

20
Real life example of an API:
Suppose, we are searching for a hotel room on an online website. In this case, you have a
vast number of options to choose from and this may include the hotel location, the check-
in and check-out dates, price, accommodation details and many more factors. So in order
to book the room online, you need to interact with the hotel booking’s website which in
further will let you know if there is a room available on that particular date or not and at
what price.
Now in the above example, the API is the interface that actually communicates in between.
It takes the request of the user to the hotel booking’s website and in turn returns back the
most relevant data from the website to the intended user. Thus, we can see from this
example how an API works and it has numerous applications in real life from switching on
mobile phones to maintaining a large amount of databases from any corner of the world.

Types of API
There are various kinds of API’s available according to their uses and applications like the
Browser API which is created for the web browsers to abstract and to return the data from
surroundings or the Third party API’s, for which we have to get the codes from other sites
on the web (e.g. Facebook, Twitter).

There are three basic forms of API-

1. Web APIs:
A Web API also called as Web Services is an extensively used API over the web and
can be easily accessed using the HTTP protocols. A Web API is an open source
interface and can be used by a large number of clients through their phones,
tablets. or PC’s.

Figure 7-4. Web API

2. Local APIs:
In this types of API, the programmers get the local middleware services. TAPI
(Telephony Application Programming Interface), .NET are common examples of
Local API’s.
3. Program APIs:
It makes a remote program appears to be local by making use of RPC’s (Remote
Procedural Calls). SOAP is a well-known example of this type of API.

21
Few other types of APIs:
• SOAP (SIMPLE OBJECT ACCESS PROTOCOL): It defines messages in XML format
used by web applications to communicate with each other.
• REST (Representational State Transfer): It makes use of HTTP to GET, POST, PUT,
or DELETE data. It is basically used to take advantage of the existing data.
• JSON-RPC: It use JSON for data transfer and is a light-weight remote procedural call
defining few data structure types.
• XML-RPC: It is based on XML and uses HTTP for data transfer. This API is widely used
to exchange information between two or more networks.

Advantages and Disadvantages of API

Following are the advantages of APIs:

• Efficiency: API produces efficient, quicker and more reliable results than the
outputs produced by human beings in an organization.
• Flexible delivery of services: API provides fast and flexible delivery of services
according to developer’s requirements.
• Integration: The best feature of API is that it allows movement of data between
various sites and thus enhances integrated user experience.
• Automation: As API makes use of robotic computers rather than humans, it
produces better and automated results.
• New functionality: While using API the developers find new tools and functionality
for API exchanges.

Following are the disadvantages of APIs:

• Cost: Developing and implementing API is costly at times and requires high
maintenance and support from developers.
• Security issues: Using API adds another layer of surface which is then prone to
attacks, and hence the security risk problem is common in API’s.

Introduction to JSON
JSON — short for JavaScript Object Notation — is a format for sharing data. As its name
suggests, JSON is derived from the JavaScript programming language, but it’s available for
use by many languages including Python, Ruby, PHP, and Java.

JSON uses the .json extension when it stands alone. When it’s defined in another file
format (as in .html), it can appear inside of quotes as a JSON string, or it can be an object
assigned to a variable. This format is easy to transmit between web server and client or
browser.

Very readable and lightweight, JSON offers a good alternative to XML and requires much
less formatting. This informational guide will get you up to speed with the data you can use
in JSON files, and the general structure and syntax of this format.

22
A JSON object looks something like this:

{
"sid" : "111",
"name" : "Raazu Poudel",
"address" : "Birtamode"
}

Although this is a very short example, and JSON could be many lines long, this shows that
the format is generally set up with two curly braces (or curly brackets) that look like this
{ } on either end of it, and with key-value pairs populating the space between. Most data
used in JSON ends up being encapsulated in a JSON object.

Key-value pairs have a colon between them as in "key" : "value". Each key-value pair is
separated by a comma, so the middle of a JSON looks like this: "key" : "value", "key" :
"value", "key": "value". In our example above, the first key-value pair is "sid" : "111".

Encoding and Decoding JSON

Encoding using PHP

In this example, we are using PHP language for creating JSON. At first we select data from
table of the database and after selecting data we encode than data in JSON format. We are
using localhost as a server for this purpose.

getdata.php

<?php
$server="localhost";
$username="root";
$password="";
$database="bcatest";

// Create connection
$conn = new mysqli($server, $username, $password,$database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

23
//retrieving data
$sql = "SELECT * FROM student";
$result = $conn->query($sql);

//encoding data in json format

$json = array();
if($result->num_rows>0){
while ($row = $result->fetch_array()) {
$json["data"][]=array("sid"=>$row["sid"],"name"=>$row["name"],
"address"=>$row["address"]);
}
}

echo json_encode($json);
$conn->close();
?>

Testing in browser:

Decoding JSON using in mobile application using Java

DecodingJSON.java

public class DecodingJSON extends Activity{

@Override
protected void onCreate(Bundle b){
super.onCreate(b);
decodeJson();
}

public void decodeJson(){

try{

//copy paste json string

String json_data="{\n" +
" \"data\": [\n" +
" {\n" +
" \"sid\": \"6\",\n" +
" \"name\": \"Ram\",\n" +
" \"address\": \"Btm\"\n" +
" },\n" +
" {\n" +
" \"sid\": \"7\",\n" +
" \"name\": \"Hari\",\n" +
" \"address\": \"Ktm\"\n" +
" }\n" +

24
" ]\n" +
"}";

//decoding JSON
JSONObject result=new JSONObject(json_data);
JSONArray data=result.getJSONArray("data");

for(int i=0;i<data.length();i++){
//fetching each row
JSONObject student=data.getJSONObject(i);
int sid=student.getInt("sid");
String name=student.getString("name");
String address=student.getString("address");

//displaying data
Log.d("Row "+i,sid+" "+name+" "+address);
}
}catch (Exception ex){
Log.d("exception",ex.toString());
}
}
}

Above code produces following output in Logcat:

Retrieving Contents Form Remote Server

For communicating with server, we are using Volley Library in our application. Volley is an
HTTP library that makes networking for Android apps easier and most importantly, faster.

Volley offers the following benefits:

• Automatic scheduling of network requests.
• Multiple concurrent network connections.
• Transparent disk and memory response caching.
• Support for request prioritization.
• Cancellation request API. You can cancel a single request, or you can set blocks or
scopes of requests to cancel.
• Ease of customization, for example, for retry and back off.
• Strong ordering that makes it easy to correctly populate your UI with data fetched
asynchronously from the network.
• Debugging and tracing tools.

25
To use volley in your application, we need to add following dependency in our project:

dependencies {
...
implementation 'com.android.volley:volley:1.1.1'
}

Also, to use Volley, you must add the android.permission.INTERNET permission to your
app's manifest. Without this, your app won't be able to connect to the network.

<uses-permission android:name="android.permission.INTERNET"/>

public void volleyRequest(){

// Instantiate the RequestQueue.
RequestQueue queue = Volley.newRequestQueue(this);
//url for localhost
String url ="http://10.0.2.2/myproject/getdata.php";

// Request a string response from the provided URL.

StringRequest stringRequest = new StringRequest(Request.Method.GET, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
//displaying response string in logcat
Log.d("result",response);
}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
//displaying error response message
Log.d("exception",error.toString());
}
});

// Add the request to the RequestQueue.

queue.add(stringRequest);
}

26
Displaying Retrieved data in RecyclerView

json_example.xml

<?xml version="1.0" encoding="utf-8"?>

<android.support.v7.widget.RecyclerView
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:id="@+id/recyclerview" />

</RelativeLayout>

list_items.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

27
DataModel.java

public class DataModel {

private int id;
private String name;
private String address;

public DataModel(int id, String name, String address){

this.id=id;
this.name=name;
this.address=address;
}

public int getId(){

return id;
}

public String getName(){

return name;
}

public String getAddress(){

return address;
}
}

RecyclerViewAdapter.java

public class RecyclerViewAdapter extends

RecyclerView.Adapter<RecyclerViewAdapter.ViewHolder> {
Activity context;
ArrayList<DataModel> data;

public RecyclerViewAdapter(Activity context, ArrayList<DataModel>

data){
this.context=context;
this.data=data;
}

@Override
public ViewHolder onCreateViewHolder(ViewGroup parent, int viewType)
{
LayoutInflater layoutInflater = LayoutInflater.from(context);
View listItem= layoutInflater.inflate(R.layout.list_items,
parent, false);
ViewHolder viewHolder = new ViewHolder(listItem);
return viewHolder;
}

28
@Override
public int getItemCount() {
return data.size();
}

public static class ViewHolder extends RecyclerView.ViewHolder {

JsonExample.java

public class JsonExample extends AppCompatActivity{

RecyclerView recyclerView;
RecyclerView.Adapter recyclerAdapter;
RecyclerView.LayoutManager layoutManager;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.json_example);
recyclerView=findViewById(R.id.recyclerview);
volleyRequest();
}

public void volleyRequest(){

// Instantiate the RequestQueue.
RequestQueue queue = Volley.newRequestQueue(this);
//url for localhost
String url ="http://10.0.2.2/myproject/getdata.php";

// Request a string response from the provided URL.

StringRequest stringRequest = new StringRequest
(Request.Method.GET, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
//passing data for decoding
decodeJson(response);
}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
//displaying error response message
Log.d("exception",error.toString());
}
});

// Add the request to the RequestQueue.

queue.add(stringRequest);
}

29
public void decodeJson(String response){
try{
ArrayList<DataModel> data=new ArrayList<>();
JSONObject result=new JSONObject(response);
JSONArray array=result.getJSONArray("data");
for(int i=0;i<array.length();i++){
//fetching each row
JSONObject student=array.getJSONObject(i);
int sid=student.getInt("sid");
String name=student.getString("name");
String address=student.getString("address");
DataModel dataModel=new DataModel(sid,name,address);
data.add(dataModel);
}

//plotting data in recyclerview

layoutManager=new LinearLayoutManager(this);
recyclerView.setLayoutManager(layoutManager);
recyclerAdapter=new RecyclerViewAdapter
(JsonExample.this,data);
recyclerView.setAdapter(recyclerAdapter);

}catch (Exception ex){

Log.d("exception",ex.toString());
}
}
}

Above code produces following output:

Figure 7-5. Output Displaying retrieved contents from server in RecyclerView

30
Sending Contents to Remote Server
send_data.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

SendData.java

public class SendData extends AppCompatActivity {

EditText edtId,edtName,edtAddress;
Button btnSubmit;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.send_data);

edtId=findViewById(R.id.edtId);
edtName=findViewById(R.id.edtName);
edtAddress=findViewById(R.id.edtAddress);
btnSubmit=findViewById(R.id.btnSubmit);

31
btnSubmit.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
volleyRequest();
}
});

public void volleyRequest(){

// Instantiate the RequestQueue.
RequestQueue queue = Volley.newRequestQueue(this);
//url for localhost
String url ="http://10.0.2.2/myproject/setdata.php";
// Request a string response from the provided URL.
StringRequest stringRequest = new StringRequest
(Request.Method.POST, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
//displaying response message
Toast.makeText(getApplicationContext(),response,
Toast.LENGTH_LONG).show();
}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
//displaying error response message
Log.d("exception",error.toString());
}
}){
//sending data to server
@Override
protected HashMap<String,String> getParams(){
HashMap<String,String> params = new HashMap<>();
params.put("sid",edtId.getText().toString());
params.put("name",edtName.getText().toString());
params.put("address",edtAddress.getText().toString());
return params;
}

};;
// Add the request to the RequestQueue.
queue.add(stringRequest);
}
}

setdata.php

<?php

//getting post data

$sid=$_POST["sid"];
$name=$_POST["name"];
$address=$_POST["address"];

32
//server credentials
$server="localhost";
$username="root";
$password="";
$database="bcatest";
// Create connection
$conn = new mysqli($server, $username, $password,$database);
// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

//inserting data
$sql = "INSERT INTO student(sid,name,address)
VALUES('".$sid."','".$name."','".$address."')";
$result = $conn->query($sql);

if($result)
echo"Data Inserted Successfully !";
else
echo"Failed to Insert Data !";
$conn->close();
?>

Above code produces following output:

Figure 7-6. Sending data to remote server

33
Implementing Google Maps in Android Application
Android allows us to integrate Google Maps in our application. For this Google provides us
a library via Google Play Services for using maps. In order to use the Google Maps API, you
must register your application on the Google Developer Console and enable the API.

Steps for Getting Google Maps API Key

An API key is needed to access the Google Maps servers. This key is free and you can use
it with any of your applications. If you haven’t created project, you can follow the below
steps to get started:

Step 1: Open Google developer console and sign in with your Gmail
account: https://console.developers.google.com/project

Step 2: Now create new project. You can create new project by clicking on the Create
Project button and give name to your project.

Step 3: Now click on APIs & Services and open Dashboard from it.

Step 4: Now click Enable APIS AND SERICES.

34
Step 5: Now search for Google Map Android API and enable it.

Step 6: Now refresh page and go to Credentials.

Step 7: Now click on Create credentials and choose API key. It will create API key to
integrate maps in your application.

35
Step 8: Now API your API key will be generated. Copy it and save it somewhere as we will
need it when implementing Google Map in our Android project.

Developing Google Maps Application in Android

Following are the steps for integrating google maps in your application:

Step 1: Add following permission in your manifest file.

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>

Step 2: Add your generated API Key in your manifest file inside application tag as follows.

Step 3: Add following dependency in build.gradle file .

dependencies {
. . .
. . .
implementation 'com.google.android.gms:play-services-maps:15.0.1'
}

Step 4: Now create layout resource file to display google map.

map_activity.xml

<?xml version="1.0" encoding="utf-8"?>

<fragment xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/map"
android:name="com.google.android.gms.maps.SupportMapFragment"
tools:context=".MapsActivity"
android:layout_width="match_parent"

36
android:layout_height="match_parent" />

</RelativeLayout>

Step 5: Now finally create an Activity by implementing OnMapReadyCallback interface.

MapsActivity.java

public class MapsActivity extends AppCompatActivity implements

OnMapReadyCallback {
GoogleMap mMap;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.map_activity);

// Obtain the SupportMapFragment and get notified when the map is

ready to be used.
SupportMapFragment mapFragment = (SupportMapFragment).
getSupportFragmentManager().findFragmentById(R.id.map);
mapFragment.getMapAsync(this);
}

@Override
public void onMapReady(GoogleMap googleMap) {
mMap = googleMap;
// Adding latitude and longitude
LatLng location = new LatLng(26.644096, 87.989391);
//Adding red marker to point location
mMap.addMarker(new MarkerOptions().position(location).
title("Marker in Birtamode"));
//Moving camera to desired location
mMap.moveCamera(CameraUpdateFactory.newLatLng(location));
//Adding zoom effect
mMap.animateCamera(CameraUpdateFactory.zoomTo(12.0f) );
}
}

Following output will be produced after running application:

37
Figure 7-7. Output Demonstrating Google Map.

Procedure for Publishing Application in Google Play Store

To upload your application in google play store you must perform following tasks:
• First generate signed APK of your application.
• Upload signed APK in google play console.

Generating Signed APK for App Release

Following are the steps used to generate signed APK:

Note: Don’t use com.example…. as a package name because example is not supported by
play store. Instead you can rename your package name.

Step 1: Go to menu and select Build -> Generate Signed APK.

38
Step 2: Now click Create new keystore file. This keystore file is necessary to upload new
app and for updating existing app. If you have already created keystore file, then you can
click Choose existing keystore file.

Step 3: Now fill up information for creating new keystore file and click ok. Example is shown
below.
Note: Please remember keystore file, username and password because if it is lost, then
you will be unable to update your application.

39
Step 4: Now select V1 (Jar Signature) and click Finish. This will create signed APK for
release.

40
Step 5: Now click Event Log and locate to the folder where signed APK has been placed.
You can get your signed APK file inside release folder.

Upload Signed APK in Play Store

Following steps are used to upload signed APK to play store.

Step 1: Visit https://play.google.com/apps/publish/ to upload your app in play store.

Following page will be displayed.

Here you need to create your developer account for lifetime by paying $25 using your
credit card. There is no limitation for number of apps. You can upload multiple apps using
a single account.

Step 2: Once you’ve created developer account following page will be displayed on screen.
Click Create Application.

41
Step 3: Next, give your application a title and the default language. You will now be moved
to the Store listing screen.

In store listing page you must add everything related to how your app will look in the store.
Following information must be added in this page:
• A short description of your application
• A full description
• Screenshots (at least 2)
• A Hi Resolution Icon
• A Feature Graphic
• The application’s type and its category
• Your email
• Your privacy policy (if you don’t have one, check the Not submitting a privacy policy
checkbox)

Step 4: Now go to the App Releases page and click Create Release button. Following page
will be displayed on screen.

42
Here you can upload your signed APK. Here you can also give the release a name and
specify what is new in this release. Pay special attention to whatever you type in what is
new in this release because it will appear in the Play store under the What’s New section.
Once you are done, you can press the Review button on the lower right corner of the page.

Step 5: Next, Click Content Rating.

After pressing the Continue button, you will be asked several questions regarding the
content of your application. Just follow them in order, filling one by one.

43
Step 6: Last but not least, go to Pricing & distribution page. Be aware to fill in all the
required fields. In this last page, you can decide on:
• If your application will be free or not
• Which countries your application will be available to
• If it contains ads
• User programs

Step 7: After filling up all the information regarding Store Listings, Content Rating, Pricing
& Distribution etc. Now you can go to App Release page to publish your application. To
publish app in play store, click Rollout Button.

Exercise

1. What do you mean by SQLite? Explain its features.

2. Explain advantages and disadvantages of using SQLite.
3. Differentiate SQLite and SQL with example.
4. How can you establish connection using SQLite in android? Explain with the help of
suitable example.
5. Explain the process of creating Database and Tables using SQLite in android.
6. Develop an android application to demonstrate basic crud operation using SQLite.
7. Develop a to-do list application using SQLite.
8. Develop a phone directory application using SQLite.
9. Develop an android application which track your daily income and expenses. Also
your app should display daily savings.
10. What do you mean by API? Explain its types.
11. Define JSON. Explain JSON as a tool for creating API with example.

44
12. Explain the advantages of JSON over XML.
13. How do your communication your application with remote server? Explain with the
help of suitable example.
14. Develop an android application that demonstrates retrieval of contents from
remote server.
15. Develop an android application that demonstrates sending of contents to remote
server.
16. Develop a phone directory application (Phone records must be stored in remote
server).
17. Explain the procedure for generating API key for displaying google map in your
application.
18. Develop an android application that displays google map.
19. Explain the procedure for generating signed APK.
20. Explain the procedure for publishing signed APK in play store.

45
Unit -8
Introduction to iOS Programming [8 Hrs]

Introduction to iOS and iOS Programming

iOS (formerly iPhone OS) is a mobile operating system created and developed by Apple Inc.
exclusively for its hardware. It is the operating system that presently powers many of the
company's mobile devices, including the iPhone, and iPod Touch; it also powered the iPad
prior to the introduction of iPadOS in 2019. It is the second most popular mobile operating
system globally after Android.

Originally unveiled in 2007 for the iPhone, iOS has been extended to support other Apple
devices such as the iPod Touch (September 2007) and the iPad (January 2010). As of March
2018, Apple's App Store contains more than 2.1 million iOS applications, 1 million of which
are native for iPads. These mobile apps have collectively been downloaded more than 130
billion times.

The iOS user interface is based upon direct manipulation, using multi-touch gestures.
Interface control elements consist of sliders, switches, and buttons. Interaction with the
OS includes gestures such as swipe, tap, pinch, and reverse pinch, all of which have specific
definitions within the context of the iOS operating system and its multi-touch interface.
Internal accelerometers are used by some applications to respond to shaking the device
(one common result is the undo command) or rotating it in three dimensions (one common
result is switching between portrait and landscape mode). Apple has been significantly
praised for incorporating thorough accessibility functions into iOS, enabling users with
vision and hearing disabilities to properly use its products.

Major versions of iOS are released annually. On all recent iOS devices, iOS regularly checks
on the availability of an update, and if one is available, will prompt the user to permit its
automatic installation. The current version, iOS 13 was released to the public on 19
September 2019, introducing user interface tweaks and a dark mode, along with features
such as a redesigned Reminders app, a swipe keyboard, and an enhanced Photos app. iOS
13 does not support devices with less than 2 GB of RAM, including the iPhone 5s, iPod
Touch (6th generation), and the iPhone 6 and iPhone 6 Plus, which still make up over 10%
of all iOS devices. iOS 13 is exclusively for the iPhone and iPod touch as the iPad variant is
now called iPadOS.

iOS programming is a set of processes and procedures involved in writing software for
iPhone developed by Apple Inc.

iOS Platform
The iOS SDK (Software Development Kit) allows for the development of mobile apps on
iOS. While originally developing iPhone prior to its unveiling in 2007, Apple's then-CEO
Steve Jobs did not intend to let third-party developers build native apps for iOS, instead
directing them to make web applications for the Safari web browser. However, backlash
from developers prompted the company to reconsider with Jobs announcing in October

1
2007 that Apple would have a software development kit available for developers by
February 2008. The SDK was released on March 6, 2008.

The SDK is a free download for users of Mac personal computers. It is not available for
Microsoft Windows PCs. The SDK contains sets giving developers access to various
functions and services of iOS devices, such as hardware and software attributes. It also
contains an iPhone simulator to mimic the look and feel of the device on the computer
while developing. New versions of the SDK accompany new versions of iOS. In order to test
applications, get technical support, and distribute apps through App Store, developers are
required to subscribe to the Apple Developer Program.

Combined with Xcode, the iOS SDK helps developers write iOS apps using officially
supported programming languages, including Swift and Objective-C. Other companies have
also created tools that allow for the development of native iOS apps using their respective
programming languages.

The history of Apple iOS versions is discussed below:

• Apple iOS was originally known as iPhone OS. The company released three versions
of the mobile OS under that name before iOS 4 debuted in June 2010.
• On Oct. 12, 2011, Apple released iOS 5, which expanded the number of available
applications to over 500,000. This iOS version also added the Notification Center, a
camera app, Siri and more.
• Unveiled on June 11, 2012, iOS 6 included a Maps application and the Passbook
ticket storage and loyalty program application.
• Released on Sept. 18, 2013, iOS 7 featured an entirely redesigned user interface. In
September 2014, iOS 8 introduced Continuity, a cross-platform system that allows
users of multiple Apple devices to pick up on one where they left off from another.
Other new features included the Photos app and Apple Music.
• Apple iOS 9 and iOS 10 -- released, respectively, on Sept. 16, 2015, and Sept. 13,
2016 -- featured upgrades such as a revamped notifications section, improved
iMessage capabilities and Siri integration with third-party apps.

Environment Setup
For development of iOS applications, we need to install Xcode editor, its apple integrated
development environment (IDE). The Xcode editor is the primary development tool for any
type of apple platforms like OSX Software’s, iPhones App, Mac, etc.

The requirement of the Xcode editor is that we should have minimum Apple Laptop or Mac
Computer for development of iOS application. We can download Xcode editor from Apple
website or Apple app store and this editor is completely free we don’t need to pay
anything for Apple.

2
Creating an Xcode Project
With Xcode installed, it is time to launch it for the first time. If all went well, you should see
the Welcome to Xcode window, which contains a few useful links and helps you create a
new application. To create your first iOS application, select Create a new Xcode
project from the list of options.

Figure 8-1: Xcode Homepage

Xcode makes it easy to create a new Xcode project by offering a handful of useful project
templates. The Single View Application template is a good choice for your first application.
Select it from the list of iOS > Application templates and click Next.

3
Figure 8-2: Creating a Project

The next window lets you configure your Xcode project. Fill in the fields as shown in the
screenshot below and click Next.

4
Figure 8-3: Configuring a new Project

Once we click on Next button new dialog will open in that we need to select the location
to save our project. Once you select the location to save project then click on Create button
like as shown below.

5
Figure 8-4: Selecting project location

After click on Create button the Xcode will create and open a new project. By default, our
project structure will be like as shown below.

Figure 8-5: Xcode workspace window

6
Building the Interface
In our project Main.storyboard and ViewController.swift are the main files which we used
to design app user interface and to maintain source code.
• Main.storyboard - Its visual interface editor and we will use this file to design our
app user interface
• ViewController.swift - It contains source code of our application and we use this
file to write any code related to our app.

Now in project select Main.storyboard file the Xcode will open visual interface editor like
as shown below.

Figure 8-6: First look of Main.storyboard

Now select ViewController.swift file in your project that view will be like as shown below.

7
Figure 8-7: First look of ViewController.swift

Now we will add controls to our application for that open Object Library. The Object Library
will appear at the bottom of Xcode in right side. In case if you don't find Object library, click
on the button which is at the third position from the left in the library selector bar like as
shown below. (Alternatively you can choose View -> Utilities -> Show Object Library).

Figure 8-8: Opening object library

As we discussed our user interface will be in Main.storyboard file so open Main.storyboard

file. Now in Object library search for the label in Filter filed then drag and drop the label
into Main.storyboard ViewController like as shown below.

8
Figure 8-9: Adding label to the project

Now we will change the text of label for that click on label in right side the label properties
will open in Text property textbox write the “Hello World”. Once we change the label text
now we will change the position of label control for that select label control -> Click
on label control and just drag the label control like as shown below.

Figure 8-10: Adding text “Hello World” to label

9
Once we click and drag the label control we can able to see multiple properties like
“Center Horizontally in Container”, “Center Vertically in Container”, etc.
We will set “Center Horizontally in Container”, “Center Vertically in Container” properties
for label control to make our label appeared in centered position. Once we set these two
properties we can able to see two lines which appear like cross on our hello world label like
as shown below.

Figure 8-11: Centering the label

Running on the Simulator

To build and run our application we use Simulator in Xcode. The Simulator will help us to
know how our app will look and behave if it is running on device.
The Simulator in Xcode is having different device options to check our app in multiple
devices like iPad, iPhone with different screen sizes. By using these options, we can
simulate our app in any device and test its design and behavior based on our requirements.

Figure 8-12: Configuring Simulator

10
Once we select the required simulator then we will run our application by
using Run button, located in the top-left corner of the Xcode toolbar like as shown below.

Figure 8-13: Running Application on Simulator

Once we run the iOS hello world application we will get output like as shown below.

Figure 8-14: Output displayed in Simulator

Making Connections
A connection lets one object know where another object is in memory so that the two
objects can communicate. There are two kinds of connections that you can make in
Interface Builder: outlets and actions. An outlet is a reference to an object. An action is a
method that gets triggered by a button or some other view that the user can interact with,
like a slider or a picker.
For making connections you have to use iOS Outlets and Actions. In iOS Outlets and Actions
are basically the property symbol of IBoutlets and IBActions where IB called Interface
Builder. Outlet is basically the reference object and action is the method which is used to
perform some type of actions.
Following is the syntax of using iOS Actions and Outlets in applications.

@IBOutlet weak var labeltxt: UILabel!

@IBAction func buttonaction(sender: AnyObject) {
labeltxt.text = "Hello"
}

If you observe above syntax we used “@IBOutlet” to add reference of label control and
we used “@IBAction” to add button click action to change label control text.

11
To demonstrate connection, let’s take an example of an iOS application containing two
view controls (one label control and another button control). While clicking on the button
control we must be able to change text of label.
So, let’s begin by adding label and button controls in our storyboard.

Figure 8-15: Adding label and button

Now we will map our controls to ViewController.swift file for that we need to
use Assistant editor in Xcode. Open the Xcode editor in assistant mode for that click on
the overlap circle button in Xcode toolbar at top right side like as shown below.

Figure 8-16: Opening Assistant Editor

Now press Ctrl button in keyboard and drag the controls from your canvas to the code
display in ViewController.swift file like as shown below.

12
Figure 8-17: Connecting UI controls to application code

Once you drag the controls from viewcontroller to code in ViewController.swift file now
write code in @IBAction to change the label text when click on button. Once we make
required changes our ViewController.swift file should be like as shown below.

import UIKit
class ViewController: UIViewController {
@IBOutlet weak var labeltxt: UILabel!
@IBAction func buttonaction(sender: AnyObject) {
labeltxt.text = "We love BCA "
}
override func viewDidLoad() {
super.viewDidLoad()
// Do any additional setup after loading the view.
}
override func didReceiveMemoryWarning() {
super.didReceiveMemoryWarning()
// Dispose of any resources that can be recreated.
}
}

Once we run application click on button it will change the label text. The button performs
the action for label to change its outlet text.

Above code produces following output:

13
Figure 8-18: Output demonstrating connection

Introduction to Swift Language

Swift is a new language that Apple introduced in 2014. It replaces Objective-C as the
recommended development language for iOS and Mac. In this chapter, you are going to
focus on the basics of Swift. You will not learn everything, but you will learn enough to get
started. Then, as you continue through the book, you will learn more Swift while you learn
iOS development.

Swift maintains the expressiveness of Objective-C while introducing a syntax that is safer,
succinct, and readable. It emphasizes type safety and adds advanced features such as
optionals, generics, and sophisticated structures and enumerations. Most importantly,
Swift allows the use of these new features while relying on the same tested, elegant iOS
frameworks that developers have built upon for years.

Types in Swift
Swift types can be arranged into three basic groups: structures, classes, and enumerations.
All three can have:
• properties – values associated with a type
• initializers – code that initializes an instance of a type
• instance methods – functions specific to a type that can be called on an instance of
that type
• class or static methods – functions specific to a type that can be called on the type
itself

14
c

Built-in Data Types

The following types of basic data types are most frequently when declaring variables −
• Int or UInt − This is used for whole numbers. More specifically, you can use Int32,
Int64 to define 32 or 64-bit signed integer, whereas UInt32 or UInt64 to define 32
or 64-bit unsigned integer variables. For example, 42 and -23.
• Float − This is used to represent a 32-bit floating-point number and numbers with
smaller decimal points. For example, 3.14159, 0.1, and -273.158.
• Double − This is used to represent a 64-bit floating-point number and used when
floating-point values must be very large. For example, 3.14159, 0.1, and -273.158.
• Bool − This represents a Boolean value which is either true or false.
• String − This is an ordered collection of characters. For example, "Hello, World!"
• Character − This is a single-character string literal. For example, "C"
• Optional − This represents a variable that can hold either a value or no value.
• Tuples − This is used to group multiple values in single Compound Value.

Variables
You must declare them using var keyword as follows –
var variableName = <initial value>

You can provide a type annotation when you declare a variable, to be clear about the kind
of values the variable can store. Here is the syntax –
var variableName:<data type> = <optional initial value>

var varA = 42
print(varA)

var varB:Float

varB = 3.14159
print(varB)

When we run the above program using playground, we get the following result −
42
3.1415901184082

Optionals
Swift also introduces Optionals type, which handles the absence of a value. Optionals say
either "there is a value, and it equals x" or "there isn't a value at all".

15
Here’s an optional Integer declaration –
var perhapsInt: Int?

Here’s an optional String declaration –

var perhapsStr: String?

The above declaration is equivalent to explicitly initializing it to nil which means no value –
var perhapsStr: String? = nil

Let's take the following example to understand how optionals work-

var myString:String? = nil

if myString != nil {
print(myString)
} else {
print("myString has nil value")
}

When we run the above program using playground, we get the following result –
myString has nil value

Constants
Constants refer to fixed values that a program may not alter during its execution. Constants
can be of any of the basic data types like an integer constant, a floating constant, a
character constant, or a string literal. There are enumeration constants as well.
Constants are treated just like regular variables except the fact that their values cannot be
modified after their definition.

Before you use constants, you must declare them using let keyword as follows –
let constantName = <initial value>

Following is a simple example to show how to declare a constant-

let constA = 42
print(constA)

When we run the above program using playground, we get the following result –
42

Operators
An operator is a symbol that tells the compiler to perform specific mathematical or logical
manipulations. Swift is rich in built-in operators and provides the following types of
operators −
• Arithmetic Operators
• Comparison Operators
• Logical Operators
• Bitwise Operators
• Assignment Operators
• Range Operators

16
• Misc Operators

Arithmetic Operators
The following table shows all the arithmetic operators supported by Swift language.
Assume variable A holds 10 and variable B holds 20, then −

Operator Description Example

+ Adds two operands A + B will give 30
− Subtracts second operand from the first A − B will give -10
* Multiplies both operands A * B will give 200
/ Divides numerator by denominator B / A will give 2
% Modulus Operator and remainder of after an B % A will give 0
integer/float division

Comparison Operators
The following table shows all the relational operators supported by Swift language. Assume
variable A holds 10 and variable B holds 20, then –

Operator Description Example

== Checks if the values of two operands are equal or not; (A == B) is not true.
if yes, then the condition becomes true.
!= Checks if the values of two operands are equal or not; (A != B) is true.
if values are not equal, then the condition becomes
true.
> Checks if the value of left operand is greater than the (A > B) is not true.
value of right operand; if yes, then the condition
becomes true.
< Checks if the value of left operand is less than the value (A < B) is true.
of right operand; if yes, then the condition becomes
true.
>= Checks if the value of left operand is greater than or (A >= B) is not true.
equal to the value of right operand; if yes, then the
condition becomes true.
<= Checks if the value of left operand is less than or equal (A <= B) is true.
to the value of right operand; if yes, then the condition
becomes true.

Logical Operators
The following table shows all the logical operators supported by Swift language. Assume
variable A holds 1 and variable B holds 0, then –

Operator Description Example

&& Called Logical AND operator. If both the operands are non- (A && B) is false.
zero, then the condition becomes true.
|| Called Logical OR Operator. If any of the two operands is (A || B) is true.
non-zero, then the condition becomes true.

17
! Called Logical NOT Operator. Use to reverses the logical !(A && B) is true.
state of its operand. If a condition is true, then the Logical
NOT operator will make it false.

Bitwise Operators
Bitwise operators work on bits and perform bit by bit operation. The truth tables for &, |,
and ^ are as follows −
p q p&q p|q p^q
0 0 0 0 0
0 1 0 1 1
1 1 1 1 0
1 0 0 1 1

Assume A = 60; and B = 13;

In binary format, they will be as follows:

A = 0011 1100

B = 0000 1101

-----------------

A & B = 0000 1100

A|B = 0011 1101

A^B = 0011 0001

~A = 1100 0011

Bitwise operators supported by Swift language are listed in the following table. Assume
variable A holds 60 and variable B holds 13, then 7−

Operator Description Example

& Binary AND Operator copies a bit to the result, if it (A & B) will give 12,
exists in both operands. which is 0000 1100
| Binary OR Operator copies a bit, if it exists in either (A | B) will give 61, which
operand. is 0011 1101
^ Binary XOR Operator copies the bit, if it is set in one (A ^ B) will give 49,
operand but not both. which is 0011 0001
~ Binary Ones Complement Operator is unary and has (~A ) will give -61, which
the effect of 'flipping' bits. is 1100 0011 in 2's
complement form.
<< Binary Left Shift Operator. The left operands value is (A << 2 will give 240,
moved left by the number of bits specified by the right which is 1111 0000
operand.

18
>> Binary Right Shift Operator. The left operands value is A >> 2 will give 15, which
moved right by the number of bits specified by the is 0000 1111
right operand.

Assignment Operators
Swift supports the following assignment operators –

Operator Description Example

= Simple assignment operator, Assigns values from C = A + B will assign value
right side operands to left side operand of A + B into C
+= Add AND assignment operator, It adds right operand C += A is equivalent to C =
to the left operand and assigns the result to left C+A
operand
-= Subtract AND assignment operator, It subtracts right C -= A is equivalent to C =
operand from the left operand and assigns the result C-A
to left operand
*= Multiply AND assignment operator, It multiplies right C *= A is equivalent to C =
operand with the left operand and assigns the result C*A
to left operand
/= Divide AND assignment operator, It divides left C /= A is equivalent to C =
operand with the right operand and assigns the result C/A
to left operand
%= Modulus AND assignment operator, It takes modulus C %= A is equivalent to C
using two operands and assigns the result to left =C%A
operand
<<= Left shift AND assignment operator C <<= 2 is same as C = C
<< 2
>>= Right shift AND assignment operator C >>= 2 is same as C = C
>> 2
&= Bitwise AND assignment operator C &= 2 is same as C = C &
2
^= bitwise exclusive OR and assignment operator C ^= 2 is same as C = C ^ 2
|= bitwise inclusive OR and assignment operator C |= 2 is same as C = C | 2

Range Operators
Swift includes two range operators, which are shortcuts for expressing a range of values.
The following table explains these two operators.

Operator Description Example

Closed Range (a...b) defines a range that runs from a to b, and 1...5 gives 1, 2, 3, 4 and 5
includes the values a and b.
Half-Open (a..< b) defines a range that runs from a to b, but 1..< 5 gives 1, 2, 3, and 4
Range does not include b.
One- sided a… , defines a range that runs from a to end of 1… gives 1 , 2,3… end of
Range elements elements
…a , defines a range starting from start to a

19
…2 gives beginning… to
1,2

Misc Operators
Swift supports a few other important operators including range and ? : which are explained
in the following table.

Operator Description Example

Unary Minus The sign of a numeric value can be toggled -3 or -4
using a prefixed -
Unary Plus Returns the value it operates on, without any +6 gives 6
change.
Ternary Condition ? X : Y If Condition is true ? Then
Conditional value X : Otherwise value
Y

Decision Making
Swift provides the following types of decision making statements.

S.N. Statement Description Example

1 if statement An if statement consists var varA:Int = 10;
of a Boolean expression
followed by one or more /* Check the boolean
statements. condition using if
statement */
if varA < 20 {
/* If condition is
true then print the
following */
print("varA is less
than 20");
}

print("Value of
variable varA is
\(varA)");

Output:
varA is less than 20
Value of variable varA
is 10

2 if...else statement An if statement can be var varA:Int = 100;

followed by an
optional else statement, /* Check the boolean
which executes when condition using if
the Boolean expression statement */
if varA < 20 {
is false.

20
/* If condition is
true then print the
following */
print("varA is less
than 20");

} else {
/* If condition is
false then print the
following */
print("varA is not
less than 20");
}

print("Value of
variable varA is
\(varA)");

Output:
varA is not less than
20
Value of variable varA
is 100

3 if...elseif...else An if statement can be var varA:Int = 100;

Statement followed by an optional
else if...else statement, /* Check the boolean
which is very useful to condition using if
test various conditions statement */
if varA == 20 {
using single if...else if /* If condition is
statement. true then print the
following */
print("varA is equal
to than 20");

} else if varA == 50 {
/* If condition is
true then print the
following */
print("varA is equal
to than 50");

} else {
/* If condition is
false then print the
following */
print("None of the
values is matching");
}

21
print("Value of
variable varA is
\(varA)");

Output:
None of the values is
matching
Value of variable varA
is 100

4 Nested if statement You can use one if or var varA:Int = 100;

else if statement inside var varB:Int = 200;
another if or else if
statement(s). /* Check the boolean
condition using if
statement */
if varA == 100 {
/* If condition is
true then print the
following */
print("First
condition is
satisfied");

if varB == 200 {
/* If condition
is true then print the
following */
print("Second
condition is also
satisfied");
}
}

print("Value of
variable varA is
\(varA)");
print("Value of
variable varB is
\(varB)");

Output:
First condition is
satisfied
Second condition is
also satisfied
Value of variable varA
is 100
Value of variable varB
is 200

22
5 switch statement A switch statement var index = 10
allows a variable to be switch index {
tested for equality case 100 :
against a list of values. print( "Value of
index is 100")
case 10,15 :
print( "Value of
index is either 10 or
15")
case 5 :
print( "Value of
index is 5")
default :
print( "default
case")
}

Output:
Value of index is
either 10 or 15

Loops
Swift programming language provides the following kinds of loop to handle looping
requirements.

S.N. Statement Description Example

1 for-in This loop performs a set var someInts:[Int] =
of statements for each [10, 20, 30]
item in a range,
sequence, collection, or for index in someInts {
progression. print( "Value of
index is \(index)")
}

Output:
Value of index is 10
Value of index is 20
Value of index is 30

2 while loop Repeats a statement or var index = 10

group of statements
while a given condition while index < 15 {
is true. It tests the print( "Value of
condition before index is \(index)")
index = index + 1
executing the loop body. }

Output:
Value of index is 10
Value of index is 11

23
Value of index is 12
Value of index is 13
Value of index is 14

3 repeat...while loop Like a while statement, var index = 10

except that it tests the repeat {
condition at the end of print( "Value of
the loop body. index is \(index)")
index = index + 1
}
while index < 15

Output:
Value of index is 10
Value of index is 11
Value of index is 12
Value of index is 13
Value of index is 14

Arrays
You can create an empty array of a certain type using the following initializer syntax –
var someArray = [SomeType]()

You can use the following statement to create an empty array of Int type having 3 elements
and the initial value as zero –
var someInts = [Int](count: 3, repeatedValue: 0)

Following is one more example to create an array of three elements and assign three values
to that array –
var someInts:[Int] = [10, 20, 30]

You can retrieve a value from an array by using subscript syntax, passing the index of the
value you want to retrieve within square brackets immediately after the name of the array
as follows –
var someVar = someArray[index]

The following example shows how to create, initialize, and access arrays –
var someInts = [Int](count: 3, repeatedValue: 10)

var someVar = someInts[0]

print( "Value of first element is \(someVar)" )
print( "Value of second element is \(someInts[1])" )
print( "Value of third element is \(someInts[2])" )

Output:
Value of first element is 10
Value of second element is 10
Value of third element is 10

24
Strings
You can create a String either by using a string literal or creating an instance of a String
class as follows –
// String creation using String literal
var stringA = "Hello, Swift!"
print( stringA )

// String creation using String instance

var stringB = String("Hello, Swift!")
print( stringB )

Empty String
You can create an empty String either by using an empty string literal or creating an
instance of String class as shown below. You can also check whether a string is empty or
not using the Boolean property isEmpty.

// Empty string creation using String literal

var stringA = ""

if stringA.isEmpty {
print( "stringA is empty" )
} else {
print( "stringA is not empty" )
}

// Empty string creation using String instance

let stringB = String()

if stringB.isEmpty {
print( "stringB is empty" )
} else {
print( "stringB is not empty" )
}

Output:
stringA is empty
stringB is empty

String Concatenation
You can use the + operator to concatenate two strings or a string and a character, or two
characters. Here is a simple example –
let constA = "Hello,"
let constB = "World!"

var stringA = constA + constB

print( stringA )

Output:
Hello,World!

25
String Length
Swift strings do not have a length property, but you can use the global count() function to
count the number of characters in a string. Here is a simple example –

var varA = "Hello, Swift 4!"

print( "\(varA), length is \((varA.count))" )

Output:
Hello, Swift 4!, length is 15

String Comparison
You can use the == operator to compare two strings variables or constants. Here is a simple
example –
var varA = "Hello, Swift!"
var varB = "Hello, World!"

if varA == varB {
print( "\(varA) and \(varB) are equal" )
} else {
print( "\(varA) and \(varB) are not equal" )
}

Output:
Hello, Swift! and Hello, World! are not equal

Function
A function's arguments must always be provided in the same order as the function's
parameter list and the return values are followed by →.

func funcname(Parameters) -> returntype {

Statement1
Statement2
---
Statement N
return parameters
}

Take a look at the following code. The student’s name is declared as string datatype
declared inside the function 'student' and when the function is called, it will return
student’s name.

func student(name: String) -> String {

return name
}
print(student(name: "First Program"))
print(student(name: "About Functions"))

26
When we run the above program using playground, we get the following result –
First Program
About Functions

Functions with Parameters

A function is accessed by passing its parameter values to the body of the function. We can
pass single to multiple parameter values as tuples inside the function.

func mult(no1: Int, no2: Int) -> Int {

return no1*no2
}

print(mult(no1: 2, no2: 20))

print(mult(no1: 3, no2: 15))
print(mult(no1: 4, no2: 30))

When we run above program using playground, we get the following result –
40
45
120

Functions without Parameters

Following is an example having a function without a parameter –

func votersname() -> String {

return "Alice"
}
print(votersname())

When we run the above program using playground, we get the following result −
Alice

Views and the View Hierarchy

A view hierarchy defines the relationships of views in a window to each other. You can
think of a view hierarchy as an inverted tree structure with the window being the top node
of the tree. Under it come views structurally specified by parent-child relationships. From
a visual perspective, the essential fact of a view hierarchy is enclosure: one view contains
one or more other views, and the window contains them all.

The view hierarchy is a major part of the responder chain, and it is something that the
application frameworks use to determine the layering order of views when they render the
content of a window in a drawing pass. The view hierarchy is also the governing concept
behind view composition: You construct compound views by adding sub views to a super
view. Finally, the view hierarchy is a critical factor in the multiple coordinate systems found
in a window.

27
Figure 8-20. View Hierarchy in iOS

A view is related to other views through two properties, and these relationships determine
the form of the hierarchy:
• super view — The view above a given view in the hierarchy; this is the view that
encloses it. All views except the topmost view must have a super view.
• sub views — The views below a given view in the hierarchy; these are the views
that it encloses. A view may have any number of sub views, or it may have none.

28
Figure 8-21. Example of View Hierarchy in iOS

Storyboard and View Controllers

Storyboards are an exciting feature first introduced in iOS 5, which save time building user
interfaces for your apps. Storyboards allow you to prototype and design multiple view
controller views within one file, and also let you create transitions between view
controllers.

Figure 8-22. Example of Storyboard with multiple view controllers

29
To demonstrate storyboard now I am going to create a storyboard containing a Tab and
multiple view controllers linking with the Tab.
So, let’s begin by creating a project with following information:
§ Product Name: MyExample.
§ Organization Name: Fill this in however you like.
§ Organization Identifier: The identifier you use for your apps.
§ Language: Swift.
§ User Interface: Storyboard.
§ Make sure you’ve unchecked the Use Core Data, Include Unit Tests and UI
Tests options.

Open Main.storyboard in the Project navigator to view it in the Interface Builder editor:

Figure 8-23. First look of Main. Storyboard

Here, you see a single view controller containing an empty view. The arrow pointing to the
view controller from the left indicates it’s the initial view controller for this
storyboard. Xcode enables Auto Layout and Size Classes by default for storyboards. They
allow you to make flexible user interfaces that can resize easily, which is useful for
supporting various sizes of iPhones and iPads.

Adding Tab to Storyboard

Drag a tab bar controller from the Object Library into the canvas. You can filter the list by
typing part of the name of the item you’re looking for.
Tab bar controller comes pre-configured with two additional view controllers, one for each
tab. It’s a so-called container view controller because it contains one or more other view
controllers. Other common containers are the Navigation controller and the Split View
controller.

30
Figure 8-24. Adding Tab Controller to Main. Storyboard

The arrows between the tab bar controller and the view controllers it contains represent
the container relationship. The icon shown below, in the middle of the arrow body,
signifies that they have an embed relationship.

Figure 8-25. Showing Relationship

31
Build and run and you’ll see something like this in the console:

MyExample[9912:704408] [WindowScene] Failed to instantiate the default

view controller for UIMainStoryboardFile 'Main' – perhaps the
designated entry point is not set?

This error simply indicates that the app didn’t find the initial view controller to show.

To fix this error, Open Main.storyboard and select the Tab Bar Controller Scene. On the
right, select the Attribute inspector.

You’ll find a checkbox named Is Initial View Controller.

Checking this box will identify the selected view controller as the initial entry point for the
storyboard you’re on. Also, an arrow will appear on the left of the view controller.

Now, build and run and you’ll see an empty view controller with a tab bar that has two
items at the bottom.

32
Figure 8-26. Output demonstrating Tab View Controller

Working with widgets and its attributes

S.N. UI Controls Description

1 iOS UI Buttons In iOS button object is a view that perform some custom
actions based on user interactions.
When we click or tap a button in iOS it will perform
actions which are attached to it and we can easily change
the appearance of iOS buttons by adding title or image
icons based on our requirements.

2 iOS UI Labels Label in iOS is a basic UI control which is used to display

plain static text or styled text. The content in iOS label
control is a read only text we cannot able change or edit
the text but we can copy the content of label.

33
We can apply custom styles to the content in iOS label
control like changing the font style, font size, adding
background colors, etc. based on our requirements.
3 iOS UI Text Fields In iOS Text fields are used to allow users to enter single
line of text as an input to an app. The text fields
automatically bring up a keyboard to enter a text
whenever the user touch or taped it and these text fields
are helpful to gather small amounts of text from the user
like name, email, etc. By using text fields, we can perform
some actions like search operation, based on that text.
We can use Text Fields in our iOS application by
adding UITextField class reference in our applications.

4 iOS UI Image View In iOS, image view is used to show the images in iOS
application and it will resize the images automatically to
make fit with the current size of view.
By using iOS image view, we can show single image or
animated sequence of images with transparent or opaque
background based on our requirement.

5 iOS Progress Bar In iOS progress indicators or progress bars are used to
(Progress View) show the progress of task in application instead of making
people staring at a static screen while performing lengthy
data operations.
By using iOS progress indicators or bars we can make the
people to understand that how long the process will take
to finish the task like as shown below:

We can use progress view indicators in our iOS

application by adding UIProgressView class reference in
our applications.

6 iOS UI DatePicker In iOS datepicker is a control which is used to select a

required date, time, or both and It also provides an
interface for a countdown timer. Datepicker is having
different modes by using those modes we can specify
date and time display formats based on our requirements
like only date or time or date and time or countdown
timer.
7 iOS UI Switches In iOS switches are used to let user know the status of
option either on or off / active or inactive. Generally, we
use switches to toggle an option between on and off.

34
By using iOS switches we can implement features like
allowing users to turn the settings on or off based on
their requirements.
The visual representation of iOS switches with on and off
options will be like as shown below:

We can use Switches in our iOS application by

adding UISwitch class reference in our applications.

8 iOS UI Sliders In iOS slider is a horizontal bar with thumb control, by

using this we can slide between minimum and maximum
value. Generally, we use sliders to increase or decrease
value like adjust screen brightness level or change the
volume of speaker like as shown below:

We can use Sliders in our iOS applications by

adding UISlider class reference.

9 iOS UI Segmented In iOS segmented control is a horizontal control which

Control made with a multiple segments and each segment will act
as separate view. Our iOS segmented control will be like
as shown below:

We can use SegmentedControl in our iOS applications

by adding UISegmentedControl class reference.

10 IOS UI WebView In iOS webview control is used to embed websites within

application or show rich HTML web content inside of app
and the iOS webview control will act as a HTML iframe to
show the website content within an app.
We can use Web View in our iOS applications by
adding UIWebView class reference.

11 iOS UI Scroll View In iOS, scroll view is used to show the content which is
larger than the scroll view boundaries like viewing larger
content in documents, showing multiple images in app. In
our iOS application whenever we see the scroll view it is
indication that there is extra content other than visible
area.
We can use Scroll View in our iOS applications by
adding UIScrollView class reference.

35
Creating a Simple iOS Application
Here we going to create a simple application to show the addition of two numbers. Our
application contains two Text Fields for inputting two numbers and a Button to trigger click
event. Also I will create a Label for displaying the result.

After designing UI our application looks something like this:

Figure 8-27. UI for adding two numbers

Source code for adding two numbers is shown below:

import UIKit
class ViewController: UIViewController {

@IBOutlet weak var txtFirst: UITextField!

@IBOutlet weak var txtSecond: UITextField!
@IBOutlet weak var lblRes: UILabel!
@IBOutlet weak var btnClick: UIButton!

@IBAction func btnClick(sender: AnyObject) {

let first= Double(txtFirst.text!)
let second= Double(txtSecond.text!)
let res=Double(first! + second!)
lblRes.text="Sum is \(res)"
}

override func viewDidLoad() {

super.viewDidLoad()
// Do any additional setup after loading the view, typically
from a nib.
}

override func didReceiveMemoryWarning() {

super.didReceiveMemoryWarning()
// Dispose of any resources that can be recreated.
}

36
}

After running our application following output will be produced:

Figure 8-28. Output demonstrating addition of two numbers

Exercise

1. What do you mean by iOS programming? Explain.

2. Explain iOS platform in detail.
3. Explain the procedure for developing hello world application in iOS.
4. What do you mean by connections? How can you connect UI controls to application
code? Explain with example.
5. What do you mean by swift language? Explain process of declaring and using
variables in swift language.
6. Explain different types of operators used in swift language.
7. Explain branching and looping statements used in swift language in detail.
8. How can you create array and use array in swift language? Explain.
9. Explain view hierarchy in iOS programming in detail.
10. What do you mean by storyboard and view controllers? Explain with example.
11. What are different types of UI controls used in iOS programming? Explain in detail.
12. Develop an iOS application to calculate simple interest.
13. Develop an iOS application to calculate area and perimeter of rectangle.

37
Model Question – Set 1

Mobile Programming
BCA Sixth Semester

Objective Type Questions (Attempt all the Questions): [10x1=10]

1. What is ADB in android?
A. Image tool B. Development tool
C. Android Debug Bridge D. None of the above.
Answer: C

2. Which company developed android?

A. Apple B. Google
C. Android Inc. D. Nokia
Answer: C

3. Which one is NOT related to fragment class?

A. DialogFragment B. ListFragment
C. PreferenceFragment D. CursorFragment
Answer: D

4. A ___________ makes a specific set of the application data available to other

applications
A. Content provider B. Broadcast receivers
C. Intent D. None of these
Answer: A

5. Which among these are NOT a part of Android’s native libraries?

A. Webkit B. Dalvik
C. OpenGL D. SQLite
Answer: B

6. During an Activity life-cycle, what is the first callback method invoked by the
system?
A. onStop() B. onStart()
C. onCreate() D. onRestore()
Answer: C

7. What Activity method you use to retrieve a reference to an Android view by using
the id attribute of a resource XML?
A. findViewByReference(int id); B. findViewById(int id)
C. retrieveResourceById(int id) D. findViewById(String id)
Answer: B
8. What does the src folder contain?
A. Image and icon files B. XML resource files
C. The application manifest file D. Java source code files
Answer: D

9. IOS Stands for?

A. Internetwork Operating System B. IPhone Operating System
C. Internet Operating System D. None of Them
Answer: B

10. The IDE used in Swift is

A. Swiftc B. Gas
C. Xcode D. Ld
Answer: C

Short Questions (Attempt any SIX Questions): [6x5=30]

11. What do you mean by mobile programming? Explain life cycle of mobile application
development.
12. What do you mean by view hierarchy? Explain view hierarchy of android with the
help of suitable example.
13. Define widget. Explain any five widgets used in android application with their
attributes.
14. What do you mean by android activity? Explain android activity life cycle.
15. Differentiate activity and fragment with example.
16. Why RecyclerView is recommended over ListView? Explain with example.
17. Develop an iOS application to calculate simple interest.

Long Questions (Attempt any TWO Questions): [6x5=30]

18. Develop a simple calculator android application with two input fields for inputting
numbers and four Buttons for performing addition, subtraction, multiplication and
division. Display the result in a TextView.
19. Develop an android application to demonstrate basic crud operation using SQLite.
20. Develop an android application that demonstrates retrieval of contents from
remote server.
Model Question – Set 2

Mobile Programming
BCA Sixth Semester

Objective Type Questions (Attempt all the Questions): [10x1=10]

1. Android releases since 1.5 have been given nicknames derived from how?
A. Adjective and strange animal B. Food
C. Planets D. American States
Answer: B

2. Which one is not a nickname of a version of Andriod?

A. Cupcake B. Gingerbread
C. Honeycomb D. Muffin
Answer: D

3. What is the name of the program that converts Java byte code into Dalvik byte
code?
A. Android Interpretive Compiler (AIC) B. Dalvik Converter
C. Dex compiler D. Mobile Interpretive Compiler (MIC)
Answer: C

4. Difference between android api and google api?

A. The Google API includes Google Maps and other Google-specific libraries. The
Android one only includes core Android libraries
B. The google API one only includes core android libraries. The Android includes
Google Maps and other Google-specific libraries
C. None of the above
D. All of the above
Answer: A

5. When developing for the Android OS, Java bytecode is compiled into what?
A. Java source code B. Dalvik application code
C. Dalvik byte code D. C source code
Answer: C

6. An activity can be thought of as corresponding to what?

A. A Java project B. A Java class
C. A method call D. An object field
Answer: A

7. Where layouts are placed in android?

A. src folder B. manifest file
C. layout folder D. drawable folder
Answer: C
8. Which one is not a dialog box supported in android?
A. Alert Dialog B. List Dialog
C. Progress Dialog D. Date Picker Dialog
Answer: B

9. In swift, to create mutable object, _____ is used.

A. let B. var
C. Both A&B D. None
Answer: B

10. Which of the following is incorrect data type in Swift?

A. UInt B. Double
C. Char D. Optional
Answer: C

Short Questions (Attempt any SIX Questions): [6x5=30]

11. Explain different brands, models and platforms of mobile devices.
12. List and explain different versions of android in detail.
13. Differentiate LinearLayout and RelativeLayout with example.
14. How can you pass data between multiple activities using intent? Explain.
15. Develop an android application to calculate simple interest in a dialog.
16. What do you mean by RecyclerView? Explain its features.
17. Develop an iOS application to calculate area and perimeter of rectangle.

Long Questions (Attempt any TWO Questions): [6x5=30]

18. Develop an android application that demonstrates sending of contents to remote
server.
19. Develop a phone directory application using SQLite.
20. Develop an image gallery using GridView. Your gallery should display at least 5
drawable images. If any of the image is clicked it should be displayed in another
activity in large size.
Model Question – Set 3

Mobile Programming
BCA Sixth Semester

Objective Type Questions (Attempt all the Questions): [10x1=10]

1. Which is not the layout in android?
A. Frame Layout B. Linear Layout
C. Relative Layout D. Fragment Layout
Answer: D

2. You can shut down an activity by calling its _______ method.

A. onDestory() B. finishActivity()
C. finish() D. none of the above
Answer: C

3. Which are the screen sizes in Android?

A. small B. normal
C. large D. all of the above
Answer: D

4. Which one is not the Direct subclasses of Activity?

A. ListActivity B. ActivityGroup
C. FragmentActivity D. BaseActivity
Answer: D

5. Which one is NOT related to fragment class?

A. DialogFragment B. CursorFragment
C. PreferenceFragment D. ListFragment
Answer: B

6. The XML file that contains all the text that your application uses.
A. stack.xml B. text.xml
C. strings.xml D. string.java
Answer: C

7. How is a simulator different from an emulator?

A. Emulators are only used to play old SNES games, simulators are used for software
development
B. The emulator is shipped with the Android SDK and third party simulators are not
C. The emulator can virtualize sensors and other hardware features, while the
simulator cannot
D. The emulator imitates the machine executing the binary code, rather than
simulating the behaviour of the code at a higher level
Answer: D
8. When the activity is not in focus, but still visible on the screen it is in?
A. running state B. stopped state
C. paused state D. destroyed state
Answer: C

9. What does the .apk extension stand for?

A. Application Package B. Application Program Kit
C. Android Proprietary Kit D. Android Package
Answer: A

10. Which of the following declares a mutable array in Swift?

A. Let X =[Int]() B. Var X=[Int]
C. Var X=[Int]() D. Let X=[Int]
Answer: C

Short Questions (Attempt any SIX Questions): [6x5=30]

11. Explain about manifest file. How can we add activity in manifest? Explain with
example.
12. What do you mean by iOS programming? Explain iOS platform in detail.
13. What do you mean by menu? Explain its types.
14. What do you mean by UI flexibility? Why UI needs to be flexible? Explain how
fragments help to make UI flexible.
15. Explain the process of creating Database and Tables using SQLite in android.
16. What do you mean by fragment? Explain lifecycle of fragment in detail.
17. Explain the procedure for publishing signed APK in play store.

Long Questions (Attempt any TWO Questions): [6x5=30]

18. Develop an android application to input your name, address, gender and other
personal information. Pass and display this information in another activity.
19. Develop an android application to calculate simple interest using fragment.
20. Explain the procedure for generating API key for displaying google map in your
application. Also develop android application that uses this API key to display
google map.
Projects

Sample Project -1 Income/Expenses Tracker

Project Title – Income/Expenses Tracker

Project Features-
• Tracks daily income and expenses.
• Displays available balance by calculating income and expenses.
• Also generates date wise income/expenses report.
• Doesn’t store data in remote server, but store data locally using SQLite.
Project Prototype-
Project Files-

Dashboard

activity_main.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

</LinearLayout>
</LinearLayout>

</LinearLayout>

</LinearLayout>
</LinearLayout>

</RelativeLayout>
MainActivity.java

public class MainActivity extends AppCompatActivity {

TextView txtIncome,txtExpenses,txtBalance,txtDetails;
Button btnEntry,btnReport;
MyDatabase myDatabase;
Cursor cursor;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.activity_main);

txtIncome=findViewById(R.id.txtIncome);
txtExpenses=findViewById(R.id.txtExpenses);
txtBalance=findViewById(R.id.txtBalance);
txtDetails=findViewById(R.id.txtDetails);
btnEntry=findViewById(R.id.btnEntry);
btnReport=findViewById(R.id.btnReport);
myDatabase=new MyDatabase(this);

btnEntry.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(MainActivity.this,
DataEntry.class);
startActivity(intent);
}
});

txtDetails.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(MainActivity.this,
TodayDetails.class);
startActivity(intent);
}
});

btnReport.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(MainActivity.this,
DateWiseReport.class);
startActivity(intent);
}
});

@Override
protected void onResume(){
super.onResume();
//displaying data of current date
loadData();
}

public void loadData(){

cursor=myDatabase.selectData(getCurrentDate());
int income=0,expenses=0,balance=0;
while (cursor.moveToNext()){
income+=cursor.getInt(2);
expenses+=cursor.getInt(3);
}
balance=income-expenses;
txtIncome.setText(income+"");
txtExpenses.setText(expenses+"");
txtBalance.setText(balance+"");
}

public static String getCurrentDate(){

//current date
SimpleDateFormat formatter = new SimpleDateFormat("yyyy-MM-dd");
Date date = new Date();
String dat=formatter.format(date);
return dat;
}
}

Data Entry

data_entry.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>
DataEntry.java

public class DataEntry extends AppCompatActivity {

EditText edtDate,edtAmount;
Spinner spTitle;
Button btnSubmit;
MyDatabase myDatabase;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.data_entry);

edtDate=findViewById(R.id.edtDate);
edtAmount=findViewById(R.id.edtAmount);
spTitle=findViewById(R.id.spTitle);
btnSubmit=findViewById(R.id.btnSubmit);
myDatabase=new MyDatabase(this);
edtDate.setText(MainActivity.getCurrentDate());

btnSubmit.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
//getting data
String date=edtDate.getText().toString();
String title=spTitle.getSelectedItem().toString();
String amount=edtAmount.getText().toString();
//validating data
if(date.equals("")){
Toast.makeText(DataEntry.this,"Please Enter Date !",
Toast.LENGTH_LONG).show();
} else if(amount.equals("")) {
Toast.makeText(DataEntry.this, "Please Enter Amount
!",Toast.LENGTH_LONG).show();
} else if(title.equals("Select Title")){
Toast.makeText(DataEntry.this,"Please Select Title
!",Toast.LENGTH_LONG).show();
}else{
//checking income or expenses
if(title.equals("Income"))
myDatabase.insertData(date,amount,"0");
else
myDatabase.insertData(date,"0",amount);

Toast.makeText(DataEntry.this,"Data Inserted
Successfully !",Toast.LENGTH_LONG).show();
edtAmount.setText("");
spTitle.setSelection(0);
}

}
});
}
}
Database

MyDatabase.java

public class MyDatabase extends SQLiteOpenHelper{

// Database Version
private static final int DATABASE_VERSION = 1;
// Database Name
private static final String DATABASE_NAME = "mydatabase";

public MyDatabase(Context context) {

super(context, DATABASE_NAME, null, DATABASE_VERSION);
}

// Creating Tables
@Override
public void onCreate(SQLiteDatabase db) {
// create notes table
String createQuery="CREATE TABLE mytable(id INTEGER PRIMARY KEY
AUTOINCREMENT,date TEXT,income TEXT,expenses TEXT)";
db.execSQL(createQuery);
}

//code to insert data

public void insertData(String date,String income, String expenses){
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues=new ContentValues();
contentValues.put("date",date);
contentValues.put("income",income);
contentValues.put("expenses",expenses);
//inserting row
db.insert("mytable",null,contentValues);
db.close();
}

//code to select data

public Cursor selectData(String date){
SQLiteDatabase db=this.getReadableDatabase();
String query="SELECT * FROM mytable WHERE date=?";
Cursor cursor=db.rawQuery(query,new String[]{date});
return cursor;
}

public Cursor selectData(String date1, String date2){

SQLiteDatabase db=this.getReadableDatabase();
String query="SELECT * FROM mytable WHERE date BETWEEN ? AND ?";
Cursor cursor=db.rawQuery(query,new String[]{date1,date2});
return cursor;
}
//code to update data
public void updateData(String id,String date, String income, String
expenses){
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues=new ContentValues();
contentValues.put("date",date);
contentValues.put("income",income);
contentValues.put("expenses",expenses);
//updating row
db.update("mytable",contentValues,"id=?",new String[]{id});
db.close();
}

//code to delete data

public void deleteData(String id) {
SQLiteDatabase db = this.getWritableDatabase();
//deleting row
db.delete("mytable","id=?",new String[]{id});
}
}

Displaying Today’s Details

today_details.xml

<?xml version="1.0" encoding="utf-8"?>

<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerview"
android:scrollbars="vertical"
android:layout_width="match_parent"
android:layout_height="match_parent"/>

</RelativeLayout>

list_items.xml

<?xml version="1.0" encoding="utf-8"?>

</RelativeLayout>

DataModel.java

public class DataModel {

private int id;
private String date;
private int income;
private int expenses;

public DataModel(int id,String date,int income,int expenses){

this.id=id;
this.date=date;
this.income=income;
this.expenses=expenses;
}

public int getId(){

return id;
}

public String getDate(){

return date;
}

public int getIncome(){

return income;
}

public int getExpenses(){

return expenses;
}

}
RecyclerViewAdapter.java

public class RecyclerViewAdapter extends

RecyclerView.Adapter<RecyclerViewAdapter.ViewHolder> {
Activity context;
ArrayList<DataModel> data;

public RecyclerViewAdapter(Activity context, ArrayList<DataModel>

data){
this.context=context;
this.data=data;
}

@Override
public ViewHolder onCreateViewHolder(ViewGroup parent, int viewType)
{
LayoutInflater layoutInflater = LayoutInflater.from(context);
View listItem= layoutInflater.inflate(R.layout.list_items,
parent, false);
ViewHolder viewHolder = new ViewHolder(listItem);
return viewHolder;
}

@Override
public void onBindViewHolder(ViewHolder holder, int position) {
final DataModel current=data.get(position);
holder.txtDate.setText("Date: "+current.getDate());
if(current.getExpenses()==0){
holder.txtExpenses.setVisibility(View.GONE);
holder.txtIncome.setVisibility(View.VISIBLE);
holder.txtIncome.setText("Income: "+current.getIncome());
}else{
holder.txtExpenses.setVisibility(View.VISIBLE);
holder.txtIncome.setVisibility(View.GONE);
holder.txtExpenses.setText("Expenses: "+
current.getExpenses());
}

holder.relativeLayout.setOnClickListener(new View.
OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(context,ModifyDetails.class);
intent.putExtra("id",current.getId());
intent.putExtra("date",current.getDate());
if(current.getExpenses()==0)
intent.putExtra("amount",current.getIncome());
else
intent.putExtra("amount",current.getExpenses());
context.startActivity(intent);

}
});

@Override
public int getItemCount() {
return data.size();
}

public static class ViewHolder extends RecyclerView.ViewHolder {

TextView txtDate,txtIncome,txtExpenses;
RelativeLayout relativeLayout;
public ViewHolder(View itemView) {
super(itemView);
txtDate = itemView.findViewById(R.id.txtDate);
txtIncome = itemView.findViewById(R.id.txtIncome);
txtExpenses = itemView.findViewById(R.id.txtExpenses);
relativeLayout=itemView.findViewById(R.id.relat);
}
}
}

TodayDetails.java

public class TodayDetails extends AppCompatActivity {

RecyclerView recyclerView;
RecyclerView.Adapter recyclerAdapter;
RecyclerView.LayoutManager layoutManager;
MyDatabase myDatabase;
Cursor cursor;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.today_details);
recyclerView=findViewById(R.id.recyclerview);
myDatabase=new MyDatabase(this);

@Override
protected void onResume(){
super.onResume();
loadData();
}

public void loadData(){

cursor=myDatabase.selectData(MainActivity.getCurrentDate());
ArrayList<DataModel> data=new ArrayList<>();
while (cursor.moveToNext()){
int id=cursor.getInt(0);
String date=cursor.getString(1);
int income=cursor.getInt(2);
int expenses=cursor.getInt(3);
DataModel dataModel=new DataModel(id,date,income,expenses);
data.add(dataModel);
}

layoutManager=new LinearLayoutManager(this);
recyclerAdapter=new RecyclerViewAdapter(this,data);
recyclerView.setLayoutManager(layoutManager);
recyclerView.setAdapter(recyclerAdapter);
}
}
Date wise Report

datewise_report.xml

<?xml version="1.0" encoding="utf-8"?>

<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerview"
android:layout_marginTop="10dp"
android:scrollbars="vertical"
android:layout_below="@+id/btnSubmit"
android:layout_width="match_parent"
android:layout_height="match_parent"/>

</RelativeLayout>

DateWiseReport.java

public class DateWiseReport extends AppCompatActivity {

RecyclerView recyclerView;
RecyclerView.Adapter recyclerAdapter;
RecyclerView.LayoutManager layoutManager;
MyDatabase myDatabase;
Cursor cursor;
EditText edtDate1,edtDate2;
Button btnSubmit;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.datewise_report);
recyclerView=findViewById(R.id.recyclerview);
myDatabase=new MyDatabase(this);
edtDate1=findViewById(R.id.edtDate1);
edtDate2=findViewById(R.id.edtDate2);
btnSubmit=findViewById(R.id.btnSubmit);

btnSubmit.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
loadData();
}
});

public void loadData(){

String date1=edtDate1.getText().toString();
String date2=edtDate2.getText().toString();
if(date1.equals("")||date2.equals("")){
Toast.makeText(DateWiseReport.this,"Please Enter Date !",
Toast.LENGTH_LONG).show();
}else{
cursor=myDatabase.selectData(date1,date2);
ArrayList<DataModel> data=new ArrayList<>();
while (cursor.moveToNext()){
int id=cursor.getInt(0);
String date=cursor.getString(1);
int income=cursor.getInt(2);
int expenses=cursor.getInt(3);
DataModel dataModel=new DataModel(id,date,income,
expenses);
data.add(dataModel);
}
layoutManager=new LinearLayoutManager(this);
recyclerAdapter=new RecyclerViewAdapter(this,data);
recyclerView.setLayoutManager(layoutManager);
recyclerView.setAdapter(recyclerAdapter);
}
}
}
Modifying Data

modify_details.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

ModifyDetails.java

public class ModifyDetails extends AppCompatActivity {

EditText edtDate,edtAmount;
Spinner spTitle;
Button btnUpdate,btnDelete;
MyDatabase myDatabase;
int id=0,amount=0;
String date="";
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.modify_details);

edtDate=findViewById(R.id.edtDate);
edtAmount=findViewById(R.id.edtAmount);
spTitle=findViewById(R.id.spTitle);
btnUpdate=findViewById(R.id.btnUpdate);
btnDelete=findViewById(R.id.btnDelete);
myDatabase=new MyDatabase(this);

Intent intent=getIntent();
id=intent.getIntExtra("id",0);
date=intent.getStringExtra("date");
amount=intent.getIntExtra("amount",0);

edtDate.setText(date);
edtAmount.setText(amount+"");

btnDelete.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
myDatabase.deleteData(String.valueOf(id));
Toast.makeText(ModifyDetails.this,"Data Deleted
Successfully !",Toast.LENGTH_LONG).show();
finish();
}
});

btnUpdate.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
//getting data
String date=edtDate.getText().toString();
String title=spTitle.getSelectedItem().toString();
String amount=edtAmount.getText().toString();
//validating data
if(date.equals("")){
Toast.makeText(ModifyDetails.this,"Please Enter Date
!",Toast.LENGTH_LONG).show();
} else if(amount.equals("")) {
Toast.makeText(ModifyDetails.this, "Please Enter
Amount !", Toast.LENGTH_LONG).show();
} else if(title.equals("Select Title")){
Toast.makeText(ModifyDetails.this,"Please Select
Title !",Toast.LENGTH_LONG).show();
}else{
//checking income or expenses
if(title.equals("Income"))
myDatabase.updateData(String.valueOf(id),
date,amount,"0");
else
myDatabase.updateData(String.valueOf(id),
date,"0",amount);

Toast.makeText(ModifyDetails.this,"Data Updated
Successfully !",Toast.LENGTH_LONG).show();
finish();
}
}
});
}
}

Manifest File

AndroidManifest.xml

<activity android:name=".MainActivity" android:label="Dashboard">

<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.
category.LAUNCHER"/>
</intent-filter>
</activity>
<activity android:name=".DataEntry" android:label="Data Entry"/>
<activity android:name=".TodayDetails" android:label="Today's
Details"/>
<activity android:name=".ModifyDetails" android:label="Modify
Details"/>
<activity android:name=".DateWiseReport" android:label="Date Wise
Report"/>
</application>

</manifest>

Gradle Build File

build.gradle

dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:26.1.0'
implementation 'com.android.support:recyclerview-v7:26.1.0'
}
Sample Project -2 Jokes/Stories Application

Project Title – Jokes/Stories Application

Project Features-
• Jokes and stories can be added by admin.
• Admin can update/delete jokes/stories.
• All data are saved permanently on remote server.
• Users can read jokes/stories anytime/anywhere.
• Data once loaded are saved locally using SQLite.
• So, users are able to read jokes/stories even if there is no internet connection.

Project Files-
Project Prototype:
Database Tables

Necessary API’s

<?php
$user=$_POST["username"];
$pass=$_POST["password"];

$server="localhost";
$username="root";
$password="";
$database="bcatest";

// Create connection
$conn = new mysqli($server, $username, $password,$database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

//retrieving data
$sql = "SELECT * FROM tbllogin WHERE username='$user' AND
password='$pass'";
$result = $conn->query($sql);

if($result->num_rows>0)
echo "Success";
else
echo "Failed";

$conn->close();
?>
storedata.php
<?php

//getting post data

$title=$_POST["title"];
$category=$_POST["category"];
$description=$_POST["description"];

//server credentials
$server="localhost";
$username="root";
$password="";
$database="bcatest";

// Create connection
$conn = new mysqli($server, $username, $password,$database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

//inserting data
$sql = "INSERT INTO tbldata(title,category,description)
VALUES('".$title."','".$category."','".$description."')";
$result = $conn->query($sql);

if($result)
echo"Data Inserted Successfully !";
else
echo"Failed to Insert Data !";
$conn->close();
?>

getdetails.php

<?php
$server="localhost";
$username="root";
$password="";
$database="bcatest";

// Create connection
$conn = new mysqli($server,$username,$password,$database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

//retrieving data
$sql="SELECT * FROM tbldata ORDER BY id DESC";
$result = $conn->query($sql);

//encoding data in json format

$json = array();
if($result->num_rows>0){
while ($row = $result->fetch_array()) {
$json["data"][] =
array("id"=>$row["id"],"title"=>$row["title"],"category"=>$row["category
"],"description"=>$row["description"]);
}
}

echo json_encode($json);
$conn->close();
?>

updatedata.php

<?php

//getting post data

$id=$_POST["id"];
$title=$_POST["title"];
$category=$_POST["category"];
$description=$_POST["description"];

//server credentials
$server="localhost";
$username="root";
$password="";
$database="bcatest";

// Create connection
$conn = new mysqli($server, $username, $password,$database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

//updating data
$sql = "UPDATE tbldata SET title='$title', category='$category',
description='$description' WHERE id='$id'";
$result = $conn->query($sql);

if($result)
echo"Data Updated Successfully !";
else
echo"Failed to Update Data !";
$conn->close();
?>
deletedata.php

<?php

//getting post data

$id=$_POST["id"];

//server credentials
$server="localhost";
$username="root";
$password="";
$database="bcatest";

// Create connection
$conn = new mysqli($server, $username, $password,$database);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

//updating data
$sql = "DELETE FROM tbldata WHERE id='$id'";
$result = $conn->query($sql);

if($result)
echo"Data Deleted Successfully !";
else
echo"Failed to Delete Data !";
$conn->close();
?>

Connection Detector (Checking Internet Connection)

ConnectionDetector.java

public class ConnectionDetector {

private Context _context;

public ConnectionDetector(Context context){

this._context = context;
}

public boolean isConnectingToInternet(){

ConnectivityManager connectivity = (ConnectivityManager)
_context.getSystemService(Context.CONNECTIVITY_SERVICE);
if (connectivity != null)
{
NetworkInfo[] info = connectivity.getAllNetworkInfo();
if (info != null)
for (int i = 0; i < info.length; i++)
if (info[i].getState() ==
NetworkInfo.State.CONNECTED)
{
return true;
}

}
return false;
}
}

Local SQLite Database

MyDatabase.java

public class MyDatabase extends SQLiteOpenHelper{

// Database Version
private static final int DATABASE_VERSION = 1;
// Database Name
private static final String DATABASE_NAME = "mydbase";

public MyDatabase(Context context) {

super(context, DATABASE_NAME, null, DATABASE_VERSION);
}

// Creating Tables
@Override
public void onCreate(SQLiteDatabase db) {
// create notes table
String createQuery="CREATE TABLE mytable(id INTEGER PRIMARY KEY,
title TEXT,category TEXT,description TEXT)";
db.execSQL(createQuery);
}

//code to insert data

public void insertData(int id,String title, String category,
String description){
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues=new ContentValues();
contentValues.put("id",id);
contentValues.put("title",title);
contentValues.put("category",category);
contentValues.put("description",description);
//inserting row
db.insert("mytable",null,contentValues);
db.close();
}

//code to select data

public Cursor selectData(){
SQLiteDatabase db=this.getReadableDatabase();
String query="SELECT * FROM mytable";
Cursor cursor=db.rawQuery(query,null);
return cursor;
}

public Cursor selectData(String category){

SQLiteDatabase db=this.getReadableDatabase();
String query="SELECT * FROM mytable WHERE category=?";
Cursor cursor=db.rawQuery(query,new String[]{category});
return cursor;
}

//code to delete data

public void deleteData() {
SQLiteDatabase db = this.getWritableDatabase();
//deleting row
db.delete("mytable",null,null);
}
}

Dashboard

activity_main.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

</LinearLayout>
</LinearLayout>

MainActivity.java

public class MainActivity extends AppCompatActivity {

TextView txtJokes,txtStories;
MyDatabase myDatabase;
int totalJokes=0,totalStories=0;
ConnectionDetector cd;
Boolean isInternetPresent=false;
Cursor cursor;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.activity_main);

txtJokes=findViewById(R.id.txtJokes);
txtStories=findViewById(R.id.txtStories);
myDatabase=new MyDatabase(this);
cd=new ConnectionDetector(this);

//checking internet connection

isInternetPresent=cd.isConnectingToInternet();
if(isInternetPresent){
//no internet connection
//loading from sqlite
loadData();
}else{
//no internet
//loading from sqlite
cursor=myDatabase.selectData();
while (cursor.moveToNext()){
String category=cursor.getString(2);
if(category.equals("Jokes"))
totalJokes++;
else
totalStories++;
txtJokes.setText(totalJokes+"");
txtStories.setText(totalStories+"");
}
}

txtJokes.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(MainActivity.this,
ViewData.class);
intent.putExtra("category","Jokes");
startActivity(intent);
}
});

txtStories.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(MainActivity.this,
ViewData.class);
intent.putExtra("category","Stories");
startActivity(intent);
}
});

public void loadData(){

//displaying progress dialog
final ProgressDialog progress=new ProgressDialog(this);
progress.setMessage("Loading... Please Wait...");
progress.show();

RequestQueue queue = Volley.newRequestQueue(this);

//url for localhost with get request
String url ="http://10.0.2.2/myproject/getdetails.php";
// Request a string response from the provided URL.
StringRequest stringRequest = new
StringRequest(Request.Method.GET, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
progress.dismiss();
try {
//deleting all data from SQLite
myDatabase.deleteData();
JSONObject result=new JSONObject(response);
JSONArray array=result.getJSONArray("data");
for(int i=0;i<array.length();i++){
JSONObject data=array.getJSONObject(i);
int id=data.getInt("id");
String title=data.getString("title");
String category=data.getString ("category");
String description=data.getString("description");

//inserting to SQLite

myDatabase.insertData(id,title,category,description);

if(category.equals("Jokes"))
totalJokes++;
else
totalStories++;
}

//setting data
txtJokes.setText(totalJokes+"");
txtStories.setText(totalStories+"");

}catch (Exception ex){}

}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
//displaying error response message
Toast.makeText(MainActivity.this,error.toString(),
Toast.LENGTH_LONG).show();
progress.dismiss();
}
});
// Add the request to the RequestQueue.
queue.add(stringRequest);
}

//adding options menu

@Override
public boolean onCreateOptionsMenu(Menu menu) {
MenuInflater inflater = getMenuInflater();
inflater.inflate(R.menu.mymenu, menu);
return true;
}

//handling clicks
@Override
public boolean onOptionsItemSelected(MenuItem item) {
// Handle item selection
switch (item.getItemId()) {
case R.id.admin:
Intent intent=new Intent(MainActivity.this,Login.class);
startActivity(intent);
return true;

default:
return super.onOptionsItemSelected(item);
}
}

}
Displaying Data

view_data.xml

<?xml version="1.0" encoding="utf-8"?>

<android.support.v7.widget.RecyclerView
android:layout_width="match_parent"
android:id="@+id/recyclerview"
android:layout_height="wrap_content"/>

</LinearLayout>

list_items.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>
description.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

DataModel.java

public class DataModel {

private int id;
private String title;
private String category;
private String description;

public DataModel(int id,String title,String category,String

description){
this.id=id;
this.title=title;
this.category=category;
this.description=description;
}

public int getId(){

return id;
}

public String getTitle(){

return title;
}

public String getCategory(){

return category;
}

public String getDescription(){

return description;
}
}

RecyclerViewAdapter.java

public class RecyclerViewAdapter extends

RecyclerView.Adapter<RecyclerViewAdapter.ViewHolder> {
Activity context;
ArrayList<DataModel> data;

public RecyclerViewAdapter(Activity context, ArrayList<DataModel>

data){
this.context=context;
this.data=data;
}

@Override
public ViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {
LayoutInflater layoutInflater = LayoutInflater.from(context);
View listItem= layoutInflater.inflate(R.layout.list_items,
parent, false);
ViewHolder viewHolder = new ViewHolder(listItem);
return viewHolder;
}

@Override
public void onBindViewHolder(ViewHolder holder, int position) {
final DataModel current=data.get(position);
holder.txtTitle.setText("Title: "+current.getTitle());
holder.txtCategory.setText("Category: "+current.getCategory());
holder.txtDescription.setText("Description: "+
current.getDescription());

holder.linearLayout.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(context,Description.class);
intent.putExtra("id",current.getId());
intent.putExtra("title",current.getTitle());
intent.putExtra("category",current.getCategory());
intent.putExtra("description",current.getDescription());
context.startActivity(intent);
}
});
}

@Override
public int getItemCount() {
return data.size();
}

public static class ViewHolder extends RecyclerView.ViewHolder {

TextView txtTitle,txtCategory,txtDescription;
LinearLayout linearLayout;
public ViewHolder(View itemView) {
super(itemView);
txtTitle = itemView.findViewById(R.id.txtTitle);
txtCategory = itemView.findViewById(R.id.txtCategory);
txtDescription = itemView.findViewById(R.id.txtDescription);
linearLayout=itemView.findViewById(R.id.linear);
}
}
}

ViewData.java

public class ViewData extends AppCompatActivity {

RecyclerView recyclerView;
RecyclerView.Adapter recyclerAdapter;
RecyclerView.LayoutManager layoutManager;
String category="";
MyDatabase myDatabase;
Cursor cursor;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.view_data);
recyclerView=findViewById(R.id.recyclerview);
myDatabase=new MyDatabase(this);
Intent intent=getIntent();
category=intent.getStringExtra("category");

//loading data from sqlite

cursor=myDatabase.selectData(category);
ArrayList<DataModel> data=new ArrayList<>();
while (cursor.moveToNext()){
int id=cursor.getInt(0);
String title=cursor.getString(1);
String category=cursor.getString(2);
String description=cursor.getString(3);
DataModel dataModel=new DataModel
(id,title,category,description);
data.add(dataModel);
}
//displaying in recyclerview
layoutManager=new LinearLayoutManager(this);
recyclerAdapter=new RecyclerViewAdapter(this,data);
recyclerView.setLayoutManager(layoutManager);
recyclerView.setAdapter(recyclerAdapter);
}
}
Description.java

public class Description extends AppCompatActivity {

TextView txtTitle,txtCategory,txtDescription;
Button btnModify;
int id=0;
String title="",category="",description="";
public static boolean isLogin=false;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.description);

txtTitle=findViewById(R.id.txtTitle);
txtCategory=findViewById(R.id.txtCategory);
txtDescription=findViewById(R.id.txtDescription);
btnModify=findViewById(R.id.btnModify);

if(isLogin)
btnModify.setVisibility(View.VISIBLE);

Intent intent=getIntent();
id=intent.getIntExtra("id",0);
title=intent.getStringExtra("title");
category=intent.getStringExtra("category");
description=intent.getStringExtra("description");

txtTitle.setText("Title:\n"+title);
txtCategory.setText("Category: "+category);
txtDescription.setText("Description:\n"+description);

btnModify.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(Description.this,
ModifyJokesStories.class);
intent.putExtra("id",id);
intent.putExtra("title",title);
intent.putExtra("category",category);
intent.putExtra("description",description);
startActivity(intent);
finish();
}
});
}
}

Admin Panel

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

public class Login extends AppCompatActivity {

EditText edtUsername,edtPassword;
Button btnLogin;
ConnectionDetector cd;
Boolean isInternetPresent=false;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.login);

edtUsername=findViewById(R.id.edtUsername);
edtPassword=findViewById(R.id.edtPassword);
btnLogin=findViewById(R.id.btnLogin);
cd=new ConnectionDetector(this);

btnLogin.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
isInternetPresent=cd.isConnectingToInternet();
if(isInternetPresent)
CheckLogin();
else
Toast.makeText(Login.this,"Internet Connection
Required !",Toast.LENGTH_LONG).show();
}
});
}

public void CheckLogin(){

//Showing progress dialog
final ProgressDialog progress=new ProgressDialog(this);
progress.setMessage("Processing... Please Wait...");
progress.setCancelable(false);
progress.show();

RequestQueue queue = Volley.newRequestQueue(this);

String url ="http://10.0.2.2/myproject/login.php";
StringRequest stringRequest = new
StringRequest(Request.Method.POST, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
if(response.equals("Success")){
Description.isLogin=true;
Intent intent=new Intent(Login.this,
AdminPanel.class);
startActivity(intent);
finish();
}else{
Toast.makeText(Login.this,"Login Failed !",
Toast.LENGTH_LONG).show();
}
progress.dismiss();
}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
Toast.makeText(Login.this, error.toString(),
Toast.LENGTH_LONG).show();
progress.dismiss();
}
}){
//sending data to server
@Override
protected HashMap<String,String> getParams(){
HashMap<String,String> params = new HashMap<>();
params.put("username",edtUsername.getText().toString());
params.put("password",edtPassword.getText().toString());
return params;
}

};;
queue.add(stringRequest);
}
}

admin_panel.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

AdminPanel.java

public class AdminPanel extends AppCompatActivity {

Button btnCreate;
RecyclerView recyclerView;
RecyclerView.Adapter recyclerAdapter;
RecyclerView.LayoutManager layoutManager;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.admin_panel);
btnCreate=findViewById(R.id.btnCreate);

recyclerView=findViewById(R.id.recyclerview);

btnCreate.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent=new Intent(AdminPanel.this,
AddJokesStories.class);
startActivity(intent);
}
});

public void loadData(){

//displaying progress dialog
final ProgressDialog progress=new ProgressDialog(this);
progress.setMessage("Loading... Please Wait...");
progress.setCancelable(false);
progress.show();

RequestQueue queue = Volley.newRequestQueue(this);

//url for localhost with get request
String url =
"http://10.0.2.2/myproject/getdetails.php?category=All";
// Request a string response from the provided URL.
StringRequest stringRequest = new
StringRequest(Request.Method.GET, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
//passing data for decoding
decodeJson(response);
progress.dismiss();
}
}, new Response.ErrorListener() {

@Override
public void onErrorResponse(VolleyError error) {
//displaying error response message
Toast.makeText(AdminPanel.this,error.toString(),
Toast.LENGTH_LONG).show();
progress.dismiss();
}
});
// Add the request to the RequestQueue.
queue.add(stringRequest);
}

public void decodeJson(String response){

try{
ArrayList<DataModel> data=new ArrayList<>();
JSONObject result=new JSONObject(response);
JSONArray array=result.getJSONArray("data");
for(int i=0;i<array.length();i++){
JSONObject student=array.getJSONObject(i);
int sid=student.getInt("id");
String title=student.getString("title");
String category=student.getString("category");
String description=student.getString("description");
DataModel dataModel=new DataModel
(sid,title,category,description);
data.add(dataModel);
}
//plotting data in recyclerview
layoutManager=new LinearLayoutManager(this);
recyclerView.setLayoutManager(layoutManager);
recyclerAdapter=new RecyclerViewAdapter
(AdminPanel.this,data);
recyclerView.setAdapter(recyclerAdapter);

}catch (Exception ex){

Log.d("exception",ex.toString());
}
}

@Override
protected void onResume(){
super.onResume();
loadData();
}

Adding Jokes/Stories

add_jokes_stories.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

AddJokesStories.java

public class AddJokesStories extends AppCompatActivity {

EditText edtTitle,edtDescription;
Spinner spCategory;
Button btnSubmit;
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.add_jokes_stories);

edtTitle=findViewById(R.id.edtTitle);
edtDescription=findViewById(R.id.edtDescription);
spCategory=findViewById(R.id.spCategory);
btnSubmit=findViewById(R.id.btnSubmit);

btnSubmit.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
String title=edtTitle.getText().toString();
String category=spCategory.getSelectedItem().toString();
String description=edtDescription.getText().toString();
if(title.equals(""))
Toast.makeText(AddJokesStories.this,"Please Enter
Title !",Toast.LENGTH_LONG).show();
else if(category.equals("Select Category"))
Toast.makeText(AddJokesStories.this,"Please Select
Category !",Toast.LENGTH_LONG).show();
else if(description.equals(""))
Toast.makeText(AddJokesStories.this,"Please Enter
Description !",Toast.LENGTH_LONG).show();
else
submitData(title,category,description);
}
});
}

public void submitData(final String title, final String category,

final String description){
//Showing progress dialog
final ProgressDialog progress=new ProgressDialog(this);
progress.setMessage("Submitting... Please Wait...");
progress.setCancelable(false);
progress.show();

RequestQueue queue = Volley.newRequestQueue(this);

String url ="http://10.0.2.2/myproject/storedata.php";
StringRequest stringRequest = new
StringRequest(Request.Method.POST, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
Toast.makeText(AddJokesStories.this,response,
Toast.LENGTH_LONG).show();
progress.dismiss();
edtTitle.setText("");
spCategory.setSelection(0);
edtDescription.setText("");
}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
Toast.makeText(AddJokesStories.this, error.toString(),
Toast.LENGTH_LONG).show();
progress.dismiss();
}
}){
//sending data to server
@Override
protected HashMap<String,String> getParams(){
HashMap<String,String> params = new HashMap<>();
params.put("title",title);
params.put("category",category);
params.put("description",description);
return params;
}
};;
queue.add(stringRequest);
}
}

Modifying Jokes/Stories

modify_jokes_stories.xml

<?xml version="1.0" encoding="utf-8"?>

</LinearLayout>

ModifyJokesStories.java

public class ModifyJokesStories extends AppCompatActivity {

EditText edtTitle,edtDescription;
Spinner spCategory;
Button btnUpdate,btnDelete;
int id=0;
String title="",category="",description="",url="";
@Override
protected void onCreate(Bundle b){
super.onCreate(b);
setContentView(R.layout.modify_jokes_stories);

edtTitle=findViewById(R.id.edtTitle);
edtDescription=findViewById(R.id.edtDescription);
spCategory=findViewById(R.id.spCategory);
btnUpdate=findViewById(R.id.btnUpdate);
btnDelete=findViewById(R.id.btnDelete);

Intent intent=getIntent();
id=intent.getIntExtra("id",0);
title=intent.getStringExtra("title");
category=intent.getStringExtra("category");
description=intent.getStringExtra("description");

edtTitle.setText(title);
if(category.equals("Jokes"))
spCategory.setSelection(1);
else
spCategory.setSelection(2);
edtDescription.setText(description);

btnUpdate.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
title=edtTitle.getText().toString();
category=spCategory.getSelectedItem().toString();
description=edtDescription.getText().toString();
url="http://10.0.2.2/myproject/updatedata.php";
if(title.equals(""))
Toast.makeText(ModifyJokesStories.this,"Please Enter
Title !",Toast.LENGTH_LONG).show();
else if(category.equals("Select Category"))
Toast.makeText(ModifyJokesStories.this,"Please Select
Category !",Toast.LENGTH_LONG).show();
else if(description.equals(""))
Toast.makeText(ModifyJokesStories.this,"Please Enter
Description !",Toast.LENGTH_LONG).show();
else
submitData();
}
});

btnDelete.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
url="http://10.0.2.2/myproject/deletedata.php";
submitData();
}
});

public void submitData(){

//Showing progress dialog
final ProgressDialog progress=new ProgressDialog(this);
progress.setMessage("Submitting... Please Wait...");
progress.setCancelable(false);
progress.show();

RequestQueue queue = Volley.newRequestQueue(this);

StringRequest stringRequest = new
StringRequest(Request.Method.POST, url,
new Response.Listener<String>() {
@Override
public void onResponse(String response) {
Toast.makeText(ModifyJokesStories.this,response,
Toast.LENGTH_LONG).show();
progress.dismiss();
finish();
}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
Toast.makeText(ModifyJokesStories.this,
error.toString(),Toast.LENGTH_LONG).show();
progress.dismiss();
}
}){
//sending data to server
@Override
protected HashMap<String,String> getParams(){
HashMap<String,String> params = new HashMap<>();
params.put("id",String.valueOf(id));
params.put("title",title);
params.put("category",category);
params.put("description",description);
return params;
}
};;
queue.add(stringRequest);
}
}

Manifest File

AndroidManifest.xml

<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name=
"android.permission.ACCESS_NETWORK_STATE"/>
<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:roundIcon="@mipmap/ic_launcher_round"
android:supportsRtl="true"
android:theme="@style/AppTheme">

<activity android:name=".MainActivity" android:label="Dashboard">

<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name=
"android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>

<activity android:name=".Login" android:label="Login"/>

<activity android:name=".AddJokesStories" android:label="Create

Jokes/Stories"/>
<activity android:name=".Description"
android:label="Description"/>
<activity android:name=".ModifyJokesStories"
android:label="Modify Jokes/Stories"/>

</application>
</manifest>

Gradle Build File

build.gradle

dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:26.1.0'
implementation 'com.android.volley:volley:1.1.1'
implementation 'com.android.support:recyclerview-v7:26.1.0'
}
Lab Sheet Questions (Sample)
Following are the list of some topics on which student’s can create their project on:

1. Project Title: Mobile Quiz Application

Features:
• Use of SQLite and remote server for data storage.
• Adding and modifying multiple choice questions by admin.
• Users can view 10 questions which will be available in random order and
answer those questions.
• After submitting answers, finally users must be able to view score among
those 10 questions.

2. Project Title: Diet and Health Monitoring Application

Features:
• Use of SQLite and remote server for data storage.
• Adding and modifying information related to deit and health by admin.
• Users must be able to view those added information.

3. Project Title: Mobile Attendance System

Features:
• Use of SQLite and remote server for data storage.
• An interface to enter the number of students in the classroom.
• Attendance marking and storage
• Generation of daily, weekly and monthly report.

4. Project Title: Food Ordering System for Hotel

Features:
• The number of tables present in the restaurants will be shown on one page.
• Food categorize
• No of Orders from the particular table stored in the database
• Generation of Bill

5. Project Title: Leave Management System for School/College

Features:
• Signup and login page for students.
• Students can add leave note using App.
• Admin can view leave notes.

6. Project Title: Blood Bank Management System

Features:
• Use of SQLite and remote server for data storage.
• Admin can add blood groups details (person name, address, gender, age,
etc.)
• User can view those added information.
• Should implement search feature.
7. Project Title: Movie Ticket Booking App
Features:
• Admin can add movies, schedule, price and other informations.
• Users can view information related to movies.
• Rating of movie

8. Project Title: Scientific Calculator App

Features:
• Buttons or tab option for choosing functions
• text, numeric and special character display option
• Functions and methods for Calculation
• Results view option

9. Project Title: Chat-based App

Features:
• User login interface
• Show list of users
• Chat interface

10. Project Title: Online Voting System

Features:
• An online database to store Information
• Adding and manipulation of candidates
• User Login Authentication
• Interface for Voting
• Voting results

11. Project Title: Hotel Booking System

Features:
• Online database required
• User login
• Search option for place and hotels
• Booking and Cancelling option

12. Project Title: Dictionary App

Features:
• Use of SQLite and remote server for data storage.
• Add New Worlds
• Update New Words
• Delete Existing Words
• Easy Search Option

Mobile Programming Basics
No ratings yet
Mobile Programming Basics
14 pages
Unit 1 Introduction To Mobile and Mobile Programming
No ratings yet
Unit 1 Introduction To Mobile and Mobile Programming
18 pages
Unit 3 Mobile Operating Systems: Structure
No ratings yet
Unit 3 Mobile Operating Systems: Structure
24 pages
WCMC Chapter 2 - Mobile Computing - Concise
No ratings yet
WCMC Chapter 2 - Mobile Computing - Concise
43 pages
Mobile Computing Overview & Features
No ratings yet
Mobile Computing Overview & Features
16 pages
Wireless Communication
No ratings yet
Wireless Communication
10 pages
Mobile Computing
No ratings yet
Mobile Computing
39 pages
P.I. Alejandro Fdez
No ratings yet
P.I. Alejandro Fdez
4 pages
Mobile Computing
No ratings yet
Mobile Computing
22 pages
Mobile Communication & Web Analytics Activity1 1
No ratings yet
Mobile Communication & Web Analytics Activity1 1
5 pages
Introducing Today's Technologies: Computers, Devices, and The Web
No ratings yet
Introducing Today's Technologies: Computers, Devices, and The Web
58 pages
Ii - MSC - CS - Mobile Computing
No ratings yet
Ii - MSC - CS - Mobile Computing
149 pages
Types of Computers Explained
No ratings yet
Types of Computers Explained
62 pages
Crisostomo AssignmentCont MC
No ratings yet
Crisostomo AssignmentCont MC
3 pages
Chapter 1
No ratings yet
Chapter 1
21 pages
Chapter 2
No ratings yet
Chapter 2
18 pages
EnggRoom - Code - Mobile Computing
No ratings yet
EnggRoom - Code - Mobile Computing
21 pages
Unit 1
No ratings yet
Unit 1
18 pages
2 - Mobile Devices - Sub Topic 1.1
No ratings yet
2 - Mobile Devices - Sub Topic 1.1
21 pages
CYBERCRIMES
No ratings yet
CYBERCRIMES
1 page
Chapter 2
No ratings yet
Chapter 2
28 pages
Mobile Computing Less1
No ratings yet
Mobile Computing Less1
74 pages
Mobile Applications Development Unit - 1
100% (1)
Mobile Applications Development Unit - 1
25 pages
Touch Design For Mobile Interfaces Sample Chapter
No ratings yet
Touch Design For Mobile Interfaces Sample Chapter
40 pages
WCMC Chapter 2 - Mobile Computing Edited
No ratings yet
WCMC Chapter 2 - Mobile Computing Edited
26 pages
Chapter-2 Mobile Computing
No ratings yet
Chapter-2 Mobile Computing
67 pages
CHAPTER 3 - Computers and Mobile Devices
No ratings yet
CHAPTER 3 - Computers and Mobile Devices
40 pages
WCMC Chapter 2 - Mobile Computing Edited
No ratings yet
WCMC Chapter 2 - Mobile Computing Edited
32 pages
Unit 4 Chapter 19, 20 Ppts
No ratings yet
Unit 4 Chapter 19, 20 Ppts
32 pages
Chapter-Two Mobile Computing
No ratings yet
Chapter-Two Mobile Computing
17 pages
Chapter 3
No ratings yet
Chapter 3
34 pages
KERJA KHUSUS ICT Latest Development in Networks and Communications
No ratings yet
KERJA KHUSUS ICT Latest Development in Networks and Communications
10 pages
WCMC Chapter 2 - Mobile Computing - Concise
No ratings yet
WCMC Chapter 2 - Mobile Computing - Concise
26 pages
Wireless Communication Part I II
No ratings yet
Wireless Communication Part I II
113 pages
Chapter 1
No ratings yet
Chapter 1
38 pages
1.1.1 Contemporary Digital Devices
No ratings yet
1.1.1 Contemporary Digital Devices
38 pages
Presentation 4
No ratings yet
Presentation 4
16 pages
INTCOM Merged
No ratings yet
INTCOM Merged
20 pages
What Is Mobile Computing
No ratings yet
What Is Mobile Computing
3 pages
Topic 1
No ratings yet
Topic 1
18 pages
Computer and Mobile Devices: Evaluating Options For Home and Work
No ratings yet
Computer and Mobile Devices: Evaluating Options For Home and Work
42 pages
OEC CS 801C Ecommerce and ERP
No ratings yet
OEC CS 801C Ecommerce and ERP
12 pages
Chapter - 1a - Mobile Apps Overview
No ratings yet
Chapter - 1a - Mobile Apps Overview
44 pages
Topic 1 - Digital Devices
100% (1)
Topic 1 - Digital Devices
69 pages
Tia4 PPT ch08
No ratings yet
Tia4 PPT ch08
42 pages
Chapter 1 - Mobile Computing From AAU
No ratings yet
Chapter 1 - Mobile Computing From AAU
108 pages
Block 2 - Unit 1
No ratings yet
Block 2 - Unit 1
31 pages
Chapter1 2
No ratings yet
Chapter1 2
42 pages
Mobapp Reviewer
No ratings yet
Mobapp Reviewer
17 pages
Cybercrime: Mobile & Wireless Devices
No ratings yet
Cybercrime: Mobile & Wireless Devices
26 pages
Unit 3
No ratings yet
Unit 3
22 pages
Mob Comp Chapter 1
No ratings yet
Mob Comp Chapter 1
14 pages
UNIT - III: Cybercrime Mobile and Wireless Devices
No ratings yet
UNIT - III: Cybercrime Mobile and Wireless Devices
23 pages
Cybersecurity Unit-2 Notes
No ratings yet
Cybersecurity Unit-2 Notes
47 pages
Lesson 3 - Computer and Mobile Devices Presentation
No ratings yet
Lesson 3 - Computer and Mobile Devices Presentation
49 pages
Chapter - 1 A - Mobile Computing
100% (1)
Chapter - 1 A - Mobile Computing
64 pages
Widyatama - Lecture.applied Networking - IV Week03 Mobile Networking
No ratings yet
Widyatama - Lecture.applied Networking - IV Week03 Mobile Networking
43 pages