What is the significance of the `AndroidManifest.xml` file in an Android application?

Official answer

The manifest describes the app to Android and build/distribution tools. Its component declarations include activities, services, receivers and providers, with properties such as permissions, process assignment and whether other apps may access them. Intent filters declare matching capabilities; they do not replace access checks.

The final merged manifest combines app, library and build-variant information. Modern Gradle configuration normally supplies values such as applicationId, minSdk and targetSdk; inspect the merged artifact rather than assuming the source manifest is the whole installed configuration. applicationId and the code namespace have distinct roles.

uses-permission declares requested capabilities, but declaration alone does not grant runtime permissions. Handle denial, revocation and the applicable OS/target rules. Use least privilege. For example, declaring camera permission is different from asking the user for it at an appropriate moment.

uses-feature declares hardware/software requirements; a required camera can affect distribution filtering. Mark it optional when the app can function without it and provide a fallback. Intent-filtered components also need deliberate export settings under current target requirements; private internal activities should not be exposed unnecessarily.

Before release, review the merged manifest for unexpected library permissions, exported entry points and incompatible requirements. Test permission denial and a device lacking an optional feature.

Manifest overview