Purpose and Key Elements of AndroidManifest.xml

What's really being asked

This question tests your understanding of the fundamental contract between your application and the Android operating system. The interviewer wants to see if you know that the manifest is not just a configuration file, but a required declaration of your app's identity, components, and requirements that the OS parses before running any of your code. It's a check on foundational knowledge of app structure and security.

The full answer

A strong answer describes the manifest as the app's 'passport' to the Android system and then outlines four key areas. First, the root <manifest> element, which declares the app's unique package name used by the OS and Google Play. Second, the <application> element, which contains app-level properties like the icon, label, and theme. Third, the component declarations: <activity>, <service>, <receiver>, and <provider>. You must mention that at least one activity needs an intent filter for the MAIN action and LAUNCHER category to serve as the app's entry point. Fourth, system requirements and permissions, such as <uses-permission> to request access to protected APIs (like INTERNET or CAMERA) and <uses-feature> to declare necessary hardware, which Google Play uses for filtering.

The mistakes people make

A weak answer is vague, describing it as just 'a config file' without explaining its role as a contract with the OS. A major red flag is forgetting to state that all app components (activities, services, etc.) must be declared in the manifest; the OS will not recognize and cannot start undeclared components, leading to a runtime crash. Another mistake is confusing <uses-permission> (requesting a permission for your app) with <permission> (defining a new, custom permission for other apps to request).

What usually comes next

Expect questions that dive deeper into specific manifest elements. For example: 'What is the android:exported attribute and why is it a critical security setting?', 'Describe the three parts of an <intent-filter> (action, category, data).', or 'How has permission handling changed since runtime permissions were introduced in Android 6.0, and how does that affect the manifest?'.

A concrete example

A minimal manifest has a root <manifest> tag with a package="com.example.myapp" attribute. Inside, an <application> tag holds the app's icon and label. Within the application, an <activity> tag for MainActivity contains an <intent-filter> with an action of android.intent.action.MAIN and a category of android.intent.category.LAUNCHER, making it the app's entry point. Finally, a <uses-permission> tag with android:name="android.permission.INTERNET" requests network access.