Explain the res/ directory and resource qualifiers for layouts

What's really being asked

This question tests a fundamental Android architecture principle: the separation of app resources from source code. Interviewers want to confirm you understand why this is crucial for handling device configuration changes (like rotation, language, or screen size) efficiently. It's a test of your knowledge of the specific, automatic conventions the Android build tools rely on, rather than manual, conditional code.

The full answer

First, define the purpose of the res/ directory: it holds all static, non-code assets like layouts, drawables, strings, dimensions, and styles. This decouples presentation from logic. Second, explain that the build system compiles these resources and generates the R class, which provides static integer IDs for code to access them (e.g., R.layout.main_activity). Third, define resource qualifiers as suffixes added to directory names that allow the OS to select the best resource for the current device configuration. Finally, provide the specific example: to support landscape, you create a default layout in res/layout/my_activity.xml and a landscape-specific version in res/layout-land/my_activity.xml. The filenames must be identical.

The mistakes people make

Describing a solution that only uses lifecycle callbacks (like in onCreate) to programmatically check the orientation and then manually reconfigure views. This ignores the primary, intended mechanism. Using incorrect qualifier names is another major red flag, for example res/layout-landscape/ (it's -land), res/layout/landscape/ (it's a suffix, not a subdirectory), or believing the default portrait layout needs a res/layout-port/ directory (the default has no qualifier).

What usually comes next

How does the system decide which resource to use if multiple qualifiers match, like layout-en-land versus layout-land? What other qualifiers have you used in a real project? What happens if a qualified resource is requested but no match is found and there is no default? (The app crashes with a Resources.NotFoundException).

A concrete example

For a screen defined by activity_feed.xml, you would have two files. The default (portrait) layout is located at app/src/main/res/layout/activity_feed.xml. The specific landscape layout is at app/src/main/res/layout-land/activity_feed.xml. In your FeedActivity.kt, you simply call setContentView(R.layout.activity_feed). The Android OS handles selecting and inflating the correct XML file automatically when the device is rotated. No if (orientation == LANDSCAPE) logic is needed for this.