ProGuard and R8 optimization in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of ProGuard in Android development?

Choose the main reason developers use ProGuard when building Android apps.

A To generate app screenshots for the Play Store listing

B To add new UI components automatically during build

C To increase the app's runtime speed by changing the CPU architecture

D To shrink and obfuscate the app code to reduce APK size and protect code

💡 Hint

Think about what happens to your app code before publishing it.

ProGuard shrinks the app by removing unused code and obfuscates it to make reverse engineering harder, reducing APK size and improving security.

❓ ui_behavior

intermediate

What happens to your app UI if R8 removes a class used only in layout XML?

If R8 optimization removes a class that is only referenced in your layout XML files but not directly in Kotlin code, what is the likely result when you run the app?

A The app UI shows a blank screen but no crash

B The app crashes at runtime with a ClassNotFoundException

C The app runs normally without any UI changes

D The app shows a compile-time error and does not build

💡 Hint

Consider how R8 detects code usage and what happens if a needed class is missing at runtime.

R8 removes unused classes based on code references. If a class is only referenced in XML and not kept, it will be removed, causing a runtime crash when the UI tries to inflate it.

❓ lifecycle

advanced

How does enabling R8 affect app build lifecycle and debugging?

When you enable R8 in your Android project, which of the following is true about the build lifecycle and debugging experience?

A Build time increases slightly and debugging obfuscated code requires mapping files

B Build time decreases and debugging is easier because code is simplified

C Build time is unaffected and debugging works normally without changes

D Build time increases drastically and debugging is impossible

💡 Hint

Think about what happens when code is obfuscated and how developers debug crashes.

R8 adds optimization steps increasing build time slightly. Obfuscated code changes names, so debugging requires mapping files to translate stack traces back to original code.

❓ navigation

advanced

Which ProGuard rule prevents removal of classes used in Android Navigation XML?

You use Android Navigation component with fragments declared only in navigation XML. Which ProGuard rule keeps these fragment classes from being removed by R8?

A -keep class * extends android.app.Activity { <init>(); }

B -keep class ** { *; }

C -keep class * extends androidx.fragment.app.Fragment { <init>(); }

D -keep class * implements android.os.Parcelable { <init>(); }

💡 Hint

Fragments used only in XML need to be kept by their class inheritance.

Fragments used in navigation XML are instantiated by class name at runtime. The rule keeping all classes extending Fragment with a constructor prevents R8 from removing them.

📝 Syntax

expert

What is the output of this ProGuard keep rule effect on R8 optimization?

Given this ProGuard rule: -keepclassmembers class com.example.MyClass { public void myMethod(); } What effect does this have on R8 optimization?

Android Kotlin

-keepclassmembers class com.example.MyClass { public void myMethod(); }

A Keeps only the method 'myMethod' in MyClass from being removed or renamed

B Keeps the entire MyClass and all its members from removal or renaming

C Removes 'myMethod' but keeps the rest of MyClass intact

D Has no effect; R8 ignores this rule

💡 Hint

Focus on what 'keepclassmembers' means compared to 'keep'.

'-keepclassmembers' keeps only the specified members (methods/fields) from removal or renaming but allows the class itself to be removed if unused.

Practice

1. What is the main purpose of enabling minifyEnabled true in your Android app's release build?

easy

A. To automatically generate UI layouts

B. To increase the app's debug information for easier troubleshooting

C. To disable ProGuard and R8 optimizations

D. To shrink and optimize the app code by removing unused parts

Solution

1. Step 1: Understand the role of minifyEnabled

   Setting minifyEnabled true activates code shrinking and optimization tools like ProGuard and R8.

2. Step 2: Identify the effect on app code

   These tools remove unused code and optimize the remaining code to reduce app size and improve performance.

3. Final Answer:

   To shrink and optimize the app code by removing unused parts -> Option D

4. Quick Check:

   minifyEnabled true = shrink and optimize [OK]

Hint: minifyEnabled true means code shrinking is ON [OK]

