SUMMER TRAINING REPORT

On
Android App Development
Taken At

ThinkNextLearning

In partial fulfilment for award of the

Degree Of
Bachelors of Technology
In Department of Computer Science & Information Technology

SUBMITTED TO: SUBMITTED BY:

Mrs. Anita Chaudhary Devanshu Jain

18EEACS020
(18CS20)

Department of Computer Science & Information Technology

Engineering College Ajmer 2020-21
 Declaration
I Devanshu Jain Roll number 18EEACS020, student of Bachelors of
Technology (CSE), a class of 2018 – 2022, Engineering College Ajmer
hereby declare that the Summer Training project report entitled Android
App Development is an original work and the same has not been submitted
to any other Institute for the reward of any other degree.

Date: 22 July,2021

Devanshu Jain

Roll number: 18EEACS020

Computer science and Engineering

 Acknowledgement
I have taken efforts in this industrial training. However, it would not have
been possible without the kind support and help of many individuals and
organizations. I would like to extend my sincere thanks to all of them.

First and foremost, I wish to record our sincere gratitude to Thinknext

Coordinators for their constant support and encouragement in preparation of
this report and for making available videos and interface facilities needed to
prepare this report.

Last but not least, we wish to thank our parents for financing our studies in
this college as well as for constantly encouraging us to learn engineering.
Their personal sacrifice in providing the opportunity to learn engineering is
gratefully acknowledged.
Summer Training Certificate
 Introduction

Android is an open source and Linux-based Operating System for mobile devices such

as smartphones and tablet computers. Android was developed by the Open Handset
Alliance, led by Google, and other companies.
Android offers a unified approach to application development for mobile devices which
means developers need only develop for Android, and their applications should be able
to run on different devices powered by Android.
The first beta version of the Android Software Development Kit (SDK) was released by
Google in 2007 where as the first commercial version, Android 1.0, was released in
September 2008.
On June 27, 2012, at the Google I/O conference, Google announced the next Android
version, 4.1 Jelly Bean. Jelly Bean is an incremental update, with the primary aim of
improving the user interface, both in terms of functionality and performance.
The source code for Android is available under free and open source software licenses.
Google publishes most of the code under the Apache License version 2.0 and the rest,
Linux kernel changes, under the GNU General Public License version 2.
 Android - Architecture

Android operating system is a stack of software components which is roughly divided

into five sections and four main layers as shown below in the architecture diagram.

Linux kernel
At the bottom of the layers is Linux - Linux 3.6 with approximately 115 patches. This
provides a level of abstraction between the device hardware and it contains all the
essential hardware drivers like camera, keypad, display etc. Also, the kernel handles all
the things that Linux is really good at such as networking and a vast array of device
drivers, which take the pain out of interfacing to peripheral hardware.
Libraries
On top of Linux kernel there is a set of libraries including open-source Web browser
engine WebKit, well known library libc, SQLite database which is a useful repository for
storage and sharing of application data, libraries to play and record audio and video,
SSL libraries responsible for Internet security etc.

Android Libraries
This category encompasses those Java-based libraries that are specific to Android
development. Examples of libraries in this category include the application framework
libraries in addition to those that facilitate user interface building, graphics drawing and
database access. A summary of some key core Android libraries available to the
Android developer is as follows −
 android.app − Provides access to the application model and is the cornerstone of
all Android applications.
 android.content − Facilitates content access, publishing and messaging between
applications and application components.
 android.database − Used to access data published by content providers and
includes SQLite database management classes.
 android.opengl − A Java interface to the OpenGL ES 3D graphics rendering API.
 android.os − Provides applications with access to standard operating system
services including messages, system services and inter-process communication.
 android.text − Used to render and manipulate text on a device display.
 android.view − The fundamental building blocks of application user interfaces.
 android.widget − A rich collection of pre-built user interface components such as
buttons, labels, list views, layout managers, radio buttons etc.
 android.webkit − A set of classes intended to allow web-browsing capabilities to
be built into applications.
Having covered the Java-based core libraries in the Android runtime, it is now time to
turn our attention to the C/C++ based libraries contained in this layer of the Android
software stack.
Android Runtime
This is the third section of the architecture and available on the second layer from the
bottom. This section provides a key component called Dalvik Virtual Machine which is
a kind of Java Virtual Machine specially designed and optimized for Android.
The Dalvik VM makes use of Linux core features like memory management and multi-
threading, which is intrinsic in the Java language. The Dalvik VM enables every Android
application to run in its own process, with its own instance of the Dalvik virtual
machine.
The Android runtime also provides a set of core libraries which enable Android
application developers to write Android applications using standard Java programming
language.

