Package com.launchdarkly.sdk.android.subsystems

package com.launchdarkly.sdk.android.subsystems

Interfaces for implementation of LaunchDarkly SDK components.

Most applications will not need to refer to these types. You will use them if you are creating a plugin component, such as a database integration. They are also used as interfaces for the built-in SDK components, so that plugin components can be used interchangeably with those.

The package also includes concrete types that are used as parameters within these interfaces.

Related Packages

Package	Description
com.launchdarkly.sdk.android	Main package for the LaunchDarkly Android SDK, containing the client and configuration classes.
com.launchdarkly.sdk.android.env
com.launchdarkly.sdk.android.integrations	This package contains integration tools for connecting the SDK to other software components, or configuring how it connects to LaunchDarkly.
com.launchdarkly.sdk.android.interfaces	Types that are part of the public API, but are not needed for basic use of the SDK.
com.launchdarkly.sdk.android.test

Class	Description
ApplicationInfo	Encapsulates the SDK's application metadata.
Callback<T>	General-purpose interface for callbacks that can succeed or fail.
ClientContext	Configuration information provided by the LDClient when creating components.
ComponentConfigurer<T>	The common interface for SDK component factories and configuration builders.
DataSource	Interface for an object that receives updates to feature flags from LaunchDarkly.
DataSourceUpdateSink	Interface that an implementation of DataSource will use to push data into the SDK.
DiagnosticDescription	Optional interface for components to describe their own configuration.
EventProcessor	Interface for an object that can send or store analytics events.
HttpConfiguration	Encapsulates top-level HTTP configuration that applies to all SDK components.
PersistentDataStore	Interface for a data store that holds feature flag data and other SDK properties in a simple string format.