Start here
Keep more of what your app already earns. Events, error tracking, experiments, entitlements, paywalls and web checkout — one SDK, and no app release to change any of it.
Fictura is one substrate for the growth stack a mobile app normally assembles from five companies: paywalls and onboarding flows served from a dashboard, web checkout that routes eligible users past the App Store fee, an events pipeline with funnels and cohorts, error tracking with uptime monitoring, and a links platform for attribution. Everything is server-driven — changes reach installed apps on their next config refresh, not their next release.
Three pieces do the work:
- The SDK —
@fictura/sdk, one npm package for Expo and React Native. It fetches your app's config, renders paywalls and onboarding, logs events, and captures errors. Backend agents exist for Python and Node. - The dashboard — where paywalls are designed and events are inspected. Tools are switched on and off, and accounts (Stripe, RevenueCat, Slack, PostHog…) connected, under Dashboard → Tools. Keys are under Setup.
- The REST API —
x-api-key-authenticated endpoints for entitlements and event ingestion, plus a separate Links API and Data API.
The one idea to keep
Your app receives configuration, not policy. Which paywall shows, whether checkout goes to the web, which events are captured — all of it is decided server-side on every config fetch, so the dashboard's off switches are real and immediate.
Where to go next
Start here regardless of what you came for:
- Setup — six steps, each one a prompt you paste into your coding agent, from installing the SDK to your first trace. Each one ticks itself when real data arrives, and your free trial starts at step 2.
- SDK Quickstart — the same install by hand: one package and one call, after which events, errors, entitlements and experiments are all running.
Then, depending on the problem you're solving:
| You want to | Go to |
|---|---|
| Know what users do, and where they stop | Events and the conversion funnel |
| See what's breaking, joined to the user it broke for | Error tracking |
| See slow screens and slow network calls | Tracing |
| Know where an install actually came from | How attribution works and Deep links in your app |
| Test one flow against another | A/B experiments |
| Send a push, or win back a lapsed user | Push & re-engagement |
| Run paid ads or track creator links | Paid ads and Creators |
| Ask whether a user is paid, wherever they paid | Entitlements |
| Keep more of each subscription | Web checkout |
| Change what a paywall says without shipping | Paywalls & onboarding |
| Call it all from your own backend | REST API |
| Ask what your data means, without leaving the dashboard | Hawkings |