Konfeature

Konfeature is a powerful Kotlin Multiplatform library for managing remote configuration in your applications. It provides a clean, declarative API for working with feature flags and configuration elements across Android, iOS, and JVM platforms.
Working with remote configuration has become a standard part of the development process for almost any application. Depending on the complexity of the application, several requirements for such functionality may arise, including:
- convenient syntax for declaring configuration elements
- the ability to separate configuration into different files for different features
- the ability to make the configuration local-only during active feature development
- support for multiple data sources for remote config
- the ability to view a list of all configurations and modify their values for debugging purposes
- logging the value and its source when accessing the configuration, as well as logging non-critical errors
We have made every effort to meet all these requirements in the development of Konfeature.
Supported Platforms
Konfeature is a Kotlin Multiplatform library with support for:
Installation
Add Maven Central Repository
repositories {
mavenCentral()
}
Add Dependency
For Gradle (Kotlin Multiplatform Project):
kotlin {
sourceSets {
commonMain.dependencies {
implementation("com.redmadrobot.konfeature:konfeature:<version>")
}
}
}
For Gradle (Single Platform):
dependencies {
implementation("com.redmadrobot.konfeature:konfeature:<version>")
}
Usage
FeatureConfig
Defines a set of configuration elements, where each element is defined using a delegate.
There are two types of delegates:
by toggle(...) - used for elements of type Boolean
by value(...) - used for elements of any other type
The configuration requires specifying:
name - the name of the configuration
description - a detailed description of the configuration
Each configuration element requires specifying:
key - used to retrieve the value of the element from a Source
description - a detailed description of the element
defaultValue - used if the value cannot be found in a
After that, you need to register the configuration in Konfeature:
val profileFeatureConfig: FeatureConfig = ProfileFeatureConfig()
val konfeatureInstance = konfeature {
register(profileFeatureConfig)
}
Similarly, you can add multiple configurations, for example, for each module, when organizing multi-modularity by features.
FeatureSource
An abstraction over the value source for configuration elements.
public interface FeatureSource {
public val name: String
public fun get(key: String): Any?
}
name - source name
get(key: String) - logic for getting values by key
Example implementation based on FirebaseRemoteConfig:
After that, you need to add the Source in Konfeature:
val profileFeatureConfig: FeatureConfig = ProfileFeatureConfig()
val source: FeatureSource = FirebaseFeatureSource(remoteConfig)
val konfeatureInstance = konfeature {
addSource(source)
register(profileFeatureConfig)
}
Similarly, you can add multiple sources, for example, Huawei AppGallery, RuStore, or your own backend.
SourceSelectionStrategy
You can configure the retrieval of an element's value from the source more flexibly by using the sourceSelectionStrategy parameter:
val profileFeatureTitle: String by value(
key = "profile_feature_title",
description = "title of profile entry point button",
defaultValue = "Feature number nine",
sourceSelectionStrategy = SourceSelectionStrategy.Any
)
Where sourceSelectionStrategy filters the available data sources.
public fun interface SourceSelectionStrategy {
: Set<String>
{
None: SourceSelectionStrategy = SourceSelectionStrategy { emptySet() }
Any: SourceSelectionStrategy = SourceSelectionStrategy { it }
: SourceSelectionStrategy = SourceSelectionStrategy { sources.toSet() }
}
}
The select(...) method receives a list of available Source names and returns a list of sources from which the configuration element can retrieve a value.
For most scenarios, predefined implementations will be sufficient:
SourceSelectionStrategy.None - prohibits taking values from any source, i.e., the value specified in defaultValue will always be used
SourceSelectionStrategy.Any - allows taking values from any source
SourceSelectionStrategy.anyOf("Source 1", ... ,"Source N") - allows taking values from the specified list of sources
[!IMPORTANT]
By default, SourceSelectionStrategy.None is used!
Interceptor
Allows intercepting and overriding the value of the element.
public interface Interceptor {
public val name: String
public fun intercept(valueSource: FeatureValueSource, key: String, value: Any): Any?
}
name - the name of the interceptor
intercept(valueSource: FeatureValueSource, key: String, value: Any): Any? - called when accessing the element with key and value from valueSource(Source(<name>), Interceptor(<name>), Default), and returns its new value or null if it doesn't change
Example of implementation based on DebugPanelInterceptor:
After that, you need to add the Interceptor in Konfeature:
val profileFeatureConfig: FeatureConfig = ProfileFeatureConfig()
val source: FeatureSource = FirebaseFeatureSource(remoteConfig)
val debugPanelInterceptor: Interceptor = DebugPanelInterceptor()
val konfeatureInstance = konfeature {
addSource(source)
register(profileFeatureConfig)
addInterceptor(debugPanelInterceptor)
}
Similarly, you can add multiple interceptors.
Logger
public interface Logger {
public fun log(severity: Severity, message: String)
public enum class Severity {
WARNING, INFO
}
}
The following events are logged:
- key, value, and its source when requested
Get value 'true' by key 'profile_feature' from 'Source(name=FirebaseRemoteConfig)'
Source or Interceptor returns an unexpected type for key
Unexpected value type for 'profile_button_appear_duration': expected type is 'kotlin.Long', but value from 'Source(name=FirebaseRemoteConfig)' is 'true' with type 'kotlin.Boolean'
Example of implementation based on Timber:
class TimberLogger: Logger {
override fun log(severity: Severity, message: String) {
if (severity == INFO) {
Timber.tag(TAG).i(message)
} else if (severity == WARNING) {
Timber.tag(TAG).w(message)
}
}
{
TAG =
}
}
After that, you need to add the Logger in Konfeature:
val profileFeatureConfig: FeatureConfig = ProfileFeatureConfig()
val source: FeatureSource = FirebaseFeatureSource(remoteConfig)
val debugPanelInterceptor: Interceptor = DebugPanelInterceptor()
val logger: Logger = TimberLogger()
val konfeatureInstance = konfeature {
addSource(source)
register(profileFeatureConfig)
addInterceptor(debugPanelInterceptor)
setLogger(logger)
}
Spec
Konfeature contains information about all registered FeatureConfig in the form of spec:
public interface Konfeature {
public val spec: List<FeatureConfigSpec>
public fun <T : Any> getValue(spec: FeatureValueSpec<T>): FeatureValue<T>
}
This allows you to obtain information about added configurations as well as the current value of each element:
val konfeatureInstance = konfeature {...}
val featureConfigSpec = konfeatureInstance.spec[0]
val featureSpec = featureConfigSpec.values[0]
val featureValue = konfeatureInstance.getValue(featureSpec)
This can be useful for use in the DebugPanel
Ordering
The value of the configuration element is determined in the following order:
Contributing
Merge requests are welcome.
For major changes, please open an issue first to discuss what you would like to change.