Wear Widgets logo

Wear Widgets

OrganizationPopular
android
wear-widgets

Create, migrate, update, and verify Wear OS widgets using Glance Wear and Remote Compose in an Android project. Use this skill when implementing GlanceWearWidget, GlanceWearWidgetService, WearWidgetDocument, Remote Compose UI primitives (RemoteColumn, RemoteRow, RemoteBox, RemoteText, RemoteImage, RemoteButton), local state with rememberMutableRemoteInt and valueChange, click actions with pendingIntentAction, widget provider XML containers (SMALL and LARGE), rectangular widget picker PNG previews, or migrating legacy ProtoLayout TileService tiles to Wear OS widgets. Don't use for mobile home screen AppWidgetProvider or GlanceAppWidget implementations, watch face complications, or full-screen Wear OS activities.

Overview

Publisherandroid
Repositoryskills
Skill namewear-widgets
Stars
10K
Forks
654
Bundled files
4
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by android on GitHub. Read the source before you install it.

Installation

Install the Wear Widgets AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/android/skills/tree/main/wear/wear-widgets
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/android/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/wear/wear-widgets .claude/skills/wear-widgets
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wear Widgets in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Wear Widgets on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Wear Widgets is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Wear OS widgets use androidx.glance.wear (GlanceWearWidget and GlanceWearWidgetService) with androidx.compose.remote (Remote Compose). They serialize declarative UI and state documents to the watch host process.

Prerequisites and setup

  1. Resolve library versions : Resolve the latest versions for {GLANCE_WEAR_VERSION} (androidx.glance.wear), {COMPOSE_REMOTE_VERSION} (androidx.compose.remote), and {WEAR_COMPOSE_REMOTE_VERSION} (androidx.wear.compose.remote). Include -alpha, -beta, or -rc releases when no stable version exists yet. Don't run ./gradlew dependencies to resolve versions:

  2. SDK and Compose compiler requirements : Ask permission before modifying repo-wide Gradle files unless the user requested widget creation, tile migration, or dependency setup. Set compileSdk = 37 or higher and enable buildFeatures { compose = true }. Keep the project's existing Android and Kotlin Gradle plugin declarations intact.

    dependencies { implementation("androidx.glance.wear:wear:{GLANCE_WEAR_VERSION}") implementation("androidx.glance.wear:wear-core:{GLANCE_WEAR_VERSION}") implementation("androidx.glance.wear:wear-tooling-preview:{GLANCE_WEAR_VERSION}") implementation("androidx.compose.remote:remote-creation-compose:{COMPOSE_REMOTE_VERSION}") implementation("androidx.compose.remote:remote-creation:{COMPOSE_REMOTE_VERSION}") implementation("androidx.compose.remote:remote-core:{COMPOSE_REMOTE_VERSION}") implementation("androidx.compose.remote:remote-tooling-preview:{COMPOSE_REMOTE_VERSION}") implementation("androidx.wear.compose.remote:remote-material3:{WEAR_COMPOSE_REMOTE_VERSION}") }

Codebase exploration

  1. Search the module for existing TileService, Material3TileService, or GlanceWearWidget implementations, <service> entries in app/src/main/AndroidManifest.xml, and @drawable/ preview assets under app/src/main/res/.
  2. When migrating an existing tile or modifying an unfamiliar multi-module project, run ./gradlew :app:assembleDebug to verify baseline build health.

Workflow

Step 1: Configure AndroidManifest.xml and provider XML

Register the GlanceWearWidgetService subclass in app/src/main/AndroidManifest.xml with the BIND_TILE_PROVIDER permission and BIND_WIDGET_PROVIDER intent action. Attach <meta-data> pointing to an @xml/ <wearwidget-provider> resource with SMALL and LARGE <container> entries. When configuring the service, provider XML, or legacy TileService migration, you MUST follow Widget service and manifest reference.

xml
<service
    android:name=".snippets.widget.skill.MyWidgetService"
    android:exported="true"
    android:permission="com.google.android.wearable.permission.BIND_TILE_PROVIDER">
    <intent-filter>
        <action android:name="androidx.glance.wear.action.BIND_WIDGET_PROVIDER" />
    </intent-filter>
    <meta-data
        android:name="androidx.glance.wear.widget.provider"
        android:resource="@xml/my_widget_info" />
</service>

Step 2: Implement GlanceWearWidget and GlanceWearWidgetService

