OSS TanbouSign in with GitHub

fill common Wear OS gaps with libraries for media, volume, pickers, DataLayer, and more

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
699
Primary language
Kotlin
License
Apache-2.0
Repository last updated
Oct 4, 2026
On this page

Overview

Horologist is a set of Google libraries that supplements Wear OS development. Its modules cover media playback, audio and output control, date/time pickers, Compose layout, authentication, DataLayer helpers, Tiles, and related Wear-specific needs.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Build Wear OS media playback, volume, and output controls from reusable modules

The Media Toolkit separates domain, Media3 data/backend, player and browse UI, and audio/output modules so Wear-specific routing and playback screens do not need to be rebuilt from scratch.

Sources: [2]

Add pickers, layout, authentication, DataLayer, and Tile helpers as needed

Horologist provides date/time pickers, Wear-aware Compose layout, authentication UI and data helpers, phone/watch DataLayer utilities, and coroutine-oriented TileService support in separate modules.

Sources: [2]

Best fit

Fits Wear OS applications that want to focus on product behavior instead of platform glue

Media apps, fitness companions, and phone-connected Wear apps can layer Horologist on AndroidX for common device-specific patterns and UI.

Sources: [2]

Before adoption

Choose deliberately between the stable 0.7.x line and 0.8.x alpha line

Horologist 0.7.15 documents Wear minSdk 26, Kotlin 2.1.20/JDK 17, and generally stable AndroidX. The current 0.8.x line consumes newer Wear Compose and AndroidX alphas and main may change APIs, so production applications should pin the intended line.

Sources: [2][4][5]

Official sources

  1. [1]google/horologist — GitHub repository(2026-10-06)
  2. [2]Horologist 0.7.15 — README(2026-10-06)
  3. [3]Horologist 0.7.15 release(2026-10-06)
  4. [4]Horologist 0.8.4-alpha — README(2026-10-06)
  5. [5]Horologist 0.8.4-alpha release(2026-10-06)
  6. [6]Horologist Apache-2.0 license(2026-10-06)
Supplemental curator note

Horologist reduces the amount of Wear OS-specific media, volume, UI, and phone-integration code teams build themselves. The maintained 0.7.x line follows stable AndroidX while 0.8.x consumes newer Wear Compose and AndroidX alphas, so production apps should choose the line deliberately.

Try it in 3 steps

  1. 1

    Add Horologist Composables 0.7.15

    Pin the maintained 0.7.x line that tracks stable AndroidX. The Wear OS minimum SDK is 26.

    implementation("com.google.android.horologist:horologist-composables:0.7.15")
  2. 2

    Import the Wear DatePicker

    Import DatePicker from the Horologist composables module and LocalDate for an initial value.

    import com.google.android.horologist.composables.DatePicker import java.time.LocalDate
  3. 3

    Render DatePicker in Compose

    Use the same API as the official sample and confirm that the selected date is returned.

    DatePicker( onDateConfirm = { date -> println(date) }, date = LocalDate.of(2026, 10, 6), )
Check the official README

Growth

Growth trends · Last 30 days

699 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
35
Open PRs
5

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • wear-os
  • compose
  • media3
Stars
699
Forks
123
Watchers
15
Open issues
10
Contributors
55
Owner type
Organization
Primary language
Kotlin
License
Apache-2.0
Repository last updated
Oct 4, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?