Boop

about

description

See a nearby person. Pop their bubble. They get Booped. Boop is a small, local-only native Android app. Translucent animated soap bubbles drift in a calm little field. Decorative bubbles pop only on your own phone; named bubbles represent real nearby people who opted in. Tap a person’s bubble to send a direct Bluetooth Low Energy Boop. Their phone posts a small notification, and they can reply with one of five emoji before meeting in person. • Procedural iridescent bubbles: grab, fling or stir empty space, with film-petal pops and quiet synthesized contacts. • A name and accent color, without profiles, accounts or a friend list. • Basic foreground discovery; optional Background Boops and Floating Boops are off by default. • Contextual Bluetooth/notification permissions; overlays require a separate explicit choice. • No Internet permission, trackers, analytics, ads, cloud, Google Play Services or proprietary backend. • Open documented Boop BLE Protocol v1; no pairing or bonding. • System/light/dark themes, accessible named bubbles and continuous motion independent of Android UI animation settings. Android 12+ and BLE advertising support required. Background discovery requires Android’s persistent service notification and can be interrupted by battery restrictions or force-stop. Floating bubbles never read another app or appear on the lock screen. Nearby names and identifiers are public radio information; messages are not encrypted or authenticated. This is a playful social Boop, not secure messaging.

publisher

78ce6faa72264387284e647ba6938995735ec8c7d5c5a65737e55130f026307d

first seen

2026-10-23T22:19:21.338434+00:00

last event

2026-10-13 22:50 UTC

install

zapstore.dev or any Zapstore-compatible client

topics

#casual game #party game

source & build

repository

https://gitlab.com/derpbiscuit/boop

arch flags

android-arm64-v8a

manifest

error

releases (kind 30063)

1 release indexed; latest android-v0.2.4.

assets & verification

Every app, release and asset event is schnorr-verified (NIP-01 id + signature) before it enters the catalog, and assets are content-addressed by sha256. We subscribe read-only to the catalog relay — never write to it.

Showing the newest 0 asset descriptors; the full set is in /api/apps/78ce6faa…