What Is New in Android 1.6
| Category | Key Changes |
|---|---|
| New Features | Android Market, Gestures, Text-to-speech, New Camera/Gallery integration |
| Platform Improvements | Search framework, Screen support (QVGA, WVGA), Battery usage indicator |
| Developer Tools | Updated SDK, New DDMS, GestureBuilder tool |
| Accessibility | Explore-by-touch, Accessibility APIs |
How did Android 1.6 improve the user experience?
Android 1.6, codenamed Donut, introduced the Android Market, fundamentally changing how users discover and install apps. This was a massive shift from manual APK installation to a centralized, curated storefront.
The update also brought a new integrated Camera, Camcorder, and Gallery experience. Users could now switch between photo and video modes with a single toggle and quickly review their shots from the camera interface itself.
Gesture Support
Developers could now build apps that responded to custom gestures. The SDK included a GestureBuilder tool to create and test gesture libraries, paving the way for more intuitive, touch-driven interfaces.
What developer tools were added in Android 1.6?
The SDK tools saw significant upgrades. DDMS (Dalvik Debug Monitor Server) got a major overhaul, making it easier to profile an app's memory usage and track thread activity.
A new battery usage indicator was a game-changer for debugging. Developers could finally see exactly which services and processes were draining the battery, helping them optimize for longer battery life.
Screen Support
Donut added official support for more screen densities, specifically QVGA (low-density) and WVGA (high-density) screens. This meant building apps that could scale properly across a wider range of devices was now a core part of development.
How did Android 1.6 handle accessibility?
This release marked a huge leap forward for accessibility with the introduction of the "Explore by Touch" mode. It provided spoken feedback so users with visual impairments could navigate their devices without seeing the screen.
New accessibility APIs allowed developers to make their apps accessible. This meant apps could now be built to work seamlessly with screen readers and other assistive technologies.
What new APIs should developers start using?
The text-to-speech (TTS) engine API was a standout addition. It allowed apps to speak text, which was crucial for navigation apps, accessibility features, and creating new kinds of audio feedback.
The new search framework APIs were powerful. Developers could now expose their app's content to the global system search, making it discoverable from the home screen search box.
Example: Creating a Searchable Activity
<activity android:name=".SearchableActivity" >
<intent-filter>
<action android:name="android.intent.action.SEARCH" />
</intent-filter>
<meta-data android:name="android.app.searchable"
android:resource="@xml/searchable"/>
</activity>FAQ
How do I integrate with the new Android Market?
You need to prepare your application for publication by finalizing your app's APK, creating a listing with descriptions and graphics, and then uploading everything through the Android Developer Console. The Market handles distribution and updates.
What's the easiest way to add gesture support to my app?
Use the GestureBuilder tool (included in the SDK samples) to create a gesture library file. Then, in your app, load that library and use the GestureOverlayView to recognize when a user draws a matching gesture.
My app has a custom search, should I use the new search framework?
Absolutely. Integrating with the global search framework makes your app's content instantly discoverable from the home screen. It significantly improves user engagement without them needing to open your app first.
How does the new screen density support affect my existing layouts?
You should start providing alternative bitmap drawables for different densities (ldpi, mdpi, hdpi). The system will automatically select the correct one, ensuring your UI looks sharp on both old and new, higher-resolution devices.
Is the Text-to-Speech engine available on all devices?
No, it requires a TTS engine that supports the appropriate language. You should always check for availability using the TextToSpeech.Engine.INTENT_ACTION_CHECK_TTS_DATA intent before trying to use it in your app.