Application Framework
The Application Framework layer provides many higher-level services to applications in
the form of Java classes. Application developers are allowed to make use of these
services in their applications.
The Android framework includes the following key services −
 Activity Manager − Controls all aspects of the application lifecycle and activity
stack.
 Content Providers − Allows applications to publish and share data with other
applications.
 Resource Manager − Provides access to non-code embedded resources such as
strings, color settings and user interface layouts.
 Notifications Manager − Allows applications to display alerts and notifications to
the user.
 View System − An extensible set of views used to create application user
interfaces.

Applications
You will find all the Android application at the top layer. You will write your application
to be installed on this layer only. Examples of such applications are Contacts Books,
Browser, Games etc.
 Android - Application Components

Application components are the essential building blocks of an Android application.

These components are loosely coupled by the application manifest
file AndroidManifest.xml that describes each component of the application and how
they interact.
There are following four main components that can be used within an Android
application –

Sr.No Components & Description

1 Activities
They dictate the UI and handle the user interaction to the smart phone screen.

Services
2
They handle background processing associated with an application.

Broadcast Receivers
3
They handle communication between Android OS and applications.

Content Providers
4
They handle data and database management issues.

Activities
An activity represents a single screen with a user interface, in-short Activity performs
actions on the screen. For example, an email application might have one activity that
shows a list of new emails, another activity to compose an email, and another activity
for reading emails. If an application has more than one activity, then one of them
should be marked as the activity that is presented when the application is launched.
An activity is implemented as a subclass of Activity class as follows −
public class MainActivity extends Activity {
}

Services
A service is a component that runs in the background to perform long-running
operations. For example, a service might play music in the background while the user is
in a different application, or it might fetch data over the network without blocking user
interaction with an activity.
A service is implemented as a subclass of Service class as follows −
public class MyService extends Service {
}

Broadcast Receivers
Broadcast Receivers simply respond to broadcast messages from other applications or
from the system. For example, applications can also initiate broadcasts to let other
applications know that some data has been downloaded to the device and is available
for them to use, so this is broadcast receiver who will intercept this communication and
will initiate appropriate action.
A broadcast receiver is implemented as a subclass of BroadcastReceiver class and each
message is broadcaster as an Intent object.
public class MyReceiver extends BroadcastReceiver {
public void onReceive(context,intent){}
}

Content Providers
A content provider component supplies data from one application to others on
request. Such requests are handled by the methods of
the ContentResolver class. The data may be stored in the file system, the
database or somewhere else entirely.
A content provider is implemented as a subclass of ContentProvider class and
must implement a standard set of APIs that enable other applications to perform
transactions.
public class MyContentProvider extends ContentProvider {
public void onCreate(){}
}
We will go through these tags in detail while covering application components in
individual chapters.

Additional Components

There are additional components which will be used in the construction of above
mentioned entities, their logic, and wiring between them. These components are –

S.No Components & Description

1 Fragments
Represents a portion of user interface in an Activity.

Views
2
UI elements that are drawn on-screen including buttons, lists forms etc.

Layouts
3
View hierarchies that control screen format and appearance of the views.

Intents
4
Messages wiring components together.

Resources
5
External elements, such as strings, constants and drawable pictures.

Manifest
6
Configuration file for the application.
 Android – Activities
An activity represents a single screen with a user interface just like window or frame of
Java. Android activity is the subclass of ContextThemeWrapper class.
The Activity class defines the following call backs i.e. events. You don't need to
implement all the callbacks methods. However, it's important that you understand
each one and implement those that ensure your app behaves the way users expect.

Sr.N Callback & Description

o

1 onCreate()
This is the first callback and called when the activity is first created.

onStart()
2
This callback is called when the activity becomes visible to the user.

onResume()
3
This is called when the user starts interacting with the application.

onPause()

4 The paused activity does not receive user input and cannot execute any code and
called when the current activity is being paused and the previous activity is being
resumed.

onStop()
5
This callback is called when the activity is no longer visible.

onDestroy()
6
This callback is called before the activity is destroyed by the system.

onRestart()
7
This callback is called when the activity restarts after stopping it.
 Android – Services
A service is a component that runs in the background to perform long-running
operations without needing to interact with the user and it works even if
application is destroyed. A service can essentially take two states –

