Understanding Android 6.0 Marshmallow API 23 Features

API 23 corresponds to Android 6.0 Marshmallow, released by Google in 2015. It represents a massive watershed moment in mobile operating system history, fundamentally transforming how Android devices handle user privacy, power management, and application security.

Here is a look at what made Android API Level 23 a pivotal milestone in software development and mobile technology.

1. The Runtime Permissions Revolution

Before API 23, Android utilized an “all-or-nothing” installation-time permission model. When users downloaded an app from the Google Play Store, they were presented with a long list of permissions (accessing the camera, contacts, location, microphone, etc.) that they had to accept before the app installed. If a user didn’t want to grant even one of those permissions, their only option was not to use the app at all.

API 23 changed everything by introducing Runtime Permissions.

• Just-in-Time Prompts: Apps could now request sensitive permissions (classified as “dangerous”) when the user actually tried to use a specific feature. For instance, a messaging app wouldn’t ask for camera access upon installation; it would only ask when the user tapped the camera icon to take a photo.
• Granular Control: Users gained the power to grant or deny individual permissions and could revoke them at any time through the device settings menu without breaking the entire app experience.

2. Smarter Power Management: Doze Mode and App Standby

Battery life has always been a primary concern for mobile users. API 23 introduced two core features designed to drastically reduce power consumption:

• Doze Mode: When a device was left unattended, screen-off, and stationary, Doze Mode would periodically wake up the system briefly to handle syncs and background tasks while otherwise keeping CPU and network-intensive services asleep.
• App Standby: This feature recognized apps that weren’t actively being used, putting them into a “standby” state so they wouldn’t drain background resources or battery life unnecessarily.

3. Native Fingerprint Authentication

Prior to API 23, manufacturers like Samsung or Motorola built custom, fragmented APIs to support fingerprint sensors on their respective hardware. Marshmallow standardized this capability by introducing a native Fingerprint API. This allowed developers to easily integrate secure biometric authentication into their apps—such as for banking, logins, and secure vault storage—with a consistent user experience across different phone brands.

4. Direct Share and Text Selection Enhancements

• Direct Share: API 23 introduced targets for the sharing menu, allowing apps to present specific, deep-linked targets (like a frequent chat contact) directly in the share sheet rather than just listing generic apps.
• Floating Text Selection Toolbar: When selecting text within an application, the copy/paste toolbar was redesigned to float right next to the selected text rather than residing at the top of the screen, making editing much faster and more intuitive.

Why API 23 Still Matters Today

While modern Android versions have marched far ahead (introducing advanced privacy dashboards, notification permissions, and much stricter scoped storage), API 23 remains a legendary building block. For developers, API 23 established baseline expectations for user consent and hardware integration that continue to dictate how modern secure mobile architecture is designed.