Android开发：为何R.drawable.image_name为整数类型？

Great question—this confused me a lot when I was first building ListView (and other) components too! Let’s break down why Android uses integer IDs instead of something more "direct" like a file path to reference drawables:

• Resource Adaptability & Optimization
  Android’s resource system is built to handle device-specific adaptations automatically (like different screen densities, languages, or orientations). When you use R.drawable.image_name, that integer is actually a unique key that maps to the correct version of the resource for the current device. For example, on an xhdpi device, the ID might point to the image in res/drawable-xhdpi/, while on an mdpi device it points to res/drawable-mdpi/. The system handles this mapping behind the scenes, so you don’t have to write conditional code for each case. Plus, the Android Asset Packaging Tool (aapt) compiles all resources into binary format during build, and integer IDs are much faster to look up than string paths.

• Compile-Time Safety
  Using integer IDs lets the compiler catch mistakes early. If you mistype R.drawable.wronge_image_name, your IDE will throw an error immediately before you even run the app. If we used string references instead (like "drawable/image_name"), you’d only find out there’s a problem when the app crashes at runtime with a ResourceNotFoundException. This saves tons of debugging time!

• Consistency & Simplicity
  This integer ID system isn’t just for drawables—every resource type (layouts, strings, colors, styles) uses the same pattern with R.xxx.yyy. This consistency makes it easier to learn and use Android’s resource system, since you don’t have to switch between different reference formats for different resource types.

• APK Size Efficiency
  Integer IDs take up less space than full string paths. When you have hundreds or thousands of resource references in an app, this adds up to a smaller overall APK size. Also, the aapt tool can deduplicate identical resources and assign them the same ID, further reducing redundancy.

For example, when you’re setting an image in your ListView adapter, calling imageView.setImageResource(R.drawable.list_item_icon) is fast, safe, and ensures the right image loads for the user’s device.

内容的提问来源于stack exchange，提问作者CLay