Sr.No State & Description

.

1
Started
A service is started when an application component, such as an activity, starts it
by calling startService(). Once started, a service can run in the background
indefinitely, even if the component that started it is destroyed.

2
Bound
A service is bound when an application component binds to it by
calling bindService(). A bound service offers a client-server interface that allows
components to interact with the service, send requests, get results, and even do
so across processes with interprocess communication (IPC).

A service has life cycle callback methods that you can implement to monitor changes in
the service's state and you can perform work at the appropriate stage. The following
diagram on the left shows the life cycle when the service is created with startService()
and the diagram on the right shows the life cycle when the service is created with
bindService(): (image courtesy : android.com )
To create an service, you create a Java class that extends the Service base class or one
of its existing subclasses. The Service base class defines various callback methods and
the most important are given below. You don't need to implement all the callbacks
methods. However, it's important that you understand each one and implement those
that ensure your app behaves the way users expect.

Sr.No Callback & Description

.

1
onStartCommand()
 The system calls this method when another component, such as an activity,
requests that the service be started, by calling startService(). If you implement this
method, it is your responsibility to stop the service when its work is done, by
calling stopSelf() or stopService() methods.

2
onBind()
The system calls this method when another component wants to bind with the
service by calling bindService(). If you implement this method, you must provide
an interface that clients use to communicate with the service, by returning
an IBinder object. You must always implement this method, but if you don't want
to allow binding, then you should return null.

3
onUnbind()
The system calls this method when all clients have disconnected from a particular
interface published by the service.

4
onRebind()
The system calls this method when new clients have connected to the service,
after it had previously been notified that all had disconnected in
its onUnbind(Intent).

5
onCreate()
The system calls this method when the service is first created
using onStartCommand() or onBind(). This call is required to perform one-time
set-up.

6
onDestroy()
The system calls this method when the service is no longer used and is being
destroyed. Your service should implement this to clean up any resources such as
threads, registered listeners, receivers, etc.

The following skeleton service demonstrates each of the life cycle methods –

package com.tutorialspoint;
import android.app.Service;
import android.os.IBinder;
import android.content.Intent;
import android.os.Bundle;

