Android 6.0 Marshmallow API 23: Complete Guide & Features

Understanding Android API 23: The Milestone That Redefined Mobile Security

When discussing milestones in mobile operating system history, few updates have been as quietly revolutionary as Android 6.0 Marshmallow, corresponding to API Level 23. Released by Google, this version fundamentally reshaped how applications interact with user data, hardware, and system permissions.

While newer Android versions have since built upon its foundation, API 23 remains a critical baseline in mobile development lore—primarily because it marked the death of the “install-time permission” model.

The Pre-Marshmallow Wild West

Before API Level 23, Android’s permission system operated on an “all-or-nothing” basis during installation. When a user wanted to download an app from the Google Play Store, a comprehensive list of permissions—accessing the camera, reading contacts, tracking location, or writing to storage—was presented upfront.

If a user wanted the app, they had no choice but to accept all of them. Once installed, the application had carte blanche to use those permissions indefinitely. This created massive privacy vulnerabilities: a simple flashlight app could secretly harvest contact lists or track GPS data without the user ever realizing it.

Enter API 23: The Runtime Permissions Revolution

API Level 23 turned this paradigm completely on its head by introducing runtime permissions.

Instead of demanding every permission at the moment of installation, apps targeting API 23 had to request access to sensitive resources (known as “dangerous permissions”) at the exact moment they were needed—such as when a user first taps the “take a photo” or “share location” button.

• User Control: Users could finally grant or deny individual permissions granularly.
• Revocability: Users could dive into system settings at any time and revoke a permission from an app that already had it, without needing to uninstall the app entirely.
• Graceful Degradation: Developers were forced to write code that handled scenarios where a user clicked “Deny,” ensuring apps wouldn’t instantly crash if a permission was withheld.

Other Defining Features of API 23

Beyond runtime permissions, Android API 23 introduced several other under-the-hood upgrades that modern developers still rely on:

1. Doze Mode and App Standby: To combat battery drain, API 23 introduced power-saving features that put the device into a deep sleep state when left idle, or restricted background network access for apps that hadn’t been used recently.
2. Fingerprint Authentication Support: Marshmallow brought standardized, native APIs for hardware-backed fingerprint scanners, paving the way for secure mobile banking and passwordless logins.
3. Direct Share: Enhancing the sharing sheet to allow users to share content directly to specific contacts within various apps seamlessly.

The Legacy of API 23 in Modern Development

Even years after its debut, API Level 23 holds a special place in the Android ecosystem. For a long time, it served as the baseline standard (minSdk) for many modern Android libraries, ensuring compatibility across a vast majority of active legacy devices.

Ultimately, API 23 shifted the philosophy of mobile software design from trust-by-default to permission-on-demand. It laid the bedrock for contemporary digital privacy, transforming user interaction on smartphones into a safer, more transparent experience.