Launch Darkly
Tested with Launch Darkly version 9.12.0 (iOS)
Using Appfigurate remote properties instead of Launch Darkly flag evaluation APIs directly allows for the following:
locally change Launch Darkly flags without affecting your entire customer base.
compile time type safety - Appfigurate remote properties are typed.
avoids hardcoding duplicated flag names throughout your app.
avoids hardcoding duplicated default values throughout your app.
deleting a flag from Launch Darkly Console won't affect existing apps, they'll continue to use the default value provided in the
resetmethod.
We assume you already have Appfigurate Library and Launch Darkly integrated into your app with the following example remote properties created in the Launch Darkly console:

Add remote properties into your Configuration subclass
Update your configuration subclass to include your remote configuration properties. Provide default values for the properties in the overridden reset method. See also Supported property types.
Swift Configuration example
Objective-C Configuration header example
Objective-C Configuration implementation example
Kotlin Configuration example
Java Configuration example
Provide remote configuration values to Appfigurate Library when requested
Appfigurate Library needs to be able to read the current remote flags from Launch Darkly. Copy and paste the following code into your app.
Swift example
Objective-C example
Kotlin example
Java example
Notify Appfigurate Library when Launch Darkly has received flags
We need to tell Appfigurate Library that Launch Darkly has received flags, so that it can keep your Configuration subclasses remote properties in sync.
Add a call to APLFlushRemoteConfiguration in any existing Launch Darkly start(config, startWaitSeconds, completion) and observeAll(owner, handler) blocks.
Swift example
Add a call to APLFlushRemoteConfiguration in any existing Launch Darkly startWithConfiguration:startWaitSeconds:completion: and observeAllKeysWithOwner:handler: blocks.
Objective-C example
The Android Launch Darkly SDK doesn't have functionality that notifies you of flags being received during the LDClient.init call. Instead we must programmatically check for a well known flag's evaluation detail, and then call Appfigurate.flushRemoteConfiguration as appropriate.
Add another call to Appfigurate.flushRemoteConfiguration in a Launch Darkly registerAllFlagsListener block.
Kotlin example
The Android Launch Darkly SDK doesn't have functionality that notifies you of flags being received during the LDClient.init call. Instead we must programmatically check for a well known flag's evaluation detail, and then call Appfigurate.flushRemoteConfiguration as appropriate.
Add another call to Appfigurate.flushRemoteConfiguration in a Launch Darkly registerAllFlagsListener block.
Java example
Complete initialisation example
Swift complete initialisation example
Objective-C complete initialisation example
Kotlin complete initilisation example
Java complete initialisation example
Best practice and usage
Replace all calls to Launch Darkly boolVariation(forKey:defaultValue:), intVariation(forKey:defaultValue:), doubleVariation(forKey:defaultValue), stringVariation(forKey:defaultValue:)
with the following:
Replace all calls to Launch Darkly boolVariationForKey:defaultValue:, intVariationForKey:defaultValue:, doubleVariationForKey:defaultValue, stringVariationForKey:defaultValue:
with the following:
Replace all calls to Launch Darkly boolVariation(), intVariation(), doubleVariation(), stringVariation()
with the following:
Replace all calls to Launch Darkly boolVariation(), intVariation(), doubleVariation(), stringVariation()
with the following:
Last updated