A closer look at Android 2.3 (Gingerbread)

So finally I’ve had the time to write a new post. This week has been a busy release week. Google released Android’s Gingerbread, and Robotium released their 2.0 version.
So let’s take a closer look at Google’s Android 2.3 a.k.a Gingerbread.

Gingerbread for Users

The new features for users in Gingerbread are detailed on the Android Developers website. To summarize, those are as follows:

  • UI Refinements
  • New Keyboard
  • Word Selection Improved
  • Copy/Paste Improved
  • Improved Power Management: Android now is more active in managing apps that keep the device awake, even going so far as to close apps when appropriate. In the Application Settings, users can now see how the battery is being used by various apps.
  • Application Control
  • Internet Calling: Internet Calling (SIP) addresses can be added to Contacts and calls can be placed from the Quick Contact or Dialler. A SIP account is needed for this feature to work. This feature will be available depending on manufacturer and carrier support.
  • NFC: Near-field communications support is now included in the OS. With NFC, you can “touch” or “swipe” an NFC tag embedded in a poster, sticker, ad, or anywhere else and then be directed to a website associated with the URL included in the tag’s data. NFC support will be determined by the phone’s hardware.
  • Downloads Management
  • Camera: The camera app now provides access to multiple cameras on the device, if the phone includes more than one (such as a front-facing camera, for example).

Gingerbread for Developers

Developers need to be aware of the following features:

  • StrictMode
  • Concurrent garbage collector: The Dalivik VM introduces a new, concurrent garbage collector that minimizes application pauses, helping to ensure smoother animation and increased responsiveness in games and similar applications.
  • Faster event distribution: The platform now handles touch and keyboard events faster and more efficiently, minimizing CPU utilization during event distribution. The changes improve responsiveness for all applications, but especially benefit games that use touch events in combination with 3D graphics or other CPU-intensive operations.
  • Updated video drivers: The platform uses updated third-party video drivers that improve the efficiency of OpenGL ES operations, for faster overall 3D graphics performance.
  • Event Handling: Applications that use native code can now receive and process input and sensor events directly in their native code, which dramatically improves efficiency and responsiveness. Native libraries exposed by the platform let applications handle the same types of input events as those available through the framework. Applications can receive events from all supported sensor types and can enable/disable specific sensors and manage event delivery rate and queueing.
  • New Sensor Types: Android 2.3 adds API support for several new sensor types, including gyroscope, rotation vector, linear acceleration, gravity, and barometer sensors. Applications can use the new sensors in combination with any other sensors available on the device, to track three-dimensional device motion and orientation change with high precision and accuracy. For example, a game application could use readings from a gyroscope and accelerometer on the device to recognize complex user gestures and motions, such as tilt, spin, thrust, and slice.
  • Open API for Native Audio: The platform provides a software implementation of Khronos OpenSL ES, a standard API that gives applications access to audio controls and effects from native code. Applications can use the API to manage audio devices and control audio input, output, and processing directly from native code.
  • Native graphics management: The platform provides an interface to its Khronos EGL library, which lets applications manage graphics contexts and create and manage OpenGL ES textures and surfaces from native code.
  • Native access to Activity lifecycle, window management: Native applications can declare a new type of Activity class, NativeActivity whose life-cycle callbacks are implemented directly in native code. The NativeActivity and its underlying native code run in the system just as do other Activities — they run in the application’s system process and execute on the application’s main UI thread, and they receive the same life-cycle callbacks as do other Activities. The platform also exposes native APIs for managing windows, including the ability to lock/unlock the pixel buffer to draw directly into it..
  • Native access to assets, storage: Applications can now access a native Asset Manager API to retrieve application assets directly from native code without needing to go through JNI. If the assets are compressed, the platform does streaming decompression as the application reads the asset data. There is no longer a limit on the size of compressed .apk assets that can be read. Additionally, applications can access a native Storage Manager API to work directly with OBB files downloaded and managed by the system. (Dev tools for creating and managing OBB files will not be available until early 2011.)
  • Robust native development environment: The Android NDK (r5 or higher) provides a complete set of tools, toolchains, and libraries for developing applications that use the rich native environment offered by the Android 2.3 platform.
  • Internet telephony: Developers can now add SIP-based internet telephony features to their apps. Android 2.3 includes a full SIP protocol stack and integrated call management services that let applications easily set up outgoing and incoming voice calls, without having to manage sessions, transport-level communication, or audio record or playback directly.
  • Near Field Communications (NFC): The platform’s support for Near Field Communications (NFC) lets developers get started creating a whole new class of applications for Android. Developers can create new applications that offer proximity-based information and services to users, organizations, merchants, and advertisers. Using the NFC API, applications can respond to NFC tags “discovered” as the user “touches” an NFC-enabled device to elements embedded in stickers, smart posters, and even other devices. When a tag of interest is collected, applications can respond to the tag, read messages from it, and then store the messages, prompting the user as needed.

Source Readwriteweb..com
Source Developer.android.com

Leave a Reply


captcha *

This site uses Akismet to reduce spam. Learn how your comment data is processed.