Common Mistakes:

• Thinking it increases debug info instead of reducing code
• Confusing minifyEnabled with disabling optimizations
• Assuming it generates UI layouts automatically

2. Which of the following is the correct way to specify a ProGuard rules file in your build.gradle for release builds?

easy

A. proguardFiles 'proguard-rules.txt'

B. proguardFiles 'proguard-android-optimize.txt', getDefaultProguardFile('proguard-rules.pro')

C. proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'

D. minifyEnabled false

Solution

1. Step 1: Recall the standard syntax for ProGuard files

   The correct syntax uses getDefaultProguardFile for the default file and then adds custom rules.

2. Step 2: Match the correct order and file names

   proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro' correctly calls getDefaultProguardFile('proguard-android-optimize.txt') and then adds 'proguard-rules.pro'.

3. Final Answer:

   proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro' -> Option C

4. Quick Check:

   Correct ProGuard file syntax = proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro' [OK]

Hint: Default file uses getDefaultProguardFile() [OK]

Common Mistakes:

• Swapping file names or forgetting getDefaultProguardFile()
• Setting minifyEnabled false disables ProGuard
• Using wrong file extensions like .txt instead of .pro

3. Given this ProGuard rule:

-keep class com.example.MyClass { *; }

What will happen to MyClass during code shrinking?

medium

A. It will be kept intact with all its members

B. It will be removed if unused

C. Only its public methods will be kept

D. It will be renamed but removed if unused

Solution

1. Step 1: Understand the -keep rule

   The -keep directive tells ProGuard to keep the specified class and its members without removing or renaming them.

2. Step 2: Analyze the rule syntax

   The rule -keep class com.example.MyClass { *; } means keep the entire class and all its members intact.

3. Final Answer:

   It will be kept intact with all its members -> Option A

4. Quick Check:

   -keep class = keep all members [OK]

Hint: -keep means keep class and members intact [OK]

Common Mistakes:

• Thinking -keep removes unused classes
• Assuming only public methods are kept
• Confusing renaming with removal

4. You enabled minifyEnabled true but your app crashes at runtime due to missing classes. What is the most likely cause?

medium

A. You set minifyEnabled false by mistake

B. You forgot to add -keep rules for classes used via reflection

C. You used the wrong ProGuard file name in build.gradle

D. You disabled R8 in your project

Solution

1. Step 1: Identify the cause of missing classes

   When code shrinking removes classes used only by reflection, runtime crashes occur.

2. Step 2: Understand the role of -keep rules

   Adding -keep rules for such classes prevents their removal during shrinking.

3. Final Answer:

   You forgot to add -keep rules for classes used via reflection -> Option B

4. Quick Check:

   Missing classes after shrinking = missing -keep rules [OK]

Hint: Add -keep rules for reflection-used classes [OK]

Common Mistakes:

• Assuming minifyEnabled false causes missing classes
• Confusing file name errors with missing classes
• Thinking disabling R8 causes missing classes

5. You want to keep all classes in the package com.example.models but allow R8 to rename their members to reduce size. Which ProGuard rule should you use?

hard

A. -keepnames class com.example.models.**

B. -keepclassmembers class com.example.models.** { *; }

C. -keep class com.example.models.** { *; }

D. -keepclassmembernames class com.example.models.** { *; }

Solution

1. Step 1: Understand the difference between -keep and -keepnames

   -keep prevents removal and renaming; -keepnames prevents renaming but allows removal.

2. Step 2: Match the requirement

   You want to keep classes but allow member renaming, so -keepnames on classes is correct.

3. Final Answer:

   -keepnames class com.example.models.** -> Option A

4. Quick Check:

   Keep classes but rename members = -keepnames [OK]

Hint: -keepnames keeps class names but allows member renaming [OK]

Common Mistakes:

• Using -keep which prevents renaming
• Confusing -keepclassmembers with -keepnames
• Assuming -keepclassmembernames keeps classes