First Beep · Commlink
· ~5 minBrowser-only round-trip. Encode a beep in the cloud, decode it in your browser. ~5 min, no install.
🎮 Playcenter
Quests, tutorials and games — explore freely. Sign in to track progress, earn badges and unlock the PvP Transponder games.
Tutorials that walk you through the Beeping platform. Complete them to unlock badges and the Transponder games.
Browser-only round-trip. Encode a beep in the cloud, decode it in your browser. ~5 min, no install.
Build beeping-core from source on your machine, decode the WAV with the CLI you just compiled. Become a Beeping engineer.
🚧 Coming soon
Pair two devices over sound — no Bluetooth, no WiFi, no manual codes. Unlocks the four Transponder games.
🚧 Coming soon
One end-to-end onboarding path per Beeping component. From your first beep in C++ to your first Apple TV app — every stack covered.
Clone beeping-core, build with CMake + Conan, encode + decode a 5-char payload from a 30-line main.cpp.
You'll be able to: You can synthesise and decode a beep entirely from C++.
Needs: C++20 compiler · CMake 3.25+ · Conan 2.x
Clone beepbox, build the HTTP server, POST a JSON payload to /v1/encode, play the returned WAV in your browser.
You'll be able to: You have a beepbox running locally and serving the encode endpoint.
Needs: C++20 compiler · CMake 3.25+ · Beeping API key (free tier)
Add beeping-android via Maven Central; encode + decode a payload in a one-screen Kotlin sample.
You'll be able to: You have a Kotlin app that emits a beep on tap and decodes from the mic.
Needs: Android Studio 8.5+ · Kotlin 2.0+ · Android device or emulator
Add beeping-ios via Swift Package Manager; encode + decode in a SwiftUI sample running on simulator or device.
You'll be able to: You have a Swift app that emits and decodes a beep with one button.
Needs: Xcode 16+ · Swift 6 · iOS 17+ device or simulator
Drop beeping-web's WASM build into a static page; encode and decode entirely in the browser, no server.
You'll be able to: You have an index.html that emits and decodes beeps with zero network.
Needs: A modern browser (Web Audio API) · Any static file host
Add the beeping-flutter plugin to a fresh `flutter create` app; encode + decode runs identically on Android + iOS.
You'll be able to: You have a Flutter app that beeps on both platforms from a single codebase.
Needs: Flutter 3.x · Android Studio / Xcode · One device per OS
Bootstrap an Expo / RN app, add the beeping-react-native bridge, encode + decode in a JSX screen.
You'll be able to: You have an RN app that round-trips a beep using the JS bridge.
Needs: Node 20+ · Expo CLI or RN CLI · Xcode / Android Studio
`npm install beeping`, write a 10-line Node script that emits a beep through your laptop speaker.
You'll be able to: You have a Node CLI script that beeps any text on demand.
Needs: Node 20+ · A speaker / headphones
`pip install beeping`, decode a sample WAV in 5 lines, then loop on a mic stream.
You'll be able to: You have a Python script that detects beeps from the mic in real time.
Needs: Python 3.11+ · pip · Working mic
Install the Rust `beeping` CLI via Homebrew / cargo / scoop. Encode + decode from your terminal.
You'll be able to: You can `beeping encode --key abcde --mode audible | beeping decode -` and see the round-trip.
Needs: Homebrew / cargo / scoop · A terminal
Bootstrap an Apple TV (tvOS) and Android TV sample. Emit a beep on screen-on, decode on a paired phone.
You'll be able to: You have a TV app that signals nearby phones with a single ultrasonic beep.
Needs: Xcode (tvOS) or Android Studio (Android TV) · TV device or simulator
Add Beeping to a Chromecast / smart-speaker sample. The speaker emits, your phone decodes the deep-link.
You'll be able to: You have a Cast receiver that beeps a payload to whoever is in the room.
Needs: Cast SDK / smart speaker dev kit · One phone in earshot
150 ideas across 7 categories. Every game shows its level + which Beeping component it's built on.
Pure beeping-core — audio engine, modes, scheduler. Browser-only, no SDK required.
Hear a beep and decide: audible or ultrasonic? Sharpen your ear for the modes Beeping speaks in.
Showcases the audible / inaudible / custom mode flag in beeping-core.
Drag your finger across a canvas; pitch follows your y-axis, duration follows x. Hear what you paint.
Lays bare the core's frequency synthesis — turn gesture into tone in real time.
Three bands play in random order. Which was the inaudible one? Train your ear without seeing.
Highlights the audible-vs-ultrasonic boundary the core operates around.
A bingo card with frequency bands. Beeps play randomly; mark cells until you have a line.
Probability + identification — fast feedback for the modes you just learned.
Memorise a pitch from a 1-second beep, then sing/beep it back. Core compares your frequency to the source.
Tests pitch perception — a frequency-recall game powered by core's analysis.
Two beeps play back-to-back at almost-identical frequencies. Same or different?
Trains discrimination of small frequency deltas — the core's resolution in action.
Schedule N beeps over a fixed window and race to land them in the correct intervals.
Showcases the beeping-core scheduler — multi-beep timing without drift.
A pattern repeats with one beep swapped each time. Spot the change before the next loop.
Demonstrates deterministic playback — same scheduler, repeatable output.
Compose a 6-step sequence mixing audible + inaudible + custom modes. Play it and decode.
Composes mode flags into one round so users feel the full mode surface.
Slide a continuous tone up and down across the audible band. Hit the target frequencies as they appear.
Real-time pitch control — the core treated as a controllable oscillator.
Encode a message using only the GAPS between beeps. Silence carries the payload.
Time-domain encoding — payload by timing, not pitch.
Compose a short tune with beeps. Each beep is a note; arrange duration + pitch into something musical.
Sequencing UI on top of the core — explore composition with the engine.
Payload hidden in volume swells — louder = 1, quieter = 0. Decode the binary by listening.
Amplitude-domain encoding — different axis of payload from frequency or timing.
A normal pop song plays. Detect the hidden ultrasonic beep slipped inside it.
Steganography flavour — the core's ultrasonic mode hidden in audible noise.
Decode 3 simultaneous tones layered into one beep. Core's FFT must separate them in real time.
Stresses the core's spectral resolution — multi-tone decoding with overlap.
Design your own encoding scheme inside the core's API. Verify round-trip with sample payloads.
Power-user surface — write a `mode=3` config, test on the core's reference decoder.
Inject noise into the channel; watch BER curves shift as you slide the noise amplitude.
Quantifies the core's robustness — a microscope on the protocol's tolerances.
🍪 We use cookies to sign you in and to understand how Beeping is used. Read our Privacy Policy for details.