Dynamic

Android API Level 21 vs Android API Level 22

Developers should learn and use Android API Level 21 when building apps that require modern Android features such as Material Design components, improved notification systems, or support for devices from 2014 onward meets developers should learn and use android api level 22 when building apps that need to support older devices running android 5. Here's our take.

🧊Nice Pick

Android API Level 21

Developers should learn and use Android API Level 21 when building apps that require modern Android features such as Material Design components, improved notification systems, or support for devices from 2014 onward

Android API Level 21

Nice Pick

Developers should learn and use Android API Level 21 when building apps that require modern Android features such as Material Design components, improved notification systems, or support for devices from 2014 onward

Pros

  • +It is essential for apps targeting a broad user base on Android 5
  • +Related to: android-sdk, material-design

Cons

  • -Specific tradeoffs depend on your use case

Android API Level 22

Developers should learn and use Android API Level 22 when building apps that need to support older devices running Android 5

Pros

  • +1 Lollipop, as it represents a significant user base in legacy markets
  • +Related to: android-sdk, android-studio

Cons

  • -Specific tradeoffs depend on your use case

The Verdict

Use Android API Level 21 if: You want it is essential for apps targeting a broad user base on android 5 and can live with specific tradeoffs depend on your use case.

Use Android API Level 22 if: You prioritize 1 lollipop, as it represents a significant user base in legacy markets over what Android API Level 21 offers.

🧊
The Bottom Line
Android API Level 21 wins

Developers should learn and use Android API Level 21 when building apps that require modern Android features such as Material Design components, improved notification systems, or support for devices from 2014 onward

Disagree with our pick? nice@nicepick.dev