Android 6.0 Marshmallow API 23 Features and Overview

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

In the fast-paced ecosystem of mobile software development, few version numbers carry as much historical and structural weight as API 23. Formally tied to Android 6.0 (Marshmallow), released by Google in late 2015, API 23 marks a definitive turning point in how mobile applications interact with user privacy, hardware components, and operating system permissions.

Whether you are a seasoned Android veteran looking down memory lane or a newcomer trying to decipher legacy codebase constraints, API 23 remains a critical baseline in software architecture.

What Makes API 23 Special?

Before API 23, the Android permission model mirrored early desktop operating systems: installation-time granting. When a user downloaded an app from the Google Play Store, they were presented with a static, all-or-nothing list of permissions (accessing the camera, reading contacts, tracking location, reading storage). If you didn’t want the app to have access to even one of those items, your only choice was not to install the app at all.

API 23 shattered this paradigm by introducing Runtime Permissions.

Instead of asking for everything upfront, apps targeting API 23 (or higher) had to request sensitive permissions at the exact moment the user tried to use a feature requiring them. For instance, an app wouldn’t gain access to your device’s camera the moment you downloaded it; it had to prompt you with a dialog box (“Allow [App] to take pictures and record video?”) right when you tapped the shutter button inside the app.

Key Innovations Introduced in API 23

Beyond runtime permissions, API 23 introduced a suite of underlying platform features that shaped modern Android development:

• Doze Mode and App Standby: Android 6.0 introduced intelligent power-saving features. Doze mode put the device into a deep sleep state when left unattended, while App Standby prevented rarely used apps from draining background battery resources.
• Fingerprint Authentication Support: API 23 provided a standard, system-level API for integrating biometric fingerprint scanners into apps securely, paving the way for modern passwordless logins and in-app mobile payments.
• Direct Share: Enhancing the sharing sheet to allow users to share content directly to specific contacts within various apps seamlessly.
• Text Selection Actions: A contextual floating toolbar for text selection that made actions like “Copy,” “Cut,” “Paste,” and web searching much faster and more intuitive.

The Legacy of API 23 in Modern Development

Even years after its debut, API 23 holds a unique strategic position in Android project configurations, frequently appearing as a historical baseline or minimum SDK consideration in modern libraries (such as Android Jetpack components).

Navigating API 23 guidelines required a fundamental shift in defensive programming. Developers could no longer assume that ContextCompat.checkSelfPermission() would always return true. Codebases had to gracefully handle scenarios where users denied permissions, offering rationales, alternative workflows, or fallback states without crashing.

Summary

API 23 was far more than just a routine dessert-themed update. By shifting the power dynamic from the developer to the end-user via runtime permissions, it forced an industry-wide elevation of privacy standards. Android 6.0’s foundational architecture laid the groundwork for the robust, privacy-centric mobile ecosystems we rely on securely every single day.