Android Bluetooth widgets

BlueTap

In development · paused
Period
Sep 2026 – present
Ownership
Personal project · RSX Develops
Licence
MIT
Illustration
EarbudsAlready paired · assigned

Tap to connect: not built yet

IllustrationIllustration, not a screenshot: assigning and styling work; tap to connect is not built

Earbuds Outline style home-screen widget, 2 × 1 assign, customise tap to connect: not yet already paired public APIs only
IllustrationAssigning and customising work. Tap to connect does not yet.

What it is

Home-screen widgets for already-paired Bluetooth devices. Device assignment, per-widget appearance and responsive widget layouts work. Development is paused with the pre-Android-17 foundation complete. Tapping a widget to connect or disconnect is the goal, and it is not implemented yet.

The longer-term aim is one-tap Bluetooth control from the home screen: a widget per paired device. The foundation for that, which covers devices, widgets, appearance and persistence, is built. The connection itself is not.

What works

  • Device assignment from the already-paired list, de-duplicated by address.
  • Per-widget appearance with a set of presets, independent configuration and previews.
  • Responsive exact-size layouts, including a two-by-two layout, aware of the system font scale.
  • Per-device custom artwork, kept in private storage and shared across that device's widgets.

Why it stops where it does

Connecting and disconnecting a device from a widget needs APIs that the public Android SDK does not offer before Android 17. BlueTap waits for them rather than reaching for hidden APIs, reflection, root or accessibility services, and the work will be verified on a real device before it ships.

The app currently targets API 36. Validating Android 17's public Bluetooth APIs on a real device is the next development phase.

Privacy

BlueTap asks only for the Bluetooth-connect permission. It does not request location, does not scan, has no network access or analytics, and keeps its settings and artwork out of cloud backup.

How it works

Devices

The already-paired device list from Android is the source of truth, de-duplicated by address, with a friendly name, alias or address shown in that order.

Widgets

Each widget is assigned one device and its own appearance, saved together.

Layouts

Exact-size responsive layouts from a small tile to a wide showcase, aware of the system font scale.

Artwork

Optional per-device artwork, stored privately and shared across that device's widgets.

Decisions

Public SDK only

No hidden APIs, reflection, root or accessibility services. Connect and disconnect wait for Android 17's public APIs, to be verified on a real device first.

Minimal permissions

Only the Bluetooth-connect permission: no location, no scanning, no network, no analytics.

Careful persistence

Widget settings survive launcher restores and are cleaned up when a widget is removed, without deleting artwork another widget still uses.

Where it stands

  • Connect and disconnect, live connection state and generic battery reporting are not implemented; they wait on Android 17's public APIs, to be verified on a real device first.
  • Tapping a widget currently opens its editor.
  • Pre-release: there is no published build.

Stack

  • Kotlin
  • Jetpack Glance
  • Android