Skip to content
FlagSwiftDocs

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.

Features of the client-side and mobile SDKs
SDKKeyReal-time updatesWorks offline fromOutcome analyticsVerified
JavaScriptKey:Client key (fs_client_)Real-time updates:YesWorks offline from:localStorage cacheOutcome analytics:YesVerified:Tested against shared vectors
ReactKey:Client key (fs_client_)Real-time updates:YesWorks offline from:localStorage cacheOutcome analytics:YesVerified:Unit tests
React NativeKey:Client key (fs_client_)Real-time updates:No, it pollsWorks offline from:Storage adapter (AsyncStorage)Outcome analytics:YesVerified:Unit tests
VueKey:Client key (fs_client_)Real-time updates:YesWorks offline from:localStorage cacheOutcome analytics:YesVerified:Unit tests
FlutterKey:Client key (fs_client_)Real-time updates:No, it pollsWorks offline from:Storage adapter (SharedPreferences)Outcome analytics:YesVerified:Not yet compiled
SwiftKey:Client key (fs_client_)Real-time updates:No, it pollsWorks offline from:UserDefaultsOutcome analytics:YesVerified: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.

Features of the server-side SDKs
SDKKeyReal-time updatesWorks offline fromOutcome analyticsVerified
Next.jsKey:Server key; client entry takes a client keyReal-time updates:Client entry onlyWorks offline from:In memory per processOutcome analytics:YesVerified:Unit tests
Node.jsKey:Server key (fs_srv_)Real-time updates:YesWorks offline from:Snapshot fileOutcome analytics:YesVerified:Tested against shared vectors
NestJSKey:Server key (fs_srv_)Real-time updates:YesWorks offline from:Snapshot fileOutcome analytics:YesVerified:Unit tests
GoKey:Server key (fs_srv_)Real-time updates:YesWorks offline from:Snapshot fileOutcome analytics:YesVerified:Tested against shared vectors
PythonKey:Server key (fs_srv_)Real-time updates:YesWorks offline from:Snapshot fileOutcome analytics:YesVerified:Tested against shared vectors
PHPKey:Server key (fs_srv_)Real-time updates:No, it pollsWorks offline from:Shared config storeOutcome analytics:YesVerified:Tested against shared vectors
LaravelKey:Server key (fs_srv_)Real-time updates:No, it pollsWorks offline from:Your Laravel cacheOutcome analytics:YesVerified:Tested against stand-ins for Laravel only
JavaKey:Server key (fs_srv_)Real-time updates:YesWorks offline from:Snapshot fileOutcome analytics:YesVerified:javac and JUnit only, no real Maven build
.NETKey:Server key (fs_srv_)Real-time updates:No, it pollsWorks offline from:Snapshot fileOutcome analytics:YesVerified: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: true a 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 trackExposure and track helpers. Nothing is sent unless you call them or turn on autoExposures, 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#