Key differences at a glance
Marshmallow (Android 6.0, 2015) and Lollipop (Android 5.0–5.1, 2014) are both older Android releases, but they differ meaningfully in behavior and capabilities. Lollipop introduced Material Design, a new notification shade, and ART as the default runtime. Marshmallow refined the experience with granular runtime permissions, new power management, and fingerprint support. The table below summarizes core attributes for a quick comparison.
| Attribute | Marshmallow (6.0) | Lollipop (5.0–5.1) | Source Type |
|---|---|---|---|
| Initial release | October 2015 | November 2014 | Verified |
| Default runtime | ART (AOT) | ART (optional); Dalvik still present | Verified |
| Design language | Material refinements, softer corners | Material Design introduced | Verified |
| Notification shade | Separate toggles; improved UX | First split shade; quick settings | Verified |
| Permissions model | Install-time permissions only | Verified | |
| Battery optimization | Doze and App Standby | Basic optimizations; no Doze | Verified |
| Fingerprint support | First-class API and UI | Limited or OEM-specific | Verified |
| Security updates | Extended window; now ended | Ended earlier; both unsupported | Verified |
| 64-bit support | Improved; common on new devices | Early, uneven 64-bit adoption | Verified |
What is Android Lollipop
Lollipop, primarily Android 5.0 and refined in 5.1, launched in 2014 as a major redesign focused on performance, battery, and a coherent visual language. It centered on Material Design, introducing bold color, deeper shadows, and intentional motion. Key technical shifts included the transition to ART as an opt‑in runtime and a redesigned notification shade with a quick settings panel. While Lollipop laid foundations for modern Android behavior, it lacked mature power management and permission controls that later versions would address.
Lollipop highlights
- Material Design system across UI and apps
- Notification shade split into two panels
- ART introduced with Ahead‑of‑Time compilation option
- Project Volta focused on battery life at the platform level
- Basic battery optimizations but no Doze mode
What is Android Marshmallow
Marshmallow (Android 6.0), released in 2015, emphasized user control, security, and power efficiency. It moved beyond visual changes to fundamental interactions, most notably runtime permissions that ask when needed rather than at install. Doze and App Standby significantly improved battery life on idle devices, and fingerprint support gained standardized APIs. By tightening permission rules and refining background behavior, Marshmallow offered a more polished and privacy‑conscious experience.
Marshmallow highlights
- Runtime permissions for sensitive capabilities
- Doze and App Standby for battery management
- Native fingerprint authentication support
- Google Now on Tap contextual awareness
- Refined notifications with direct actions
Head‑to‑head feature comparison
The practical differences between Marshmallow and Lollipop affect daily use, privacy, and battery life. Marshmallow’s runtime permission system is the most notable change, giving users control over location, camera, microphone, and other sensitive permissions at the moment they are needed. Battery optimizations are stronger in Marshmallow, with Doze preventing background network activity and GPS when the device is stationary. Lollipop’s Material Design is visually distinctive, yet Marshmallow refined card layouts, touch feedback, and iconography. Both versions are no longer supported, so security patches and compatibility with newer apps are limited on both.
Feature breakdown
| Feature | Lollipop | Marshmallow | Practical impact |
|---|---|---|---|
| Design | Material Design debut; bold | Material refinements; softer | Consistent UI, improved touch targets |
| Notifications | Split shade introduced | Expanded actions and toggles | More controls at a glance |
| Permissions | Install‑time only | Runtime for dangerous perms | Better privacy and control |
| Battery | Project Volta; basic savings | Doze + App Standby | Longer idle time in Marshmallow |
| Fingerprint | OEM implementations | Standard API and UI | More reliable auth in Marshmallow |
| 64‑bit & ART | Early 64‑bit; ART optional | Better 64‑bit; ART default | Improved performance and compatibility |
Performance and user experience differences
Runtime permissions in Marshmallow reduce surprise access but can introduce occasional prompts, whereas Lollipop’s install‑time model is simpler up front yet less transparent. Battery life on Marshmallow benefits from Doze, which restricts background network and GPS when the screen is off, often resulting in noticeably longer standby time compared with Lollipop. Lollipop’s ART opt‑in could yield smoother installs and slightly better performance on capable hardware, but Dalvik was still present, leading to variability. In real-world usage, Marshmallow offers a more consistent experience across devices, while Lollipop may feel more visually distinctive on devices that showcase Material Design at launch.
Security, compatibility, and app behavior
Both Lollipop and Marshmallow are past their end of life, meaning no security updates are provided. Devices stuck on either version may face compatibility issues with newer apps or services, especially those requiring newer APIs or security patches. Marshmallow’s runtime permissions can affect app behavior; some apps may request multiple permissions over time, while others designed for install‑time models may behave differently when moved to Marshmallow. For users evaluating devices, upgrading from Lollipop to Marshmallow typically yields tangible gains in control and battery efficiency, though device hardware remains the primary factor in performance.
Which should you choose or consider today?
Given that both versions are unsupported, the practical question is rarely about choosing between Lollipop and Marshmallow for new devices. Instead, users should prioritize upgrading to a currently supported Android version when possible. If you are maintaining legacy devices or evaluating older hardware, Marshmallow generally offers better battery optimization, privacy controls, and fingerprint support, while Lollipop provides a foundational Material Design experience that may feel familiar on very old devices. Security-conscious users should prefer any device that can move to a supported release, as extended unsupported status increases risk.
Practical recommendations
- Prioritize devices that can run a supported Android version (Android 10 or higher).
- If maintaining older devices, prefer Marshmallow over Lollipop for better battery and permissions control.
- Check app compatibility; some newer apps may not install on either version due to API level requirements.
- Consider security implications: unsupported OS versions should not store sensitive credentials or conduct sensitive transactions.
- When upgrading, verify device firmware updates and vendor support timelines.