public class HelloService extends Service {

/** indicates how to behave if the service is killed */

int mStartMode;

/** interface for clients that bind */

IBinder mBinder;

/** indicates whether onRebind should be used */

boolean mAllowRebind;

/** Called when the service is being created. */

@Override
public void onCreate() {

/** The service is starting, due to a call to startService() */

@Override
public int onStartCommand(Intent intent, int flags, int startId) {
return mStartMode;
}

/** A client is binding to the service with bindService() */

@Override
public IBinder onBind(Intent intent) {
return mBinder;
}

/** Called when all clients have unbound with unbindService() */

@Override
public boolean onUnbind(Intent intent) {
return mAllowRebind;
}

/** Called when a client is binding to the service with

bindService()*/
@Override
public void onRebind(Intent intent) {

/** Called when The service is no longer used and is being destroyed
*/
 @Override
public void onDestroy() {

}
}

Example
This example will take you through simple steps to show how to create your own
Android Service. Follow the following steps to modify the Android application we
created in Hello World Example chapter –

Ste Description
p

1 You will use Android StudioIDE to create an Android application and name it as My
Application under a package com.example.tutorialspoint7.myapplication as explained in
the Hello World Example chapter.

2 Modify main activity file MainActivity.java to add startService() and stopService() methods.

3 Create a new java file MyService.java under the package com.example.My Application. This

file will have implementation of Android service related methods.

4 Define your service in AndroidManifest.xml file using <service.../> tag. An application can

have one or more services without any restrictions.

5 Modify the default content of res/layout/activity_main.xml file to include two buttons in linear

layout.

6 No need to change any constants in res/values/strings.xml file. Android studio take care of

string values

7 Run the application to launch Android emulator and verify the result of the changes done in
the application.
Following is the content of the modified main activity file MainActivity.java. This file can
include each of the fundamental life cycle methods. We have
added startService() and stopService() methods to start and stop the service.

package com.example.tutorialspoint7.myapplication;

import android.content.Intent;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;

import android.os.Bundle;
import android.app.Activity;
import android.util.Log;
import android.view.View;

public class MainActivity extends Activity {

String msg = "Android : ";

/** Called when the activity is first created. */

@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
Log.d(msg, "The onCreate() event");
}

public void startService(View view) {

startService(new Intent(getBaseContext(), MyService.class));
}

// Method to stop the service

public void stopService(View view) {
stopService(new Intent(getBaseContext(), MyService.class));
}
}

Following is the content of MyService.java. This file can have implementation of one or
more methods associated with Service based on requirements. For now we are going
to implement only two methods onStartCommand() and onDestroy() –

package com.example.tutorialspoint7.myapplication;
import android.app.Service;
import android.content.Intent;
import android.os.IBinder;
import android.support.annotation.Nullable;
import android.widget.Toast;

/**
* Created by TutorialsPoint7 on 8/23/2016.
*/

public class MyService extends Service {

@Nullable
@Override
public IBinder onBind(Intent intent) {
return null;
}

@Override
public int onStartCommand(Intent intent, int flags, int startId) {
// Let it continue running until it is stopped.
Toast.makeText(this, "Service Started", Toast.LENGTH_LONG).show();
return START_STICKY;
}

@Override
public void onDestroy() {
super.onDestroy();
Toast.makeText(this, "Service Destroyed",
Toast.LENGTH_LONG).show();
}
}

Following will the modified content of AndroidManifest.xml file. Here we have added

<service.../> tag to include our service –

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

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.tutorialspoint7.myapplication">

<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:supportsRtl="true"
android:theme="@style/AppTheme">
 <activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />

<category android:name="android.intent.category.LAUNCHER" />

</intent-filter>
</activity>

<service android:name=".MyService" />

</application>

</manifest>

Following will be the content of res/layout/activity_main.xml file to include two

buttons −
<RelativeLayout
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
android:paddingBottom="@dimen/activity_vertical_margin"
tools:context=".MainActivity">

<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Example of services"
android:layout_alignParentTop="true"
android:layout_centerHorizontal="true"
android:textSize="30dp" />

<TextView
android:id="@+id/textView2"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Tutorials point "
android:textColor="#ff87ff09"
android:textSize="30dp"
android:layout_above="@+id/imageButton"
android:layout_centerHorizontal="true"
android:layout_marginBottom="40dp" />
 <ImageButton
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/imageButton"
android:src="@drawable/abc"
android:layout_centerVertical="true"
android:layout_centerHorizontal="true" />

<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/button2"
android:text="Start Services"
android:onClick="startService"
android:layout_below="@+id/imageButton"
android:layout_centerHorizontal="true" />

<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Stop Services"
android:id="@+id/button"
android:onClick="stopService"
android:layout_below="@+id/button2"
android:layout_alignLeft="@+id/button2"
android:layout_alignStart="@+id/button2"
android:layout_alignRight="@+id/button2"
android:layout_alignEnd="@+id/button2" />

</RelativeLayout>
 Android - Broadcast Receivers
Broadcast Receivers simply respond to broadcast messages from other applications or
from the system itself. These messages are sometime called events or intents.

For example, applications can also initiate broadcasts to let other applications know that
some data has been downloaded to the device and is available for them to use, so this is
broadcast receiver who will intercept this communication and will initiate appropriate
action.

There are following two important steps to make BroadcastReceiver works for the
system broadcasted intents −
 Creating the Broadcast Receiver.
 Registering Broadcast Receiver
There is one additional steps in case you are going to implement your custom intents
then you will have to create and broadcast those intents.

Creating the Broadcast Receiver

A broadcast receiver is implemented as a subclass of BroadcastReceiver class and
overriding the onReceive() method where each message is received as a Intent object
parameter.
public class MyReceiver extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {
Toast.makeText(context, "Intent Detected.",
Toast.LENGTH_LONG).show();
}
}

Registering Broadcast Receiver

An application listens for specific broadcast intents by registering a broadcast receiver
in AndroidManifest.xml file. Consider we are going to register MyReceiver for system
generated event ACTION_BOOT_COMPLETED which is fired by the system once the
Android system has completed the boot process.

Broadcast-Receiver
<application
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<receiver android:name="MyReceiver">

<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED">
</action>
</intent-filter>

</receiver>
</application>

Now whenever your Android device gets booted, it will be intercepted by

BroadcastReceiver MyReceiver and implemented logic inside onReceive() will be
executed.

There are several system generated events defined as final static fields in
the Intent class. The following table lists a few important system events.
Sr.N Event Constant & Description
o

android.intent.action.BATTERY_CHANGED
1
Sticky broadcast containing the charging state, level, and other information about
the battery.

android.intent.action.BATTERY_LOW
2
Indicates low battery condition on the device.

