SDK features
What each SDK can do, side by side: where it evaluates, whether it gets changes in real time, what it falls back on offline, whether it reports outcomes, and how far it has been verified.
Client-side and mobile SDKs#
Client SDKs take a client key. The server evaluates targeting for one person and sends back only the result, so no rules or other people's data reach the device.
| SDK | Key | Real-time updates | Works offline from | Outcome analytics | Verified |
|---|---|---|---|---|---|
| JavaScript | Key:Client key (fs_client_) | Real-time updates:Yes | Works offline from:localStorage cache | Outcome analytics:Yes | Verified:Tested against shared vectors |
| React | Key:Client key (fs_client_) | Real-time updates:Yes | Works offline from:localStorage cache | Outcome analytics:Yes | Verified:Unit tests |
| React Native | Key:Client key (fs_client_) | Real-time updates:No, it polls | Works offline from:Storage adapter (AsyncStorage) | Outcome analytics:Yes | Verified:Unit tests |
| Vue | Key:Client key (fs_client_) | Real-time updates:Yes | Works offline from:localStorage cache | Outcome analytics:Yes | Verified:Unit tests |
| Flutter | Key:Client key (fs_client_) | Real-time updates:No, it polls | Works offline from:Storage adapter (SharedPreferences) | Outcome analytics:Yes | Verified:Not yet compiled |
| Swift | Key:Client key (fs_client_) | Real-time updates:No, it polls | Works offline from:UserDefaults | Outcome analytics:Yes | Verified:Not yet compiled |
Server-side SDKs#
Server SDKs take a server key, download the environment's configuration and evaluate it in memory, so a flag check is a local call with no network round trip.
| SDK | Key | Real-time updates | Works offline from | Outcome analytics | Verified |
|---|---|---|---|---|---|
| Next.js | Key:Server key; client entry takes a client key | Real-time updates:Client entry only | Works offline from:In memory per process | Outcome analytics:Yes | Verified:Unit tests |
| Node.js | Key:Server key (fs_srv_) | Real-time updates:Yes | Works offline from:Snapshot file | Outcome analytics:Yes | Verified:Tested against shared vectors |
| NestJS | Key:Server key (fs_srv_) | Real-time updates:Yes | Works offline from:Snapshot file | Outcome analytics:Yes | Verified:Unit tests |
| Go | Key:Server key (fs_srv_) | Real-time updates:Yes | Works offline from:Snapshot file | Outcome analytics:Yes | Verified:Tested against shared vectors |
| Python | Key:Server key (fs_srv_) | Real-time updates:Yes | Works offline from:Snapshot file | Outcome analytics:Yes | Verified:Tested against shared vectors |
| PHP | Key:Server key (fs_srv_) | Real-time updates:No, it polls | Works offline from:Shared config store | Outcome analytics:Yes | Verified:Tested against shared vectors |
| Laravel | Key:Server key (fs_srv_) | Real-time updates:No, it polls | Works offline from:Your Laravel cache | Outcome analytics:Yes | Verified:Tested against stand-ins for Laravel only |
| Java | Key:Server key (fs_srv_) | Real-time updates:Yes | Works offline from:Snapshot file | Outcome analytics:Yes | Verified:javac and JUnit only, no real Maven build |
| .NET | Key:Server key (fs_srv_) | Real-time updates:No, it polls | Works offline from:Snapshot file | Outcome analytics:Yes | Verified:Not yet compiled |
Next.js uses both
Server code reads the configuration with a server key. Its client entry takes a client key and is the part that can open a real-time stream.
What the columns mean#
- Real-time updates. With
streaming: truea change reaches the SDK in about a second. Without it, or where an SDK cannot read a stream, it polls (every 30 seconds by default). Details are under Real-time updates. - Works offline from. What keeps the last good data so a restart works while the server is down. A start with nothing saved serves your fallbacks until the server is reachable. See Offline and outages.
- Outcome analytics. The
trackExposureandtrackhelpers. Nothing is sent unless you call them or turn onautoExposures, and the server must run with analytics enabled. See Outcome analytics. - Verified. Said plainly. “Tested against shared vectors” means the SDK ran the same evaluation test cases as the server. “Not yet compiled” means it was written without its toolchain: run its tests before you depend on it.
Behaviour every SDK shares#
- Options every SDK takes: key, address, environment, refresh interval, fallbacks and callbacks.
- Describing a person: identifiers, accounts, devices and attributes.
- What an evaluation returns: on or off, the variant, its value and the reason.
- How they behave when things go wrong: retries, backoff and errors that never reach your code.