Platform roadmap - FloKit.AI

RevenueCat and Adapty make their platform coverage obvious. FloKit should do the same, even while SDKs are future-facing.

Planned surfaces

Surface	Role	Status
React Native SDK	Purchases, entitlements, app measurement	Shipping — see SDKs
Web checkout (`@flokitai/checkout-js`)	Browser checkout runtime for hosted Flows	Shipping — v0.6.2
Web checkout React bindings (`@flokitai/checkout-react`)	React wrapper over `@flokitai/checkout-js`	Shipping — v0.6.2
iOS SDK (Swift)	Native counterpart to the React Native SDK	Scaffold only — no code, no release
Android SDK (Kotlin)	Native counterpart to the React Native SDK	Scaffold only — no code, no release
Node.js SDK	Server event ingestion, reports, action queue workflows	Planned
Python SDK	Warehouse jobs, notebooks, analytics workflows	Planned
Web API	Server-to-server event and reporting access	Placeholder
Webhooks	Action and guardrail notifications	Placeholder
MCP server	Agent-readable growth context and proposed actions	Shipping — see Assistant

The iOS and Android entries are empty directories in the platform repository with a documented target shape. They are listed so the roadmap is honest about what exists — there is nothing to install, and no publish pipeline is wired for either.

Integration posture

FloKit should not require a mobile SDK on day one. The first marketing promise can be: connect the systems you already use, validate the numbers, then turn on controlled actions.

Copy direction

Use this section to make FloKit feel easy to adopt:

No app release required for first read-only setup
Works alongside existing subscription infrastructure
Starts with reporting and recommendations
Moves to automation only when guardrails are trusted