Android 6.0 Marshmallow API 23: Complete Developer Guide

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

In the fast-paced world of software development, certain version numbers carry historic weight. For the Android ecosystem, API Level 23—better known as Android 6.0 (Marshmallow)—stands as one of the most transformative milestones in mobile operating system history.

Released by Google, this update did more than just introduce incremental visual tweaks or under-the-hood performance boosts. It fundamentally revolutionized how applications interact with user data, privacy, and hardware permissions.

The Pre-Marshmallow Reality: All-or-Nothing Permissions

To understand why API 23 was a watershed moment, you have to look back at how Android handled permissions prior to 2015.

In the era of API levels 22 and below, Android used an installation-time permission model. When a user went to the Google Play Store and clicked “Install” on an app, a long list of requested permissions would pop up—access to the camera, location, contacts, and storage.

This system had a fatal flaw: it was all-or-nothing. If a user wanted a simple flashlight app, but the app demanded access to their contacts and location, the user had only two choices: accept all terms blindly or forego the app entirely. Unsurprisingly, users rarely read these lists, creating a massive loophole for malicious actors to harvest private data unnoticed.

Enter API 23: The Runtime Permissions Revolution

API 23 turned this paradigm upside down by introducing runtime permissions.

Instead of forcing users to grant every permission upfront during installation, apps targeting API 23 (and higher) had to request permissions dynamically while the app was actively running.

• Contextual Prompts: If a photo-editing app wanted to use the camera, it couldn’t just assume it had access. It had to trigger a system dialog asking for permission at the exact moment the user tried to snap a picture.
• Granular Control: Users gained the power to grant or deny individual permissions. Even better, if a user denied a permission, they could change their mind later by toggling permissions individually in the Android system settings.
• Revocability: Users could revoke permissions from an app at any time, even if the app had already been installed and used for months.

This single change dramatically enhanced user privacy and forced developers to write cleaner, more resilient code that could gracefully handle situations where a user said “No” to a permission request.

Other Defining Features of API 23

While runtime permissions stole the spotlight, API 23 brought several other vital developer tools and architectural changes to the platform:

• Doze Mode and App Standby: Marshmallow introduced aggressive power-saving features. Doze mode put the device into a low-power state when left idle, while App Standby restricted background network access and syncs for apps that hadn’t been used recently, drastically improving battery life.
• Native Fingerprint Authentication: API 23 standardized biometric security, providing standard APIs (FingerprintManager) so developers could seamlessly integrate fingerprint login into banking, shopping, and lock screens.
• Direct Share: Making sharing content between apps faster by letting developers target specific direct-share targets (like a specific chat thread in a messaging app) right from the system share sheet.
• Text Selection Actions: Floating toolbars appeared right next to selected text, making cut, copy, paste, and web searches much more intuitive.

The Legacy of API 23 in Modern Android Development

API 23 proved to be a defining line in Android’s history. For years, Google used API 23 as a baseline requirement for various security and library updates. Even as modern Android moves forward into double-digit version numbers, the architecture established in Marshmallow forms the bedrock of current mobile privacy standards.

For developers, API 23 serves as a reminder that platform evolution is driven by user trust. By shifting the power dynamic from developers to users, API 23 not only cleaned up the app ecosystem but also set a gold standard for mobile operating systems worldwide.