Android SDK and API levels in Android Kotlin - Build, Publish & Deploy

Build & Publish - Android SDK and API levels

Performance Impact

Choosing the right Android SDK and API level affects app performance. Using newer API levels can improve frame rates and battery efficiency by leveraging platform optimizations. However, targeting very old API levels may limit access to performance improvements and modern features, causing slower UI rendering and higher memory use.

Optimization Tips

To keep your app running smoothly at 60fps, target the latest stable API level while maintaining backward compatibility. Use compileSdkVersion and targetSdkVersion set to the newest API to access performance improvements. Use conditional code to avoid deprecated APIs on newer devices. Test on multiple API levels to catch performance issues early.

App Size and Startup Time

Higher API levels allow you to use modern libraries and features that can reduce app size by removing legacy code. However, supporting many old API levels increases code complexity and app size due to compatibility libraries. Minimizing the minimum API level reduces the need for extra compatibility code, improving startup time and reducing APK size.

iOS vs Android Differences

Android uses API levels to manage platform features and compatibility, while iOS uses OS versions. Android apps must specify minimum, target, and compile SDK versions. iOS apps specify minimum and target OS versions. Android API levels affect device compatibility and app behavior more granularly. iOS updates are more uniform, so compatibility issues are less fragmented.

Store Review Guidelines

• Google Play requires apps to target a recent API level (usually within 1 year of the latest release) to ensure security and performance.
• Apps must declare correct minSdkVersion and targetSdkVersion in the manifest or build configuration.
• Using deprecated APIs may cause warnings or rejections during review.
• Ensure your app handles runtime permissions properly for API 23+.

Self-Check Question

Your app takes 5 seconds to load this screen. What's likely wrong?

• You might be targeting a very old API level missing performance improvements.
• Compatibility libraries for old APIs could be slowing startup.
• Heavy initialization code not optimized for newer APIs.
• Not using asynchronous loading or modern lifecycle-aware components.

Key Result

Targeting the latest Android SDK and API levels improves app performance, reduces size, and ensures compliance with Google Play requirements, while careful backward compatibility maintains smooth user experience across devices.

Practice

1. What does the minSdk version specify in an Android app?

easy

A. The latest Android version available

B. The Android version you compile your app against

C. The Android version your app is optimized for

D. The oldest Android version your app can run on

Solution

1. Step 1: Understand minSdk meaning

   minSdk defines the minimum Android version that can run the app.

2. Step 2: Differentiate from other SDK versions

   compileSdk is for building, targetSdk is optimization, but minSdk is the oldest supported version.

3. Final Answer:

   The oldest Android version your app can run on -> Option D

4. Quick Check:

   minSdk = oldest supported version [OK]

Hint: minSdk means minimum Android version supported [OK]

Common Mistakes:

• Confusing minSdk with compileSdk
• Thinking minSdk is the target optimization version
• Assuming minSdk is the latest Android version

2. Which of the following is the correct way to set the compileSdk version to 33 in a Kotlin DSL Gradle file?

easy

A. compileSdkVersion 33

B. compileSdkVersion = 33

C. compileSdk = 33

D. compileSdk(33)

Solution

1. Step 1: Identify Kotlin DSL syntax for compileSdk

   In Kotlin DSL, compileSdk is assigned directly with =.

2. Step 2: Compare options

   compileSdkVersion 33 is Groovy syntax without assignment, compileSdkVersion = 33 uses the wrong property name, and compileSdk(33) is invalid function call syntax. Only compileSdk = 33 is correct.

3. Final Answer:

   compileSdk = 33 -> Option C

4. Quick Check:

   Kotlin DSL uses compileSdk = 33 [OK]

Hint: Kotlin DSL uses equals sign for assignments [OK]

Common Mistakes:

• Using Groovy syntax in Kotlin DSL
• Omitting equals sign
• Using method call syntax incorrectly

3. Given this Gradle configuration snippet:

android {
  compileSdk = 31
  minSdk = 21
  targetSdk = 30
}

What is the highest Android version your app is optimized for?

medium

A. 30

B. 21

C. 31

D. Cannot determine from this

Solution

1. Step 1: Identify meaning of targetSdk

   targetSdk is the Android version the app is optimized for and tested against.

2. Step 2: Check given values

   Here, targetSdk is 30, so the app is optimized for Android 30.

3. Final Answer:

   30 -> Option A

4. Quick Check:

   targetSdk = 30 means optimized for Android 30 [OK]

Hint: targetSdk shows optimization version, not compileSdk [OK]

Common Mistakes:

• Confusing compileSdk with targetSdk
• Thinking minSdk is optimization version
• Choosing compileSdk as optimization version

4. You set minSdk = 30 but want your app to run on Android 21 devices. What is the problem in this Gradle config?

android {
  compileSdk = 33
  minSdk = 30
  targetSdk = 33
}

medium

A. compileSdk must be lower than minSdk

B. minSdk is too high, app won't run on Android 21

C. targetSdk must be equal to minSdk

D. No problem, app runs on all versions

Solution

1. Step 1: Understand minSdk role

   minSdk sets the lowest Android version the app supports.

2. Step 2: Check compatibility with Android 21

   Since minSdk is 30, devices with Android 21 cannot run the app.

3. Final Answer:

   minSdk is too high, app won't run on Android 21 -> Option B

4. Quick Check:

   minSdk = 30 excludes Android 21 devices [OK]

Hint: minSdk must be ≤ lowest Android version supported [OK]

Common Mistakes:

• Thinking compileSdk affects device compatibility
• Assuming targetSdk limits device support
• Believing app runs on all versions regardless of minSdk

5. You want to use a new Android feature introduced in API level 31 but still support devices running API level 21. How should you configure your Gradle file to safely use this feature?

hard

A. Set minSdk = 21, targetSdk = 31, and use runtime checks for API 31 features

B. Set minSdk = 21 and targetSdk = 21

C. Set minSdk = 31 and targetSdk = 31

D. Set compileSdk = 21 and minSdk = 31

Solution

1. Step 1: Understand minSdk and targetSdk roles

   minSdk is the oldest supported version; targetSdk is the optimized version.

2. Step 2: Use runtime checks for new features

   To support API 21 devices but use API 31 features, keep minSdk = 21, set targetSdk = 31, and check API level at runtime before using new features.

3. Step 3: Evaluate options

   Set minSdk = 21, targetSdk = 31, and use runtime checks for API 31 features correctly sets minSdk and targetSdk and mentions runtime checks. Others either restrict support or use wrong compileSdk.

4. Final Answer:

   Set minSdk = 21, targetSdk = 31, and use runtime checks for API 31 features -> Option A

5. Quick Check:

   minSdk low + targetSdk high + runtime checks = safe feature use [OK]

Hint: Use runtime API checks to support older devices safely [OK]

Common Mistakes:

• Raising minSdk and losing older device support
• Not using runtime checks for new APIs
• Setting compileSdk lower than targetSdk