Lesson Plan: Unit - 02
Subject: P15A2AAD - Android Application Development
Topic of Study: Android Manifest File and it's different configuration tags
Grade/Level: Master of Computer Applications
Objective: To understand configuration of Android Manifest file with its values and examples
Time Allotment: 55 Minutes
- Managing Application Identity
- Android manifest file defines the apps properties.
- The package name must be defined within the Android manifest file within the manifest
tag using the package attribute. - Exa.
- Versioning of Application
- It is vital to maintaining your application.
- It’s make product support and upgrades simpler.
- Two different version attributes defined within the
tag: - The version name.
- The version code.
- Let’s see…
- The version name - is a user-friendly, developer defined version attribute.
- The version code - is a numeric attribute to manage application upgrades.
- Exa.
- Settings the Application name and icon
- Overall application settings are configured with the
tag. - Such as…
- The application icon (android:icon)
- The application name (android:label)
- Exa.
- Enforcing Application System Requirement
- It is also used to specify any system requirements necessary for the application to run properly.
- Exa. an augmented reality application…requires
- GPS, a compass and camera.
- Android manifest file include..
- The Android SDK versions
- The Android platform features
- The Android hardware configurations
- The screen sizes and pixel densities
- Any external libraries
- Android SDK versions…
- Android devices run different versions of the Android platform
- Developers can specify which versions of the Android application supports using the
tag - This tag has 3 important attributes…
- The minSdkVersion attribute: specifies the lowest API level
- The targetSdkVersion attribute: specifies the optimum API level
- The maxSdkVersion attribute: specifies the highest API level
- Specifying Supported Input Methods…
- The
tag can be used to specify which input methods. - Exa. if your application requires a physical keyboard and touch screen input using a finger or a stylus
- Specifying Required Device Features…
- The
tag can be used to specify which Android features. - Exa. an application that requires both a light and proximity sensor requires two tags.
- Specifying Supported Screen Sizes…
- The
tag can be used to specify which Android types of screen - Exa. if the application supports QVGA screens (small) and HVGA screens (normal).
- Registering Activities and other application components
- All application components are defined within the Android manifest file.
- Activities are registered using the activity tag.
- Services are registered using the service tag.
- Broadcast Receivers are registered using the receiver tag.
- Content provider are registered using the provider tag.
- Each Activity within the application must be defined within the Android manifest file with an
tag. - Exa.
- If not defined then it will not launch.
- Exa.
- We can use the relative or absolute path to define the activity name.
- Design a Primary Entry point Activity using Intent Filter
- The Android OS uses Intent filters to resolve implicit intents.
- Intent filters can be applied to Activities, Services, and Broadcast Receivers.
- Intent filters are defined using the
tag. - It has 3 blocks…
- So, configuring an intent filter using the Android manifest tag
in the application’s AndroidManifest.xml file with the MAIN action type and the LAUNCHER category. - Exa.
