mobile bitdrift SDK
38
stars
935
commits
Kotlin
primary language
Sep 10, 2026
updated
The bitdrift Capture SDK is a highly optimized, lightweight library built to enable high volume, low overhead local telemetry storage and persistence. Controlled in real-time by the bitdrift control plane, the SDK selectively uploads the precise data needed to debug customer issues, and nothing more.
See here for more information.
For setup, please refer to the wiki
Release builds do not use the Bazel/BuildBuddy remote cache. GitHub Actions caches used by a
release are scoped as release-${{ github.workflow }} and must not be shared with pull-request or
ordinary main builds. See AGENTS.md before changing release commands, workflows, or shared
setup actions.
This section uses just, a modern Make alternative. Install via brew install just.
Generate the Bazel-derived Rust crate graph after cloning and whenever Bazel or Rust dependency configuration changes:
just ra
This installs the Bazel-pinned Rust Analyzer tools under ignored local state, generates a root
rust-project.json, and configures VS Code to use them. The generated project includes test
targets and their development dependencies.
To limit indexing to local areas and their transitive Rust dependencies, select one or more paths. Each invocation replaces the previous local selection:
just select-ra platform/jvm/core
The command writes the ignored .rules_rust_analyzer/selection.json and runs the same setup as
just ra. To edit that selection directly, use this format:
{
"paths": [
"platform/shared",
"platform/crash"
]
}
To restore the full project, remove the ignored selection and run just ra:
rm .rules_rust_analyzer/selection.json
just ra
334 commits
137 commits
123 commits
112 commits
Kotlin
44.2%
Swift
26.9%
Rust
10.8%
TypeScript
5.1%
Starlark
3.0%
Objective-C
2.9%
Python
2.9%
Shell
2.7%
mobile bitdrift SDK
38
stars
935
commits
Kotlin
primary language
Sep 10, 2026
updated
The bitdrift Capture SDK is a highly optimized, lightweight library built to enable high volume, low overhead local telemetry storage and persistence. Controlled in real-time by the bitdrift control plane, the SDK selectively uploads the precise data needed to debug customer issues, and nothing more.
See here for more information.
For setup, please refer to the wiki
Release builds do not use the Bazel/BuildBuddy remote cache. GitHub Actions caches used by a
release are scoped as release-${{ github.workflow }} and must not be shared with pull-request or
ordinary main builds. See AGENTS.md before changing release commands, workflows, or shared
setup actions.
This section uses just, a modern Make alternative. Install via brew install just.
Generate the Bazel-derived Rust crate graph after cloning and whenever Bazel or Rust dependency configuration changes:
just ra
This installs the Bazel-pinned Rust Analyzer tools under ignored local state, generates a root
rust-project.json, and configures VS Code to use them. The generated project includes test
targets and their development dependencies.
To limit indexing to local areas and their transitive Rust dependencies, select one or more paths. Each invocation replaces the previous local selection:
just select-ra platform/jvm/core
The command writes the ignored .rules_rust_analyzer/selection.json and runs the same setup as
just ra. To edit that selection directly, use this format:
{
"paths": [
"platform/shared",
"platform/crash"
]
}
To restore the full project, remove the ignored selection and run just ra:
rm .rules_rust_analyzer/selection.json
just ra
334 commits
137 commits
123 commits
112 commits
Kotlin
44.2%
Swift
26.9%
Rust
10.8%
TypeScript
5.1%
Starlark
3.0%
Objective-C
2.9%
Python
2.9%
Shell
2.7%