Skip to main content
This page captures documentation gaps to close as FloKit’s marketing docs mature.

​
What strong subscription docs do well

  • Clear SDK quickstarts with copy-paste snippets
  • Platform coverage tables
  • Webhooks and API pages with concrete event objects
  • No-SDK or server-to-server integration paths
  • Paywall, offering, entitlement, and revenue analytics concepts
  • Migration guides for teams with existing users and receipts
  • Operational recipes that connect setup to business outcomes

​
FloKit gaps to close

  • Add a crisp “Why FloKit” page that contrasts CAC optimization with subscription management.
  • Add source-specific guides for RevenueCat, Adapty, AppsFlyer, Adjust, Meta, Google, TikTok, Stripe, and warehouses.
  • Add event object examples for every lifecycle event.
  • Add a real webhook catalog for action and guardrail events.
  • Add report screenshots or representative tables for payback, creative quality, and action outcomes.
  • Add “no app release required” setup path for read-only adoption.
  • Add migration and coexistence docs for teams already using subscription platforms.
  • Add security, permissions, and data retention pages before enterprise conversations.

​
Positioning principle

FloKit should not try to look like another subscription SDK. The docs should make the category clear: monetization tools manage purchase state; FloKit turns acquisition, creative, funnel, and revenue signals into controlled growth actions.