android.intent.action.BATTERY_OKAY
3
Indicates the battery is now okay after being low.

android.intent.action.BOOT_COMPLETED
4
This is broadcast once, after the system has finished booting.

android.intent.action.BUG_REPORT
5
Show activity for reporting a bug.

android.intent.action.CALL
6
Perform a call to someone specified by the data.

android.intent.action.CALL_BUTTON
7 The user pressed the "call" button to go to the dialer or other appropriate UI for
placing a call.

android.intent.action.DATE_CHANGED
8
The date has changed.

android.intent.action.REBOOT
9
Have the device reboot.
Broadcasting Custom Intents

If you want your application itself should generate and send custom intents then you
will have to create and send those intents by using the sendBroadcast() method inside
your activity class. If you use the sendStickyBroadcast(Intent) method, the Intent
is sticky, meaning the Intent you are sending stays around after the broadcast is
complete.

public void broadcastIntent(View view) {

Intent intent = new Intent();
intent.setAction("com.tutorialspoint.CUSTOM_INTENT");
sendBroadcast(intent);
}

This intent com.tutorialspoint.CUSTOM_INTENT can also be registered in similar way as

we have regsitered system generated intent.

<application
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<receiver android:name="MyReceiver">

<intent-filter>
<action android:name="com.tutorialspoint.CUSTOM_INTENT">
</action>
</intent-filter>

</receiver>
</application>

Example
This example will explain you how to create BroadcastReceiver to intercept custom
intent. Once you are familiar with custom intent, then you can program your
application to intercept system generated intents. So let's follow the following steps to
modify the Android application we created in Hello World Example chapter –
 Ste Description
p

1 You will use Android studio to create an Android application and name it as My
Application under a package com.example.tutorialspoint7.myapplication as explained in
the Hello World Example chapter.

2 Modify main activity file MainActivity.java to add broadcastIntent() method.

3 Create a new java file called MyReceiver.java under the

package com.example.tutorialspoint7.myapplication to define a BroadcastReceiver.

4 An application can handle one or more custom and system intents without any restrictions.
Every intent you want to intercept must be registered in your AndroidManifest.xml file using
<receiver.../> tag

5 Modify the default content of res/layout/activity_main.xml file to include a button to

broadcast intent.

6 No need to modify the string file, Android studio take care of string.xml file.

7 Run the application to launch Android emulator and verify the result of the changes done in
the application.

Following is the content of the modified main activity file MainActivity.java. This file
can include each of the fundamental life cycle methods. We have
added broadcastIntent() method to broadcast a custom intent.
package com.example.tutorialspoint7.myapplication;

import android.app.Activity;
import android.content.Intent;
import android.os.Bundle;
import android.view.View;
public class MainActivity extends Activity {

/** Called when the activity is first created. */

@Override

public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}

// broadcast a custom intent.

public void broadcastIntent(View view){

Intent intent = new Intent();
intent.setAction("com.tutorialspoint.CUSTOM_INTENT");
sendBroadcast(intent);
}
}

Following is the content of MyReceiver.java:

package com.example.tutorialspoint7.myapplication;

import android.content.BroadcastReceiver;
import android.content.Context;
import android.content.Intent;
import android.widget.Toast;

/**
* Created by TutorialsPoint7 on 8/23/2016.
*/
public class MyReceiver extends BroadcastReceiver{
@Override
public void onReceive(Context context, Intent intent) {
Toast.makeText(context, "Intent Detected.",
Toast.LENGTH_LONG).show();
}
}

Following will the modified content of AndroidManifest.xml file. Here we have added

<receiver.../> tag to include our service:

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

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.tutorialspoint7.myapplication">

<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:supportsRtl="true"
android:theme="@style/AppTheme">

<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />

<category android:name="android.intent.category.LAUNCHER" />

</intent-filter>
</activity>

<receiver android:name="MyReceiver">
<intent-filter>
<action android:name="com.tutorialspoint.CUSTOM_INTENT">
</action>
</intent-filter>

</receiver>
</application>

</manifest>

Following will be the content of res/layout/activity_main.xml file to include a button

to broadcast our custom intent −
<RelativeLayout
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
android:paddingBottom="@dimen/activity_vertical_margin"
tools:context=".MainActivity">

<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
 android:text="Example of Broadcast"
android:layout_alignParentTop="true"
android:layout_centerHorizontal="true"
android:textSize="30dp" />

