How do resources work in Android?

Question

Accepted Answer

Android **resources** are the non-code assets of an app — layouts, strings, images, colors, dimensions — kept **separate from code** in the `res/` directory. This separation supports maintainability, localization, and adapting to different devices and configurations.

## What resources are

```text
Resources = app assets kept separate from code in res/:
  res/layout/    → XML layout files (UI definitions)
  res/values/    → strings.xml, colors.xml, dimens.xml, styles.xml
  res/drawable/  → images, vector graphics, shapes
  res/mipmap/    → app launcher icons
  res/font/      → fonts
→ referenced in code as R.string.app_name, R.layout.activity_main, R.drawable.logo, etc.
```

## Why separate resources from code

```text
✓ MAINTAINABILITY — change strings/colors/dimensions in one place (not scattered in code)
✓ LOCALIZATION — provide translated strings per language (no code changes)
✓ CONFIGURATION adaptation — different resources for different devices/settings (below)
✓ Consistency — reuse colors, dimensions, styles across the app
```

## Configuration qualifiers (adapt to devices/settings)

```text
Resources can be provided for different CONFIGURATIONS via folder qualifiers:
  values/strings.xml         → default strings
  values-es/strings.xml      → SPANISH strings (auto-used in Spanish locale)
  values-night/colors.xml    → DARK MODE colors
  drawable-hdpi/ -xhdpi/ ...  → images for different screen DENSITIES
  layout-land/               → landscape layouts; layout-sw600dp/ → tablets
→ Android automatically picks the right resource for the device/settings → adapt without
  code changes (localization, dark mode, screen sizes, orientation).
```

## Why it matters

Understanding how resources work is foundational to Android development because **separating resources from code is fundamental to how Android apps are built**, supporting maintainability, localization, and device adaptation, so it's important practical knowledge.

Android keeps non-code assets (layouts, strings, images, colors, dimensions) as **resources in the `res/` directory, separate from code** — and understanding this organization (and referencing resources via `R`) is necessary for any Android development.

Understanding **why resources are separated** is valuable: it improves **maintainability** (changing strings, colors, or dimensions in one place rather than scattered in code), enables **localization** (providing translated strings per language without code changes), supports **configuration adaptation**, and ensures consistency (reusing colors and styles).

Most powerfully, understanding **configuration qualifiers** is important: Android lets you provide different resources for different configurations via folder qualifiers — translated strings per language (`values-es/`), dark-mode colors (`values-night/`), images for different screen densities (`drawable-hdpi/` etc.), and layouts for orientation and screen size (`layout-land/`, `layout-sw600dp/`) — and **Android automatically selects the right resource** for the device and settings, enabling apps to **adapt to localization, dark mode, screen sizes, and orientation without code changes**.

This resource-qualifier system is a powerful, distinctive Android feature for building adaptable, localized apps.

Since separating resources from code is fundamental to Android app structure (supporting maintainability, localization, and especially automatic device/configuration adaptation), and since understanding resources and configuration qualifiers is necessary for building maintainable, adaptable, localized apps, understanding how resources work in Android is essential, foundational knowledge — a core aspect of Android development that enables maintainable, localizable, device-adaptable apps, and necessary practical knowledge for any Android developer.