Android 6.0 Marshmallow API 23 Features and Guide

Understanding API 23: The Milestone That Redefined Android Security and Architecture

When discussing milestones that fundamentally reshaped mobile operating systems, API Level 23—corresponding to Android 6.0 Marshmallow—stands out as one of the most critical turning points in smartphone history. Released by Google, this update did more than just introduce routine software tweaks; it restructured how apps interact with users, hardware, and operating system resources.

Whether you are a developer looking back at legacy codebase requirements or a tech enthusiast curious about how modern mobile privacy evolved, API 23 remains a fascinating study in balancing user control with software functionality.

The Paradigm Shift: Introduction of Runtime Permissions

Before API 23, Android utilized an “all-or-nothing” installation-time permissions model. When users downloaded an application from an app store, they were presented with a massive, monolithic list of requested permissions—ranging from accessing the camera and reading contacts to tracking precise location. If a user felt uncomfortable with even a single item on that list, their only option was to cancel the installation entirely.

API 23 changed this dynamics completely by introducing Runtime Permissions (or “Just-in-Time” requests):

• Dynamic Prompting: Instead of demanding every clearance upfront, apps targeting API 23 or higher must request dangerous permissions (such as microphone or storage access) dynamically, only when the user actually triggers the specific feature requiring it.
• Granular Control: Users gained the power to grant or deny individual permissions. Crucially, they could also revoke those permissions later directly through the device settings without having to uninstall the application.

Major Under-the-Hood Upgrades

Beyond the revolution in permissions, Marshmallow brought several vital architectural enhancements that paved the way for modern mobile design:

1. Doze Mode and App Standby: To combat battery drain, API 23 introduced smart power-saving features. Doze mode puts the device into a deep sleep state when it sits idle and stationary with the screen off. Meanwhile, App Standby restricts network access and background sync for applications that haven’t been actively used by the user for a prolonged period.
2. Standardized Fingerprint API: Prior to API 23, device manufacturers built proprietary biometric solutions. Marshmallow introduced a unified, native fingerprint authentication API, allowing developers to seamlessly integrate secure fingerprint logins and payment verifications into their apps.
3. Direct Share: This feature streamlined user workflows by letting individuals share content directly to specific contacts within specific apps right from the sharing menu.

The Developer Experience: Adapting to Change

For software developers, transitioning to API 23 was notoriously challenging. Codebases that previously assumed lifetime access to hardware components had to be rewritten to handle asynchronous permission callbacks (such as onRequestPermissionsResult) and gracefully manage scenarios where users denied or revoked access mid-use.

To maintain backward compatibility, Google introduced a clever buffer: apps targeting older API levels (API 22 or lower) ran under the legacy installation-time rules on Marshmallow devices, though users could still manually toggle permissions off in settings.

Legacy and Lasting Impact

API Level 23 established a new baseline for mobile software development. By shifting power away from forced installation demands and placing it firmly into the hands of the user via transparent runtime controls, it laid the structural cornerstone for the privacy-centric smartphone ecosystems we rely on today.