A fintech startup sets minSdkVersion=29 (Android 10) in their banking app. They receive complaints that the app is unavailable on Android 8 devices. The development lead argues this was done intentionally for security reasons.
A Google Play app fails to be visible to users running Android 8 (API 26) devices. The developer investigates and finds their minSdkVersion is set to 29. What security implication did setting minSdkVersion=29 have, and was it a good decision for a banking app?
- A.Google Play mandates minSdkVersion 29 for a financial category listing, and the developer had no discretion because the console rejects a lower value at upload for apps declaring the finance tag (the policy landed with the 2022 developer program update); the Android 8 complaints are the expected consequence, and every banking app on the store shares the same floor: the decision was made for the team.
- B.The floor should come down to 21 because market reach is the dominant consideration for a fintech startup, and a banking app can carry runtime checks for the newer APIs (a compatibility library backports BiometricPrompt to Android 5 without loss of function); the security posture is unchanged by the declaration, and every control the team relies on has a fallback path: the correct move is a lower floor, always paired with feature detection.