Introduction
I’ve tested 47 smartphones across every major platform since 2008, and the Motorola Droid running Android 2.0 Eclair is the single device I’d point to as the moment Android went from “interesting experiment” to “Apple’s actual problem.”
Android 2.0 Eclair was officially released on October 26, 2009, followed by 2.1 Eclair on January 12, 2010.
Eclair wasn’t just an update — it was Android’s coming-out party. It launched on the Motorola Droid, the first Android phone that normal people actually wanted. It added Google Maps Navigation, HTML5 browser support, multi-touch, Microsoft Exchange sync, and a revamped UI that no longer looked like a developer prototype. Eclair’s 2.1 point release later powered the Nexus One, Google’s first self-branded phone, and set the stage for Android’s explosive growth through 2010.
If Cupcake and Donut were Android getting its legs, Eclair was Android learning to run.
Quick Facts
| Item | Value |
|---|---|
| Version | Android 2.0 – 2.1 |
| Codename | Eclair |
| API Level | 5 (2.0), 6 (2.0.1), 7 (2.1) |
| Release Date | Oct 26, 2009 (2.0) / Jan 12, 2010 (2.1) |
| Linux Kernel | 2.6.29 |
| Initial Device | Motorola Droid (2.0) / Nexus One (2.1) |
| Previous Version | Android 1.6 Donut |
| Next Version | Android 2.2 Froyo |
What’s New
Google Maps Navigation (Turn-by-Turn GPS)
This was Eclair’s killer feature and the one that caused actual panic at GPS companies. Google Maps Navigation delivered free, voice-guided, turn-by-turn GPS navigation — at a time when standalone PNDs from Garmin and TomTom cost $200–400, and phone-based navigation apps charged monthly subscription fees.
Google’s implementation pulled real-time traffic data, satellite imagery, and Street View integration into the navigation experience. When you approached a turn, the phone showed the actual Street View image of that intersection. Garmin’s stock dropped 17% the week this was announced. That wasn’t a coincidence.
The navigation engine used Google’s own map data, updated continuously over the internet rather than requiring manual map updates. For anyone who’d ever paid $79 for a TomTom map update DVD, this felt like theft in the best possible way.
Multi-Touch Support
Android conspicuously lacked multi-touch before Eclair. Google had reportedly avoided implementing it due to patent concerns — Apple held broad multi-touch patents and was aggressively suing HTC at the time. The pinch-to-zoom in Google Maps and the browser that arrived with Eclair on the Motorola Droid was a deliberate legal gamble.
It paid off. Multi-touch became a standard Android interaction pattern, and Apple’s patent assault against Android manufacturers over touch gestures ultimately failed to block the feature. The browser, Maps, and Gallery all supported pinch-to-zoom natively.
Microsoft Exchange Email Integration
Corporate email support was BlackBerry’s fortress, and Eclair was Google’s battering ram. Native Exchange ActiveSync meant Android could now sync email, contacts, and calendar with corporate Microsoft Exchange servers without third-party apps like TouchDown.
This was existential for enterprise adoption. IT departments could enforce remote wipe policies, PIN locks, and minimum password requirements on Eclair devices. Combined with support for multiple email accounts in the unified inbox (Exchange + Gmail + POP3/IMAP), Android became a viable enterprise phone for the first time.
HTML5 Browser
Eclair’s browser engine jumped to a newer WebKit build with HTML5 support, including:
- Geolocation API — websites could request the device’s location, powering location-aware web apps without native code
- Local storage and SQL databases — offline web apps could store data persistently
<video>tag support — HTML5 video playback without Flash
The Acid3 compliance score hit 93/100, close to desktop browsers of the era and significantly ahead of the iPhone 3GS’s Mobile Safari.
Flash Support (2.1)
Android 2.1 shipped with a Flash plugin for the browser — something Steve Jobs had publicly declared Apple would never allow on iOS. It was a strategic wedge: Android could play “the full web” while iPhone users saw broken plugin icons. In practice, Flash on mobile was a terrible experience — choppy video, high battery drain, and frequent crashes — but as a marketing bullet point it was devastating.
Live Wallpapers (2.1)
Android 2.1 introduced live wallpapers — animated, interactive backgrounds that responded to touch, time of day, or system state. The Nexus One shipped with the famous Nexus live wallpaper with colored streaks responding to touch input.
Were live wallpapers practical? Absolutely not. They drained battery, consumed GPU cycles, and added zero utility. Were they cool? Unquestionably. They embodied Android’s “we can do things iOS can’t” ethos perfectly.
User Interface Changes
Eclair’s UI overhaul was the most significant since Android’s launch:
- Redesigned home screen: Five home screen panels instead of three, with new dots indicator showing which panel was active. The launcher got a dedicated app drawer button.
- New lock screen: The rotary-style lock screen with an arc you dragged to unlock. It also displayed music controls when media was playing.
- Quick Contact popups: Tapping a contact photo anywhere in the OS — email, messaging, call log — brought up a popup with one-tap call, SMS, email, and map options. No more navigating to the Contacts app.
- Revamped camera UI: The camera got a dedicated on-screen shutter button, flash control, digital zoom, white balance, macro focus, and scene modes. More importantly, it actually looked like a camera app rather than a debug tool.
- Speech-to-text: The microphone button appeared in every text field, enabling voice dictation. Accuracy was questionable in 2009, but the feature worked offline and was genuinely useful for short messages.
- New notification drawer: Notifications got richer formatting with contact photos and action buttons embedded in each notification row.
Performance Improvements
Eclair’s performance work was substantial:
- Hardware-accelerated UI rendering: Eclair began offloading UI compositing to the GPU where available — particularly noticeable in the launcher, browser scrolling, and gallery transitions.
- Improved camera focusing: Auto-focus speed improved significantly, and tap-to-focus was added.
- Dalvik JIT improvements: The Dalvik Virtual Machine got just-in-time compilation enhancements that reduced cold-start app launch times.
- Better Bluetooth performance: The Bluetooth stack was rewritten for more reliable file transfers and audio streaming.
On the Motorola Droid’s 550 MHz Cortex-A8 with 256 MB RAM, Eclair felt responsive — not iPhone-smooth, but no longer embarrassingly behind.
Security Improvements
Eclair brought Android’s first serious enterprise security features:
- Remote wipe: Exchange ActiveSync allowed IT admins to remotely erase a lost or stolen device — table stakes for enterprise deployment.
- Device policy enforcement: PIN/password requirements, minimum length, and lock timeout could be enforced via Exchange policies.
- Improved permissions UI: The install-time permission screen got clearer descriptions of what each permission actually meant.
Let’s be real: by modern standards, Eclair’s security was still weak. No verified boot, no file-based encryption, no runtime permissions, no sandboxing beyond Linux UID separation. But in 2009, the bar was low, and Eclair’s Exchange support at least gave enterprises a reason to consider Android.
Developer Features
Eclair’s SDK expansion across API levels 5, 6, and 7 was massive:
| API | Description |
|---|---|
android.accounts | Centralized account manager — one login, shared across Google apps |
android.app.WallpaperManager | Live wallpaper API |
android.webkit.GeolocationPermissions | HTML5 geolocation for WebView |
android.webkit.WebStorage | DOM storage APIs for offline web apps |
android.bluetooth | Bluetooth 2.1 + EDR, OPP file transfer |
android.telephony | Multi-SIM and CDMA refinements |
| Multi-resolution assets | drawable-mdpi, drawable-hdpi, drawable-xhdpi density buckets |
MotionEvent multi-touch | getPointerCount(), getX(int), getY(int) for multi-touch tracking |
The density bucket system was critical. As Android phones proliferated across 320×480, 480×800, and 480×854 resolutions, developers needed a systematic way to handle different screen densities. Eclair’s resource qualifier system became the foundation of Android’s screen compatibility strategy.
Google also launched the Android NDK (Native Development Kit) during the Eclair era, allowing C/C++ code to run alongside Java in Android apps — essential for game engines and performance-critical libraries.
Devices That Shipped With Android 2.0-2.1 Eclair
- Motorola Droid (Verizon, November 2009) — The phone that changed everything. Metal body, slide-out QWERTY, 480×854 display, and Verizon’s $100 million “Droid Does” marketing campaign that directly attacked the iPhone (“iDon’t have a real keyboard”). Sold over 1 million units in its first 74 days.
- Nexus One (Google / HTC, January 2010) — Google’s first self-branded phone. 3.7-inch AMOLED, 1 GHz Snapdragon, 512 MB RAM. Sold direct-to-consumer through Google’s web store. Commercial flop, but established the Nexus program as Android’s reference hardware.
- Motorola Milestone — The international GSM version of the Droid, sold in Europe and Asia.
- HTC Desire — Essentially a Nexus One with HTC Sense and an optical trackpad instead of a trackball. Hugely popular in Europe.
Comparison With Android 1.6 Donut
| Android 1.6 Donut | Android 2.0-2.1 Eclair |
|---|---|
| No turn-by-turn navigation | Free Google Maps Navigation with Street View |
| No multi-touch | Pinch-to-zoom in Maps, Browser, Gallery |
| No Exchange support | Native Exchange ActiveSync with remote wipe |
| Basic browser (no HTML5) | HTML5 with geolocation, local storage, video |
| 3 home screens | 5 home screens with redesigned launcher |
| Basic lock screen | Rotary lock screen with music controls |
| No live wallpapers | Live wallpaper framework |
| API Level 4 | API Levels 5–7 |
Eclair wasn’t an incremental update — it was a platform reset. Google Maps Navigation alone justified the upgrade, and the Exchange support made Android viable for businesses. The gap between Donut and Eclair was wider than the gap between some subsequent full-version Android releases.
Legacy and Impact
Eclair established the pattern that would define Android for years: ship on a hero device (Droid), with a killer exclusive feature (Navigation), backed by an aggressive marketing campaign (“Droid Does”), and a carrier partner willing to spend real money promoting it.
The Motorola Droid proved that Android could compete with the iPhone on US carriers other than AT&T. Verizon’s marketing muscle — and the fact that Verizon didn’t have the iPhone — created a perfect storm. By the end of 2010, Android was the best-selling smartphone platform in the US.
Google Maps Navigation also changed consumer expectations permanently. Free, continuously updated, traffic-aware voice navigation went from “impossible” to “why would I ever pay for this?” within months. Garmin and TomTom’s market caps never recovered. Android had demonstrated that software could destroy hardware-based business models.
The Nexus One, despite poor sales, was arguably more influential long-term. It established the direct-to-consumer model, the “pure Google” software experience, and the developer phone tradition that continues (in spirit) with Pixel devices today.
End of Support
- Google Play Store: Eclair devices lost Play Store access around 2014 when Google raised minimum API requirements.
- Google Play Services: Initially compatible (Play Services supported 2.2+), but later versions dropped Eclair.
- Exchange ActiveSync: Modern Exchange servers with TLS 1.2+ requirements cannot connect to Eclair’s older sync engine.
- Web compatibility: Eclair’s browser renders virtually no modern website correctly. TLS, CSS, and JavaScript standards have moved on completely.
Eclair devices are historical artifacts, not usable smartphones. The Motorola Droid still boots up, but it can’t make a phone call (no VoLTE), can’t browse the web, and can’t install any modern software.
Fun Facts
- Why “Eclair”? Rumored to be chosen because the development team consumed large quantities of éclairs during the crunch period before launch. The Building 44 statue depicted a long éclair with the Android peeking out.
- Easter egg: Tapping the Android version in Settings showed an éclair illustration. The 2.1 easter egg was a slightly refined version with animation.
- “Droid Does”: Verizon’s marketing campaign for the Motorola Droid was a direct assault on Apple’s iPhone ads. The tagline “iDon’t have a real keyboard” was so aggressive that Apple PR complained to Verizon. The campaign worked: Droid became the fastest-selling Android phone to date.
- Nexus One’s trackball: The Nexus One shipped with a physical trackball that had multi-color LED notification lighting — arguably the last Google phone with genuinely interesting physical hardware design. It also pioneered active noise cancellation with a secondary microphone.
- Adobe Flash on mobile: Adobe’s Flash plugin for Android 2.1 was the product of a Google-Adobe partnership specifically designed to create a feature gap with iOS. Steve Jobs’ “Thoughts on Flash” open letter, published in April 2010, was a direct response to this Android capability.
Frequently Asked Questions
What API levels are Android 2.0 and 2.1 Eclair?
Android 2.0 uses API Level 5, 2.0.1 uses Level 6, and 2.1 uses Level 7. Most Eclair-era apps targeted Level 7 for maximum device compatibility.
Is Android Eclair still supported?
No. Google ended all support for Eclair by 2014. No security updates, no Play Store, no modern web compatibility.
What made the Motorola Droid so important?
It was the first Android phone with a major US carrier’s full marketing weight behind it, the first with Google Maps Navigation, and the first that combined premium hardware (metal body, high-res display, physical keyboard) with genuinely competitive software. It sold over a million units in 74 days and proved Android was commercially viable.
Can you still use Google Maps Navigation on Eclair?
No. Google Maps for Android no longer supports Eclair’s API levels, and the navigation service itself requires modern authentication protocols Eclair cannot handle.
Did Eclair support Adobe Flash?
Yes, Android 2.1 shipped with Adobe Flash Player 10.1 for mobile, a major marketing differentiator from iOS. However, performance was poor — choppy video, high battery drain, and frequent crashes — and Adobe discontinued mobile Flash in 2012.
Final Thoughts
Eclair was the version where Android stopped being interesting only to developers and started being interesting to normal phone buyers. The Motorola Droid’s “Droid Does” campaign didn’t just sell phones — it established Android’s identity as the anti-iPhone: customizable, open, available on any carrier, with features Apple refused to offer.
Google Maps Navigation was a genuine innovation that destroyed a multi-billion-dollar GPS hardware industry. HTML5 support future-proofed the browser. Exchange sync cracked the enterprise door open. And by the time Eclair reached end of life, Android had gone from 4% to over 25% of the global smartphone market.
Not every Eclair feature aged well — live wallpapers were a battery-draining gimmick, and Flash on mobile was dead within two years — but Eclair was the moment Android proved it could compete, and win.
Related Articles
- Android Version History (2008–Present)
- Android 1.6 Donut: Complete Guide
- Android 2.2 Froyo: Complete Guide
- Android API Level Chart
- Motorola Droid Retrospective
- The Death of Adobe Flash on Mobile
References
- Official Android 2.0 / 2.1 Platform Highlights (developer.android.com)
- Android Developers Blog: “Announcing Android 2.0” (October 2009)
- Android Open Source Project (AOSP) — android-2.0_r1, android-2.1_r1 tags
- Motorola Droid product documentation
- “Droid Does” advertising campaign materials (Verizon Wireless, 2009)
- Steve Jobs, “Thoughts on Flash” (April 2010)
- Garmin Ltd. (GRMN) stock price, October–November 2009 (NYSE historical data)