Eclipse IDE for Android App Development
Eclipse IDE for Android App Development
Note 1: SDK Path is also present in Android Studio -> Tools -> SDK Manager -> Copy the Android
SDK Location path and paste it here.
Note 2: If in case after Step 6, if you are facing this issue “Could not find folder ‘tools’ inside SDK”
please refer to this article How to fix Could not find folder ‘tools’ inside SDK in Android?
Step 7: Click on Install new SDK then Next. Another dialog box will appear, Accept all three
packages and Click on Install.
After installation of packages, SDK Manager will appear for API Level Build Tools and System
Images installation. Click on Install.
Step 8: After installation is completed, Go to Eclipse then Select Window then Click on Android
Virtual Device Manager. A dialog box will appear, Select existing AVD and Click on Edit.
Fill in all the details as per the below image. Click OK.
Step 9: To create an android application, Select File -> New -> Other, and then the below dialog box
will appear Select Android -> Android Application Project then Click on Next. Follow the steps and
then click on Finish.
Step 10: Eclipse IDE setup is completed for Android Application Development.
Components of an Android Application
There are some necessary building blocks that an Android application consists of. These loosely coupled
components are bound by the application manifest file which contains the description of each component
and how they interact. The manifest file also contains the app’s metadata, its hardware configuration,
and platform requirements, external libraries, and required permissions. There are the following main
components of an android app:
1. Activities
Activities are said to be the presentation layer of our applications. The UI of our application is built
around one or more extensions of the Activity class. By using Fragments and Views, activities set the
layout and display the output and also respond to the user’s actions. An activity is implemented as a
subclass of class Activity.
2. Services
Services are like invisible workers of our app. These components run at the backend, updating your data
sources and Activities, triggering Notification, and also broadcast Intents. They also perform some tasks
when applications are not active. A service can be used as a subclass of class Service:
3. Content Providers
It is used to manage and persist the application data also typically interacts with the SQL database. They
are also responsible for sharing the data beyond the application boundaries. The Content Providers of a
particular application can be configured to allow access from other applications, and the Content
Providers exposed by other applications can also be configured.
A content provider should be a sub-class of the class ContentProvider.
4. Broadcast Receivers
They are known to be intent listeners as they enable your application to listen to the Intents that satisfy
the matching criteria specified by us. Broadcast Receivers make our application react to any received
Intent thereby making them perfect for creating event-driven applications.
5. Intents
6. Widgets
These are the small visual application components that you can find on the home screen of the devices.
They are a special variation of Broadcast Receivers that allow us to create dynamic, interactive
application components for users to embed on their Home Screen.
7. Notifications
Notifications are the application alerts that are used to draw the user’s attention to some particular app
event without stealing focus or interrupting the current activity of the user. They are generally used to
grab user’s attention when the application is not visible or active, particularly from within a Service or
Broadcast Receiver. Examples: E-mail popups, Messenger popups, etc.