Android 6.0 Marshmallow API 23 Features and Guide

In the world of mobile software development, few milestones have been as transformative as API 23—better known to the world as Android 6.0 Marshmallow. Released by Google, this specific API level fundamentally reshaped how applications interact with users, hardware, and privacy controls.

Even years after its initial rollout, API 23 remains a critical benchmark in Android software engineering, marking the dividing line between the “wild west” era of mobile permissions and the modern, user-centric security paradigm we rely on today.

The Paradigm Shift: Runtime Permissions

Before API 23, Android followed an “all-or-nothing” installation model. When a user downloaded an app from the Google Play Store, a long, intimidating list of requested permissions—access to the camera, contacts, location, microphone, and storage—was displayed upfront. Once the user hit “Install,” the app was granted blanket access to everything indefinitely. If a user was uncomfortable with even one requested permission, their only choice was not to use the app at all.

API 23 shattered this model by introducing Runtime Permissions.

Under this new framework, applications could no longer assume background access to sensitive data or hardware. Instead, apps had to request permissions contextually—at the exact moment the feature was actually needed. For instance, a messaging app wouldn’t ask for camera access upon installation; it would only prompt the user with a native dialog box the moment they tapped the “Take Photo” button.

This change accomplished two major goals:

1. Empowered Users: Users gained granular control over their privacy, with the ability to grant or deny specific permissions and even revoke them later through device settings.
2. Improved Conversion: App installation drop-offs decreased because users were no longer scared away by massive lists of upfront permission demands.

Beyond Permissions: Other Pillars of API 23

While runtime permissions stole the spotlight, API 23 introduced several other under-the-hood enhancements that laid the foundation for modern Android architecture:

• Doze Mode and App Standby: Battery life optimization took a massive leap forward. Doze mode allowed devices to enter a deep sleep state when left idle, deferring CPU-intensive background tasks and network activity. App Standby similarly throttled infrequently used apps to prevent background battery drain.
• Native Fingerprint Authentication: API 23 standardized biometric security, providing developers with a unified system API (FingerprintManager) to integrate hardware fingerprint sensors securely into login flows, payment confirmations, and app locks.
• Direct Share: Sharing content to specific contacts inside other apps became vastly streamlined, allowing developers to target direct shortcuts instead of forcing users through multiple layers of menus.
• Text Selection and Action Floating Toolbar: Copy-pasting and editing text received a modern overhaul with contextual floating action bars appearing right next to selected text.

Legacy and Impact on Modern Development

API 23 acts as an enduring milestone in mobile engineering compatibility. For a long time, it served as a baseline minSdk threshold for various libraries and modern jetpack components as older legacy versions of Android phased out of active market share.

Writing code for API 23 required developers to adopt defensive programming patterns—always checking if a permission was granted (ContextCompat.checkSelfPermission) before executing code blocks, and gracefully handling user rejections without crashing the app.

Conclusion

API 23 was much more than a routine incremental update; it was a cultural and architectural turning point for Android. By shifting the philosophy from implicit trust to explicit consent, API 23 permanently raised the bar for mobile data privacy, setting a gold standard that continues to influence how operating systems protect users across the globe.