Code obfuscation and optimization in Flutter - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable code obfuscation in Flutter build command.

Flutter

flutter build apk --[1]

Drag options to blanks, or click blank then click option'

Arelease

Bdebug

Cprofile

Dobfuscate

Attempts:

3 left

💡 Hint

Common Mistakes

Using --debug instead of --obfuscate

Forgetting to add --obfuscate flag

Use --obfuscate to enable code obfuscation during Flutter build.

2fill in blank

medium

Complete the code to specify the directory for storing debug symbols during obfuscation.

Flutter

flutter build apk --obfuscate --split-debug-info=[1]

Drag options to blanks, or click blank then click option'

Abuild/debug-info

Blib/src

Candroid/app

Dassets/images

Attempts:

3 left

💡 Hint

Common Mistakes

Using source code folders like lib/src

Using unrelated folders like assets/images

The --split-debug-info flag requires a directory path to save debug symbols for stack traces.

3fill in blank

hard

Fix the error in the Flutter build command to properly optimize the app for release.

Flutter

flutter build apk --[1] --obfuscate

Drag options to blanks, or click blank then click option'

Adebug

Bprofile

Crelease

Dtest

Attempts:

3 left

💡 Hint

Common Mistakes

Using debug mode with obfuscation

Using profile mode instead of release

The --release flag builds the app optimized for production use.

4fill in blank

hard

Fill both blanks to create a Dart function that returns the optimized square of a number using a concise syntax.

Flutter

int square(int x) => x [1] [2];

Drag options to blanks, or click blank then click option'

A*

B+

C-

D/

Attempts:

3 left

💡 Hint

Common Mistakes

Using addition or subtraction instead of multiplication

Using division operator

Multiplying x by itself returns the square.

5fill in blank

hard

Fill all three blanks to create a Dart map comprehension that filters and squares even numbers from a list.

Flutter

{ [1]: [2] * [2] for (var [3] in numbers if [2] % 2 == 0) }

Drag options to blanks, or click blank then click option'

Anum

Bx

Di

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names inconsistently

Using a variable not declared in the loop

The variable x is used for keys and values, filtering even numbers and squaring them.

Practice

1. What is the main purpose of code obfuscation in Flutter apps?

easy

A. To increase the app's loading speed

B. To hide the app's source code details and make reverse engineering harder

C. To add new features automatically

D. To change the app's user interface colors

Solution

1. Step 1: Understand code obfuscation

   Code obfuscation changes code names and structure to make it hard to read or reverse engineer.

2. Step 2: Identify the main goal

   The goal is to protect the app's source code from being easily understood or copied.

3. Final Answer:

   To hide the app's source code details and make reverse engineering harder -> Option B

4. Quick Check:

   Obfuscation = Hide code details [OK]

Hint: Obfuscation means hiding code to protect it [OK]

Common Mistakes:

• Confusing obfuscation with performance optimization
• Thinking obfuscation changes app features
• Believing obfuscation changes UI appearance

2. Which Flutter build command correctly applies code obfuscation and splits debug info?

easy

A. flutter build apk --obfuscate --split-debug-info=path/to/folder

B. flutter run --obfuscate --split-debug-info=path/to/folder

C. flutter build apk --optimize --debug-info=path/to/folder

D. flutter build apk --obfuscate --debug-info=path/to/folder

Solution

1. Step 1: Recall Flutter build flags

   The correct flags for obfuscation and debug info splitting are --obfuscate and --split-debug-info.

2. Step 2: Identify the correct command usage

   flutter build apk is used to build the app, and the flags must be exactly as documented.

3. Final Answer:

   flutter build apk --obfuscate --split-debug-info=path/to/folder -> Option A

4. Quick Check:

   Use --obfuscate and --split-debug-info with flutter build [OK]

Hint: Use flutter build with --obfuscate and --split-debug-info [OK]

Common Mistakes:

• Using flutter run instead of flutter build
• Using incorrect flag names like --debug-info
• Omitting the path after --split-debug-info

3. What will happen if you build a Flutter app with flutter build apk --obfuscate --split-debug-info=./debug-info and then run it?

medium

A. The app runs normally but the code is harder to reverse engineer

B. The app crashes immediately due to missing debug info

C. The app runs slower because of obfuscation

D. The app shows debug info on screen

Solution

1. Step 1: Understand build flags effect

   --obfuscate hides code details; --split-debug-info saves debug info externally but does not affect runtime.

2. Step 2: Predict app behavior

   The app runs normally with obfuscated code; debug info is stored separately for debugging if needed.

3. Final Answer:

   The app runs normally but the code is harder to reverse engineer -> Option A

4. Quick Check:

   Obfuscate hides code; app still runs [OK]

Hint: Obfuscation hides code but app runs normally [OK]

Common Mistakes:

• Thinking obfuscation causes crashes
• Assuming debug info must be bundled inside app
• Believing obfuscation slows app significantly

4. You tried to build your Flutter app with flutter build apk --obfuscate --split-debug-info but got an error. What is the likely cause?

medium

A. You ran the command without flutter build

B. You used --obfuscate without --split-debug-info

C. You did not provide a path after --split-debug-info

D. You forgot to add --release flag

Solution

1. Step 1: Check command syntax

   The --split-debug-info flag requires a folder path to save debug symbols.

2. Step 2: Identify missing argument

   Omitting the path causes a build error because Flutter doesn't know where to save debug info.

3. Final Answer:

   You did not provide a path after --split-debug-info -> Option C

4. Quick Check:

   --split-debug-info needs a path [OK]

Hint: Always add a folder path after --split-debug-info [OK]

Common Mistakes:

• Using --split-debug-info without path
• Confusing --obfuscate usage
• Forgetting flutter build prefix

5. You want to reduce your Flutter app size and protect your code. Which combination of steps is best?

hard

A. Use flutter build apk --debug with no flags

B. Use flutter run --obfuscate and disable tree shaking

C. Use flutter build apk --split-debug-info without obfuscation

D. Use flutter build apk --obfuscate --split-debug-info=./debug-info and enable tree shaking

Solution

1. Step 1: Combine obfuscation and optimization

   Obfuscation hides code; tree shaking removes unused code to reduce size.

2. Step 2: Use correct build command

   flutter build apk with --obfuscate and --split-debug-info enables both protections and debugging support.

3. Final Answer:

   Use flutter build apk --obfuscate --split-debug-info=./debug-info and enable tree shaking -> Option D

4. Quick Check:

   Obfuscate + tree shaking = smaller, protected app [OK]

Hint: Combine obfuscation with tree shaking for best results [OK]

Common Mistakes:

• Using flutter run instead of build for release
• Not enabling tree shaking
• Omitting debug info path