Extend GlanceWearWidget and override provideWidgetData returning WearWidgetDocument. Annotate the GlanceWearWidgetService subclass with @AssociateWithGlanceWearWidget for static provider resolution:

kotlin
// WRONG: Mobile GlanceAppWidget API (don't use on Wear OS)
class BrokenWidget : GlanceAppWidget() {
    override suspend fun provideGlance(context: Context, id: GlanceId) {}
}

// CORRECT: Wear OS GlanceWearWidget + GlanceWearWidgetService
@AssociateWithGlanceWearWidget(MyWidget::class)
class MyWidgetService : GlanceWearWidgetService() {
    override val widget: GlanceWearWidget = MyWidget()
}

class MyWidget : GlanceWearWidget() {
    override suspend fun provideWidgetData(
        context: Context,
        params: WearWidgetParams,
    ): WearWidgetData =
        WearWidgetDocument(
            background = WearWidgetBrush.color(Color(0xFF1C1B1F).rc)
        ) {
            MyWidgetContent(params = params)
        }
}

Step 3: Build Remote Compose layouts, state, and actions

Remote Compose evaluates UI and state inside the Wear OS host process rather than the app process. When building adaptive layouts or full-bleed backgrounds, you MUST follow Remote Compose layouts reference. When implementing state or click actions, you MUST follow State and actions reference.

  • Remote value wrappers : Convert primitives using .rs (RemoteString), .rc (RemoteColor), .rdp (RemoteDp), and .ri (RemoteInt). Format integers with the RemoteInt.toRemoteString member method.
  • Adaptive container sizing : Branch layout density, typography, and item counts on params.containerType (ContainerInfo.CONTAINER_TYPE_SMALL versus ContainerInfo.CONTAINER_TYPE_LARGE).
  • Unmasked full-bleed backgrounds : Render background bitmaps inside a root RemoteBox (RemoteModifier.fillMaxSize) using RemoteImage and RemoteImageBitmap (bitmap.asImageBitmap). Keep background artwork unmasked (cornerRadius = 0dp) without CircleShape or RoundedCornerShape clipping. The host clips edges to the watch shape.
  • Declarative host state and PendingIntent actions : Mutate local widget state with rememberMutableRemoteInt and valueChange(state, newValue) instead of in-memory Compose state (mutableStateOf or mutableIntStateOf). Trigger activity launches or background broadcasts using pendingIntentAction { ctx -> ... } (always passing a (Context) -> PendingIntent lambda). Refresh active widgets with widget.triggerUpdateAll(context).

Step 4: Add WearWidgetPreview functions and picker preview PNGs

  1. Composable border previews (androidx.glance.wear.tooling.preview) : Import WearWidgetPreview, SquircleAllWidgetPreviewParams, RoundAllWidgetPreviewParams, and RectangularAllWidgetPreviewParams from androidx.glance.wear.tooling.preview (NEVER androidx.glance.wear.testing). Define @Preview functions invoking WearWidgetPreview(widget, params).
  2. Rectangular picker PNGs (res/drawable-nodpi/) : Use RectangularAllWidgetPreviewParams at 320 dpi or render non-blank, unmasked rectangular PNGs for every <container> in the provider XML:
    • SMALL (CONTAINER_TYPE_SMALL): 448x168 px (224x84 dp at 320 dpi, aspect ratio 2.67).
    • LARGE (CONTAINER_TYPE_LARGE): 464x288 px (232x144 dp at 320 dpi, aspect ratio 1.61).
    • Each preview PNG MUST depict the widget's actual UI elements, including backgrounds, text labels, icons, avatar initials, and buttons. NEVER use a blank placeholder, empty unlabeled shapes, or a 1:1 tile preview. When adding composable previews, picker PNGs, or unit tests, you MUST follow Previews and testing reference.

Component mapping

Use this sample table to load complete implementation patterns and imports:

Capability or API surfaceReference guide
GlanceWearWidget, GlanceWearWidgetService, AndroidManifest.xml, <wearwidget-provider>, legacy TileService migrationWidget service and manifest reference
RemoteBox, RemoteColumn, RemoteRow, RemoteText, RemoteImage, ContainerInfo (SMALL and LARGE adaptive layouts)Remote Compose layouts reference
RemoteButton, rememberMutableRemoteInt, valueChange, pendingIntentAction, BroadcastReceiver, triggerUpdateAllState and actions reference
WearWidgetPreview, SquircleAllWidgetPreviewParams, RoundAllWidgetPreviewParams, RectangularAllWidgetPreviewParams, picker PNGs, captureRawContent testsPreviews and testing reference