<TextView
android:id="@+id/textView2"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Tutorials point "
android:textColor="#ff87ff09"
android:textSize="30dp"
android:layout_above="@+id/imageButton"
android:layout_centerHorizontal="true"
android:layout_marginBottom="40dp" />

<ImageButton
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/imageButton"
android:src="@drawable/abc"
android:layout_centerVertical="true"
android:layout_centerHorizontal="true" />

<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/button2"
android:text="Broadcast Intent"
android:onClick="broadcastIntent"
android:layout_below="@+id/imageButton"
android:layout_centerHorizontal="true" />

</RelativeLayout>
 Publishing Android Application

Android application publishing is a process that makes your Android applications

available to users. Infect, publishing is the last phase of the Android application
development process.

Android development life cycle

Once we developed and fully tested your Android Application, we can start selling or
distributing free using Google Play (A famous Android marketplace).
we can also release our applications by sending them directly to users or by letting
users download them from your own website.
we can check a detailed publishing process at Android official website, but this tutorial
will take you through simple steps to launch your application on Google Play. Here is a
simplified check list which will help you in launching your Android application –
Ste Activity
p

1 Regression Testing Before you publish your application, you need to make sure that its
meeting the basic quality expectations for all Android apps, on all of the devices that you are
targeting. So perform all the required testing on different devices including phone and
tablets.

2 Application Rating When you will publish your application at Google Play, you will have to
specify a content rating for your app, which informs Google Play users of its maturity level.
Currently available ratings are (a) Everyone (b) Low maturity (c) Medium maturity (d) High
maturity.

3 Targeted Regions Google Play lets you control what countries and territories where your
application will be sold. Accordingly you must take care of setting up time zone, localization
or any other specific requirement as per the targeted region.

4 Application Size Currently, the maximum size for an APK published on Google Play is 50
MB. If your app exceeds that size, or if you want to offer a secondary download, you can
use APK Expansion Files, which Google Play will host for free on its server infrastructure
and automatically handle the download to devices.

5 SDK and Screen Compatibility It is important to make sure that your app is designed to
run properly on the Android platform versions and device screen sizes that you want to
target.

6 Application Pricing Deciding whether you app will be free or paid is important because, on
Google Play, free app's must remain free. If you want to sell your application then you will
have to specify its price in different currencies.

7 Promotional Content It is a good marketing practice to supply a variety of high-quality

graphic assets to showcase your app or brand. After you publish, these appear on your
product details page, in store listings and search results, and elsewhere.

8 Build and Upload release-ready APK The release-ready APK is what you you will upload
to the Developer Console and distribute to users. You can check complete detail on how to
create a release-ready version of your app: Preparing for Release.

9 Finalize Application Detail Google Play gives you a variety of ways to promote your app
 and engage with users on your product details page, from colourful graphics, screen shots,
and videos to localized descriptions, release details, and links to your other apps. So you
can decorate your application page and provide as much as clear crisp detail you can
provide.

Export Android Application Process

Apk development process

Before exporting the apps, you must some of tools
 Dx tools(Dalvik executable tools ): It going to convert .class file to .dex file. it has
useful for memory optimization and reduce the boot-up speed time
 AAPT(Android assistance packaging tool):it has useful to convert .Dex file to.Apk
 APK(Android packaging kit): The final stage of deployment process is called as
.apk.
You will need to export your application as an APK (Android Package) file before you
upload it Google Play marketplace.
To export an application, just open that application project in Android studio and
select Build → Generate Signed APK from your Android studio and follow the simple
steps to export your application −
Next select, Generate Signed APK option as shown in the above screen shot and then
click it so that you get following screen where you will choose Create new keystore to
store your application.

Enter your key store path,key store password,key alias and key password to protect
your application and click on Next button once again. It will display following screen to
let you create an application −
Once you filled up all the information,like app destination,build type and flavours
click finish button While creating an application it will show as below

Finally, it will generate your Android Application as APK formate File which will be
uploaded at Google Play marketplace.

Google Play Registration

The most important step is to register with Google Play using Google Play Marketplace.
You can use your existing google ID if you have any otherwise you can create a new
Google ID and then register with the marketplace. You will have following screen to
accept terms and condition.
You can use Continue to payment button to proceed to make a payment of $25 as a
registration fee and finally to complete your account detail.
Once you are a registered user at Google Play, you can upload release-ready APK for
your application and finally you will complete application detail using application detail
page as mentioned in step 9 of the above mentioned checklist.