0601app_widget_host_android_developers_cropped.pdfVIP

App Widget Host | Android Developers In this document 1. Binding App Widgets 1. Binding app widgets on Android 4.0 and lower 2. Binding app widgets on Android 4.1 and higher 2. Host Responsibilities 1. Android 3.0 2. Android 3.1 3. Android 4.0 4. Android 4.1 5. Android 4.2 The Android Home screen available on most Android devices allows the user to embed app widgets for quick access to content. If youre building a Home replacement or a similar app, you can also allow the user to embed app widgets by implementing an AppWidgetHost. This is not something that most apps will ever need to do, but if you are creating your own host, its important to understand the contractual obligations a host implicitly agrees to. This document focuses on the responsibilities involved in implementing a custom AppWidgetHost. For an example of how to implement an AppWidgetHost, see the source code for the Android Home screen Launcher. Here is an overview of key classes and concepts involved in implementing a custom AppWidgetHost: App Widget Host— The AppWidgetHost provides the interaction with the AppWidget service for apps, like the home screen, that want to embed app widgets in their UI. An AppWidgetHost must have an ID that is unique within the hosts own package. This ID remains persistent across all uses of the host. The ID is typically a hard-coded value that you assign in your application. App Widget ID— Each app widget instance is assigned a unique ID at the time of binding (see bindAppWidgetIdIfAllowed(), discussed in more detail in Binding app widgets). The unique ID is obtained by the host using allocateAppWidgetId(). This ID is persistent across the lifetime of the widget, that is, until it is deleted from the host. Any host-s