Legacy ProtoLayout and mobile Glance equivalents

Legacy or mobile APIWear OS widget APIAction to take
androidx.wear.tiles.TileServiceGlanceWearWidgetService + GlanceWearWidgetReplace service and annotate with @AssociateWithGlanceWearWidget.
GlanceAppWidget / provideGlanceGlanceWearWidget / provideWidgetDataReturn WearWidgetDocument from provideWidgetData.
LayoutElementBuilders / primaryLayoutRemoteColumn, RemoteRow, RemoteBoxBuild layouts with @RemoteComposable functions.
mutableStateOf / mutableIntStateOfrememberMutableRemoteInt + valueChangeMutate remote state declaratively using valueChange.
ModifiersBuilders.ClickableRemoteModifier.clickable(pendingIntentAction { ... })Pass a (Context) -> PendingIntent lambda to pendingIntentAction.

Troubleshooting

SymptomCauseFix
Unresolved reference GlanceWearWidgetMissing androidx.glance.wear:wear:{GLANCE_WEAR_VERSION} or low compileSdkSet compileSdk = 37 and add androidx.glance.wear:wear:{GLANCE_WEAR_VERSION}.
Unresolved reference toRemoteStringImported toRemoteString as top-level extensionRemove the import; call remoteInt.toRemoteString as a member method.
Type mismatch on pendingIntentActionPassed bare PendingIntent instead of lambdaWrap in a lambda: pendingIntentAction { ctx -> pendingIntent }.
Unresolved wear.tiles or protolayout references after migrationOther classes or source sets in the module still use legacy tile APIsMigrate or update the remaining references before removing legacy wear.tiles and protolayout dependencies from build.gradle.kts.

Verification

  1. Run ./gradlew :app:assembleDebug to verify that the widget, service, AndroidManifest.xml declarations, and @xml/ <wearwidget-provider> resources compile and link without errors.
  2. If the project includes unit tests or new widget tests, run ./gradlew :app:testDebugUnitTest and confirm all tests pass. When adding composable previews, picker PNGs, or unit tests, you MUST follow Previews and testing reference.

Antipatterns

  • NEVER extend mobile GlanceAppWidget or AppWidgetProvider, or use deprecated GlanceTileService or TileService for Wear OS widgets.
  • NEVER use in-memory client Compose state (mutableStateOf, mutableIntStateOf) or in-process click lambdas for Remote Compose UI.
  • NEVER pass a bare PendingIntent instance to pendingIntentAction; always pass a (Context) -> PendingIntent lambda.
  • NEVER apply CircleShape or RoundedCornerShape clipping to full-bleed widget background artwork. NEVER reuse 1:1 (400x400) tile previews or blank solid-color placeholders for widget picker PNGs.

Best practices

  • MUST declare com.google.android.wearable.permission.BIND_TILE_PROVIDER and androidx.glance.wear.action.BIND_WIDGET_PROVIDER on <service>.
  • MUST declare SMALL and LARGE <container> entries in @xml/ with domain-accurate 448x168 and 464x288 PNGs in res/drawable-nodpi/.
  • MUST adapt layout content to params.containerType and include @Preview functions for both SquircleAllWidgetPreviewParams and RoundAllWidgetPreviewParams.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Wear Widgets AI skill do?

Create, migrate, update, and verify Wear OS widgets using Glance Wear and Remote Compose in an Android project. Use this skill when implementing GlanceWearWidget, GlanceWearWidgetService, WearWidgetDocument, Remote Compose UI primitives (RemoteColumn, RemoteRow, RemoteBox, RemoteText, RemoteImage, RemoteButton), local state with rememberMutableRemoteInt and valueChange, click actions with pendingIntentAction, widget provider XML containers (SMALL and LARGE), rectangular widget picker PNG previews, or migrating legacy ProtoLayout TileService tiles to Wear OS widgets. Don't use for mobile hom...

Why use Wear Widgets on TypingMind?

Because you install it once and use it with any model. Wear Widgets is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Wear Widgets in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/android/skills/tree/main/wear/wear-widgets. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Wear Widgets?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Wear Widgets?

As many as you like. As long as a model supports skills, you can use Wear Widgets with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Wear Widgets AI skill free?

Yes. It is published on GitHub by android under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