Flagbearer SDKs

Official SDKs for Flagbearer feature flags. Server SDKs download an environment's rules once and check flags locally, so a flag check never waits on the network. Docs for each are at docs.flagbearer.dev.

SDK	Directory	Package
Browser	js/web	@flagbearer/web (npm)
React Native	js/react-native	@flagbearer/react-native (npm)
iOS	swift	Swift Package Manager, from this repository
Android	android	dev.flagbearer:flagbearer-android (Maven Central)
Node.js	js/node	@flagbearer/node (npm)
Python	python	flagbearer-dev (PyPI)
Go	go	github.com/flagbearer-dev/sdks/go
Java and Kotlin	java	dev.flagbearer:flagbearer (Maven Central)
.NET	dotnet	Flagbearer (NuGet)
Ruby	ruby	flagbearer (RubyGems)
Rust	rust	flagbearer (crates.io)
C++	cpp	CMake, from a git tag
PHP	flagbearer-dev/php-sdk	flagbearer/flagbearer (Packagist)

The PHP SDK lives in its own repository, since Packagist publishes from a repository's root. Go, C++ and iOS install straight from this repository's tags. Swift Package Manager also reads a package only from a repository's root, which is why Package.swift sits here beside the code in swift/.

How the SDKs stay consistent

• fixtures/evaluation.json holds rollout buckets and evaluation cases that every SDK's tests must reproduce exactly.
• testing/servers/ has a small HTTP server per SDK with the same routes (GET /flags, GET /flush), which Flagbearer's integration tests run against the real backend.
• js/core and js/evaluator are internal packages the JavaScript SDKs bundle.

Each SDK's README covers how to build, test and release it.

License

MIT