Beekon is a small, focused SDK for capturing where your users go — in the foreground, in the background, and after the app has been swiped away. It runs on the device, keeps a rolling history, and respects the battery. No servers to wire up. No surprises in production.
We build the Android and iOS libraries ourselves, in their native languages. Flutter and React Native get the same SDK through a thin language wrapper — same behaviour, same battery, same history. Pick whichever stack your team is on; we keep them in step.
The shape of the API is the same on every platform: one config object, one start call, and a stream of locations to listen to. The naming follows whatever feels natural in your language — Kotlin Flow on Android, AsyncStream on iOS, Streams in Dart, event listeners in TypeScript. Nothing exotic to learn.
{sample.lines.map((line, i) => (
{line.length === 0 ? <> : line.map((tok, j) => (
{tok[1]}
))}
))}
Pick how often you need a fix and how far apart points should be — those are the only two knobs. The presets cover the common cases, and you can override either value when you need to. The battery numbers below are measured on real phones running real builds, not estimated.
Most location SDKs cut a corner somewhere — a shared core that pretends to be native, a smoothing layer that hides what the phone actually saw, or a server you didn’t ask to depend on. Beekon doesn’t. These are the choices that make continuous tracking actually work in the wild.
Pay for the platforms you actually ship on. One license covers one app and unlimited builds, including every update we ship on the same major version. Bundle two or more and the price drops automatically.
The questions we get most often — and a few you should ask before picking any location SDK. If something here doesn’t match what you need, the Enterprise tier is where we get into the details.