Fictura
Paywalls & onboarding

Native templates

Prebuilt React Native paywall and onboarding flows that ship inside the SDK — the dashboard edits words, six colours, and which screens run.

A locked template's layout lives in SDK code; its config carries only copy, a palette, and a screen toggle map. That trade is deliberate: no canvas and nothing to drag, so a config can never break a layout, and every change still reaches installed apps on the next config refresh.

What ships in the SDK

KindKeyScreens
Paywallhouse_ai5-screen flow: free_try → trial_notification → trial_reel → exclusive_offer → one_time_offer
Paywalltemplate_24-screen flow: intro → features → notification → pricing
Paywallhouse_ai_v2One screen, with a video hero
Onboardinghouse_ai25 steps; welcome and plan_ready always on
Onboardingtemp48 steps, light theme — welcome, value prop, then questions
Onboardingtemp54 steps, fitness-oriented
Onboardingtemp67 steps, light theme — welcome, four questions, closing pitch

Copy fields accept placeholders — {price}, {percent}, {per_week}, {standard_price}, {trial_days}, {reminder_days} — substituted at render from the live store package. Unknown placeholders stay verbatim on purpose, and the backend rejects literal currency amounts in copy so a hard-coded "$9.99" can never drift from the store's truth.

Old builds and new templates

A template key the installed SDK doesn't know renders a fallback — "Update the app to see this offer." with a working Close — and logs paywall_load_failed with stage: "template" and error: "template_unsupported". The dashboard's preview mirrors the SDK registry, so what previews is what devices can actually render.

Registering your own

TypeScript
import { registerPaywallTemplate } from "@fictura/sdk";

registerPaywallTemplate({
  key: "my_template",
  name: "My template",
  defaultTheme: MY_THEME,     // the palette the dashboard edits
  Component: MyPaywall,       // your React Native screen
  flow: MY_SCREENS,           // optional: the screens of a multi-screen flow
});

Default artwork for the SDK's own templates is hosted and fetched by the device, so it isn't in the package. Pass your own through the assets prop and it wins, key by key. Imagery can't travel in the config, because a config that could name an image could change what a reviewed app displays.

On this page