Android 6.0 Marshmallow API 23 Features and Guide

Understanding Android API 23: The Milestone That Changed Mobile Security Forever

When developers talk about Android’s history, certain API levels stand out as true paradigm shifts. Among them, API Level 23—better known as Android 6.0 Marshmallow—occupies a legendary status. Released by Google in late 2015, API 23 did more than just introduce routine system updates or minor UI tweaks; it fundamentally restructured how applications interact with user privacy and device hardware.

For anyone building, auditing, or studying mobile software ecosystems, API 23 represents the dividing line between the “wild west” era of Android permissions and the modern, user-centric security model we rely on today.

The Pre-Marshmallow Problem: The “All-or-Nothing” Trap

Before API 23, Android handled permissions using an installation-time model. When a user went to the Google Play Store and clicked “Install” on an app, a long list of requested permissions—access to the camera, contacts, location, and storage—would pop up on a single static screen.

The catch? It was an absolute all-or-nothing proposition.

• If a user wanted a simple offline flashlight app, but the app demanded access to their contacts and precise GPS location, they had two choices: accept everything or don’t install the app at all.
• Naturally, many users blindly clicked “Accept,” leading to widespread data harvesting, background tracking, and legitimate security vulnerabilities.

Developers, too, suffered from friction. Conversion rates often dropped because users were spooked by apps requesting massive bundles of permissions upfront, even if those features were only needed later in the user journey.

Enter API 23: The Runtime Permissions Revolution

Android 6.0 Marshmallow dismantled the installation-time model entirely by introducing runtime permissions.

Instead of demanding every key to the kingdom upfront, apps targeting API 23 were required to ask users for sensitive permissions (termed “dangerous permissions” like location, camera, microphone, or contacts) at the exact moment the feature was actually used.

• Contextual Prompts: If a user tapped a “Take a Photo” button inside a chat app for the first time, a system-level dialog would appear right then asking: “Allow [App Name] to take pictures and record video?”
• Granular Control: Users could finally say “Deny” to specific requests while continuing to use the rest of the application. Furthermore, users could dive into system settings at any time to revoke permissions from apps they had previously trusted.

This single architectural pivot fundamentally realigned Android with modern privacy expectations, putting power back into the hands of the consumer.

Beyond Permissions: Other Defining Features of API 23

While runtime permissions stole the spotlight, API 23 introduced several other foundational APIs and system behaviors that shaped modern Android development:

1. Doze Mode and App Standby: Marshmallow introduced aggressive power-saving features. When a device was left unattended, screen-off, and stationary, Doze mode would defer background CPU and network activities to drastically preserve battery life. App Standby similarly throttled apps that hadn’t been actively used for a while.
2. Native Fingerprint Authentication: API 23 standardized biometric authentication. Instead of manufacturers building fragmented, proprietary fingerprint APIs for their specific hardware, developers received a unified FingerprintManager API to securely authenticate users via fingerprint sensors.
3. Direct Share: The sharing sheet received an upgrade, allowing developers to target specific direct-share targets (like a specific chat thread inside a messaging app) rather than just broad application categories.

The Legacy and Modern Relevance of API 23

Fast-forward to today, and API 23 serves as a baseline milestone. Modern Android development frameworks, Jetpack libraries, and Google Play Store requirements have progressively raised minimum SDK targets well past Marshmallow to ensure optimal performance, security, and access to newer system capabilities.

However, the ripple effects of API 23 are still felt daily. Every time a clean, non-intrusive system prompt asks for your permission to access your microphone or location—and respects your right to say “Don’t allow”—you are experiencing the direct legacy of Android Marshmallow.

API 23 proved that platform security and developer flexibility could evolve hand-in-hand, forever changing the blueprint for mobile operating systems.