Beyond the Sweet Treat: Why Android API 23 (Marshmallow) Remains a Milestone in Mobile Development

When Google released Android 6.0 Marshmallow alongside API Level 23 back in late 2015, developers viewed it as yet another platform update in a rapidly moving ecosystem. Beneath the surface-level polish of the “Marshmallow” moniker, however, API 23 introduced structural paradigm shifts that fundamentally changed how applications interact with user data, hardware, and the underlying operating system.

Years after its initial rollout, API 23 occupies a fascinating place in the mobile engineering landscape: it has transitioned from a bleeding-edge standard into a foundational baseline for modern Android development.

1. The Revolution of Runtime Permissions

Before API 23, Android utilized an “all-or-nothing” installation-time permission model. When users downloaded an app from the Google Play Store, a comprehensive list of requested permissions—ranging from accessing the camera to reading contacts—was displayed. If a user didn’t want to grant even one of those permissions, their only option was to cancel the installation entirely.

API 23 shattered this friction-heavy model by introducing Runtime Permissions.

• Granular Control: Dangerous permissions (such as location, camera, microphone, and storage access) were decoupled from installation. Instead, apps had to request these permissions dynamically at the exact moment a feature required them.
• User Empowerment: Users could finally grant or deny individual permissions on the fly and toggle them later in system settings.
• Architectural Shifts: For developers, this meant writing defensive, adaptive UI flows. Codebases could no longer assume that a declared manifest permission guaranteed persistent access; they had to explicitly handle rejections, explain why a feature needed access, and gracefully fall back when denied.

2. Power Management and Doze Mode

Mobile batteries have always faced high demands, and API 23 addressed device longevity head-on with the introduction of Doze Mode and App Standby.

• Doze Mode: When a device was left unattended, screen-off, and stationary, the system entered Doze, periodically waking up via brief maintenance windows to process syncs and background tasks while heavily throttling CPU-intensive or network-heavy operations.
• App Standby: This feature categorized apps that hadn’t been actively used for a while, restricting their network access and background jobs to preserve battery life.

For engineers, API 23 marked the beginning of a strict enforcement era against background processing abuse, paving the way for future optimizations like WorkManager and strict foreground service policies.

3. Other Under-the-Hood Game Changers

While permissions and power management stole the spotlight, API 23 brought several other critical updates to the Android ecosystem:

• Native Fingerprint Authentication: Marshmallow provided standardized APIs (FingerprintManager) to integrate biometric login securely into apps, laying the groundwork for the modern biometric authentication frameworks we use today.
• Direct Share: Apps could target specific shortcuts and contacts within other applications, making sharing content faster and more contextual.
• Text Selection Actions: The floating text-selection toolbar allowed custom contextual actions (like translate, search, or share) to pop up right next to highlighted text inside any text view.

4. The Legacy: From Cutting-Edge to Baseline

In the fast-paced world of mobile tech, a platform version from 2015 could easily have been forgotten. Yet, API 23 enjoys a unique status as a baseline threshold. In recent years, core modern frameworks—including major updates to Android Jetpack/AndroidX libraries and Google Play Services—migrated their minimum SDK requirements (minSdk) to API 23 or higher.

By shifting the floor to API 23, Google allowed the developer community to finally deprecate legacy workarounds for runtime permissions, lean heavily into modern Java/Kotlin features, and drop support for obsolete legacy structures (such as the removal of the Apache HTTP client).

Final Thoughts

Android API 23 (Marshmallow) is a testament to how architectural foresight can future-proof an operating system. What began as a major security and UX overhaul in 2015 has matured into the structural floor upon which modern, secure, and power-efficient Android experiences are built. For developers, understanding API 23 isn’t just about backward compatibility—it’s about appreciating the exact moment Android grew up.