Embeddable decision-flow engine for onboarding, questionnaires and assessments; separates logic from presentation, emits renderable states from JSON-defined flows, offers theming or fully custom UI integration.
FlowKit is a Kotlin Multiplatform SDK that allows mobile apps to embed structured decision flows such as onboarding, questionnaires and assessments without building a custom evaluation engine.
The SDK provides a reusable mobile flow engine that works on Android and iOS while allowing full control over the UI so the experience matches your app's design system.
Most mobile apps eventually need to:
Teams usually implement this logic from scratch. The complexity is not the screens — it's:
FlowKit solves that.
FlowKit is:
FlowKit is NOT:
FlowKit separates logic from presentation.
The engine manages the flow. Your app renders the UI.
The SDK emits renderable state:
QuestionState
OnboardingStepState
ResultState
Your UI (or our default UI) displays it.
Use the provided screens:
FlowKitQuestionnaireScreen(session)Match your brand:
Implement your own UI while using the engine:
@Composable
fun CorporateQuestionScreen(
state: QuestionState,
actions: QuestionActions
)This allows companies with strict design systems (banks, fintech, enterprise apps) to integrate FlowKit without changing their visual identity.
Flows are defined via JSON configuration.
Example:
{
"id": "risk_profile",
"steps": [
{
"type": "single_choice",
"id": "q1",
"title": "How familiar are you with investments?",
"options": ["None", "Basic", "Advanced"]
}
]
}FlowKit UI and integration modules are open-source. The core engine is distributed as a binary dependency under a commercial license.
Contact: (you will add later)
Early development. The goal is to validate real production integrations.
If you are interested in trying FlowKit in your app, open an issue or discussion.
FlowKit is a Kotlin Multiplatform SDK that allows mobile apps to embed structured decision flows such as onboarding, questionnaires and assessments without building a custom evaluation engine.
The SDK provides a reusable mobile flow engine that works on Android and iOS while allowing full control over the UI so the experience matches your app's design system.
Most mobile apps eventually need to:
Teams usually implement this logic from scratch. The complexity is not the screens — it's:
FlowKit solves that.
FlowKit is:
FlowKit is NOT:
FlowKit separates logic from presentation.
The engine manages the flow. Your app renders the UI.
The SDK emits renderable state:
QuestionState
OnboardingStepState
ResultState
Your UI (or our default UI) displays it.
Use the provided screens:
FlowKitQuestionnaireScreen(session)Match your brand:
Implement your own UI while using the engine:
@Composable
fun CorporateQuestionScreen(
state: QuestionState,
actions: QuestionActions
)This allows companies with strict design systems (banks, fintech, enterprise apps) to integrate FlowKit without changing their visual identity.
Flows are defined via JSON configuration.
Example:
{
"id": "risk_profile",
"steps": [
{
"type": "single_choice",
"id": "q1",
"title": "How familiar are you with investments?",
"options": ["None", "Basic", "Advanced"]
}
]
}FlowKit UI and integration modules are open-source. The core engine is distributed as a binary dependency under a commercial license.
Contact: (you will add later)
Early development. The goal is to validate real production integrations.
If you are interested in trying FlowKit in your app, open an issue or discussion.