Complete Guide to Creating Drawable from Resources in Android

Fundamentals of Drawable Resource Conversion

In Android application development, Drawable represents a crucial type of graphical resource used for rendering visual elements on screen. Developers frequently need to convert image resources stored in the res/drawable directory into Drawable objects for use across various UI components.

Traditional Method and Its Limitations

In early Android development, the most common approach involved obtaining the Resources object through the Activity's getResources() method, followed by invoking its getDrawable() method:

Drawable myIcon = getResources().getDrawable(R.drawable.icon);

While this method was straightforward, it has been marked as deprecated since API level 21 (Android 5.0). Primary reasons include lack of native vector graphic support, inconsistent theme application, and limitations in resource resolution.

Modern Recommended Approaches

AppCompatResources Solution

For modern Android applications requiring backward compatibility, the AppCompatResources class is recommended:

Drawable myIcon = AppCompatResources.getDrawable(context, R.drawable.icon);

This approach offers superior vector graphic support, automatic theme attribute handling, and maintains consistency across all API levels. AppCompatResources is part of both Android Support Library and AndroidX, specifically designed to address compatibility concerns.

ResourcesCompat Solution

When custom theme specification is necessary, the ResourcesCompat class can be utilized:

Drawable myIcon = ResourcesCompat.getDrawable(getResources(), R.drawable.icon, theme);

This method automatically applies the specified theme on API 21 and above, while falling back to default behavior on lower versions. This progressive enhancement strategy ensures stable application performance across different Android versions.

ContextCompat Alternative

Another common alternative involves using the ContextCompat class:

Drawable drawable = ContextCompat.getDrawable(getApplicationContext(), R.drawable.icon);

This approach simplifies context acquisition, particularly useful in non-Activity classes. ContextCompat similarly provides excellent backward compatibility and is preferred in many contemporary Android applications.

Practical Implementation Scenarios

Taking button compound Drawable setup as an example, the complete implementation code is as follows:

// Retrieve Drawable resource
Drawable iconDrawable = AppCompatResources.getDrawable(this, R.drawable.test);

// Set button compound Drawables
mButton.setCompoundDrawablesWithIntrinsicBounds(
    iconDrawable, // left
    null,         // top
    null,         // right
    null          // bottom
);

This method ensures proper image resource display across different Android versions and devices.

Best Practice Recommendations

When selecting specific implementation methods, consider factors such as project minimum API level, AndroidX usage, theme support requirements, and code maintainability. For new projects, strongly recommend using AppCompatResources or ContextCompat methods to avoid future compatibility issues.

Additionally, encapsulating Drawable retrieval logic in application base classes or utility classes is advised to enhance code reusability and maintainability. Proper memory management of resources is also crucial—timely release of unused Drawable objects helps prevent memory leaks.