Open-source SDKs for ultrasonic data exchange between nearby devices. No Bluetooth, no WiFi, no pairing.
5-minute browser quest · no install · sign in to start
Beeping isn't new — it's back. Founded in 2015, paused in 2018, and reborn in 2026 — same idea, better hardware, open-source from day one.
Beeping starts — making data travel through sound.
The original team scatters. The idea stays parked.
Open-source, multi-stack, back for the new era.
Three simple steps. No hardware, no pairing, no setup.
Turn any data payload into an audio signal — audible or ultrasonic.
The encoded signal travels through the air via the device speaker. No network needed.
A nearby device picks up the audio with its microphone and extracts the original data.
Five lenses on what Beeping enables — pick the one you care about.
Every SDK supports both modes. Switch at runtime with one line.
Any scenario where two devices need to exchange small data payloads nearby.
Share links, contacts, or tickets with people nearby — just play a sound.
Pair devices instantly by playing a short audio handshake. Works with any speaker.
Configure smart devices by sending Wi-Fi credentials or setup data over sound. No app pairing flow.
Push interactive content to every phone in the venue simultaneously via the PA system.
One protocol, every runtime. Same simple API across native SDKs, web packages, server-side bindings and the HTTP layer.
Mobile
Dart plugin
One Dart codebase, both stores. Federated plugin wrapping the native Android + iOS SDKs underneath.
Nitro Modules
RN apps with the same API as the native SDKs. Nitro Modules under the hood — no TurboModule legacy.
Swift Package
Same API for iOS and iPadOS — actor-based Swift 6 client with PrivacyInfo.xcprivacy and AsyncStream events.
Kotlin SDK
Emit and listen for ultrasonic data inside any Android app. Coroutine-friendly API, dual mode (on-device or cloud).
Browser
@beeping/react
Hooks like useBeepingListen / useBeepingSend plus a <BeepingProvider> over the WASM core. Web Audio + AudioWorklet.
@beeping/vue
Vue 3 composables backed by the same WASM core. Reactive payload streams, no setup ceremony.
@beeping/svelte
Svelte 5 runes + stores wrapping the WASM core. Drop into any SvelteKit route.
@beeping/vanilla
Zero-deps wrapper for any browser app or framework we don't ship a binding for yet. Just the WASM core, exposed cleanly.
Server
beepbox-server (REST)
Any language, any runtime — call the beepbox REST API directly. OpenAPI 3.1 spec ships generated clients for the common stacks.
@beeping/node
Server-side encoding via the beepbox HTTP API or a native N-API binding to the C++ core. Express / Fastify / Nest sample apps.
beeping (PyPI)
Async Python client (httpx) for the cloud mode plus a pybind11 native binding for offline encoding. Type-checked with mypy strict.
Terminal
beeping-core library
The C++20 library every other binding wraps. For embedded targets or custom integrations where you want zero glue.
beeping-cli (Rust)
Encode / decode / inspect from your terminal. Cross-compiled binaries via Homebrew, Scoop, cargo install or GitHub Releases.
End-user example apps coming to every device — from your phone to the TV in your living room.
Phones & tablets
Beepster Flutter / RN
Native iPhone + iPad app. Tap to join a session, hear the beep, see the payload — works fully offline.
Beepster Flutter / RN
Native Android phone + tablet app. Same flow as iOS, distributed via Google Play.
Desktop
Beepster Web (any browser)
Open beepster.beeping.io in Safari, Chrome or Arc — host or join a session straight from your laptop.
Beepster Web (any browser)
Same web app, runs in Edge, Chrome, Firefox. No install, mic-permission only when you join.
Beepster Web (any browser)
Beepster Web runs everywhere a modern browser runs — Firefox, Chromium, Brave on any distro.
TV
Beepster tvOS
Big-screen host: lobby with QR + code, leaderboard, soundbar emits the beep. Players join from their phones.
Beepster Android TV
Same big-screen host pattern as Apple TV, distributed via the Google Play Store TV section.
Beepster Fire TV
Amazon Fire TV stick + Fire TV Cube. Host games on your living room TV, players join from phones.
Voice
Beepster Cast
Co-host audio amplifier — your phone or TV runs the host, HomePod amplifies the beep across the room via AirPlay.
Beepster Cast
Nest Mini, Nest Hub and Chromecast targets. Host on your phone, cast the beep across every Nest in the house.
Beepster Cast
Alexa skill that turns any Echo into an extra room speaker for the host's beep. Works alongside Fire TV.
Every piece of the Beeping system, how it fits, and what it does. Read top-down: foundation → apps → SDKs → surfaces.
Foundation
The audio protocol itself, plus its cloud entry point.
core
Pure C++20 audio engine — encodes payloads into audible / ultrasonic tones and decodes them back.
Where it fits: The foundation every other component is built on. No I/O, no network — just synthesis + analysis.
beepbox
HTTP server wrapping beeping-core. POST a payload → get a WAV; POST audio → get a payload back.
Where it fits: The cloud entry point — used when you can't or won't bundle the core locally.
Mobile + Web apps
In your users' pockets and browser tabs.
android
Kotlin SDK that bundles core via JNI. Mic capture + speaker playback + signal-strength scoring.
Where it fits: Drop-in for any Android app that needs to beep — pairing, broadcast, decoding.
ios
Swift SDK with the same surface as Android. Distributed via Swift Package Manager.
Where it fits: Drop-in for any iOS / iPadOS / tvOS app.
web
beeping-core compiled to WebAssembly. Encode + decode entirely in the browser tab.
Where it fits: Zero infra path — embed in a static page and run offline.
flutter
Flutter plugin wrapping the Android + iOS SDKs — one Dart codebase, both platforms.
Where it fits: Cross-platform mobile without writing native twice.
react-native
React Native bridge over the Android + iOS SDKs.
Where it fits: Drop into an Expo or bare RN app and call from JS.
Language SDKs
In your backend, scripts, and pipelines.
node
Node.js bindings — encode + decode from a server-side process or CLI tool.
Where it fits: Backends, scripts, anywhere npm reaches.
python
Python bindings + mic-capture loop for decoding ambient beeps in real time.
Where it fits: Data pipelines, research, audio analysis.
cli
Rust CLI for the terminal. `beeping encode --key abcde | beeping decode -`.
Where it fits: Quick one-liners + reproducible CI integrations.
Smart home
On the surfaces around the user.
tv
tvOS + Android TV SDK. The TV emits a beep on screen-on; nearby phones decode and deep-link.
Where it fits: TVs as identity beacons for the household.
speaker
Cast + smart-speaker integration. Speakers announce themselves to phones in earshot.
Where it fits: The simplest way to broadcast a deep-link to a roomful of devices.
The reference app for Beeping
Send a contact card, share a link, beam payment info — all over sound. Open-source Flutter app showing Beeping in production.
🍪 We use cookies to sign you in and to understand how Beeping is used. Read our Privacy Policy for details.