Fictura
Paywalls & onboarding

The paywall editor

Build a paywall by moving things on a phone — screens, layers, spacing, live prices — and publish it without an app release. Every control, and what each one does.

The editor builds a document: a tree of nodes that the server turns into the exact page a phone is served. There is one renderer, and the canvas asks it — so what you see is not a drawing of the paywall, it is the paywall.

Getting there

Sidebar → Monetize → Paywalls. Three ways in:

What it does
Browse templatesA gallery of finished designs. Open in editor loads one and creates nothing — the paywall is written when you save. Use this template writes it as a draft in Paywalls
Edit on a cardReopens a design you built. A design written as raw HTML opens on its images, colours and words — see Served designs
A share linkSomeone else's design, ready to copy into your app — see Sharing and copying

Set your slots first

Plan cards sell slots. With none configured, every plan card is empty on the phone while looking correct in the preview.

The three panes

┌────────────┬──────────────────────┬──────────────┐
│ SCREENS    │                      │ SCREEN  /    │
│  Hero      │    [ iPhone 15 ]     │ TEXT / PLAN  │
│  Proof     │                      │ Products     │
│  Plans   + │  ‹ Screen 1 of 3 ›   │ History      │
├────────────┤                      │ Test         │
│ LAYERS +Add│                      │ AI           │
│ ▣ Stack    │                      │ Stats        │
│  T Headline│                      │              │
└────────────┴──────────────────────┴──────────────┘
  Figma · Store shot · On phone · Agent · Undo · Save · Publish
  Edit ⇄ Preview ⇄ Flow · language · trial · plans · prices · device

Screens — left, top

A paywall is rarely one screen. Each has its own background and glow, and they are walked with Nav buttons.

  • + adds a screen after the current one
  • Hover a screen for ↑ ↓ (reorder), ⧉ (duplicate), ✕ (delete)
  • The last screen cannot be deleted
  • Clicking a screen lands the phone on it — it does not step through

Layers — left, bottom

The tree of what is on this screen.

  • + Add opens the palette, grouped: Layout, Content, Answers, Selling, Around it. Pieces you saved from another design sit on top, under Saved pieces
  • Drag a row to move it. The top or bottom edge of a row means before or after it; the middle of a Stack means inside it
  • A node is never dropped into itself
  • Hovering a row outlines it on the phone

The phone — middle

  • Edit — a tap selects a node and goes no further
  • Preview — the editor lets go: buttons work, the trial switch flips, the flow walks, and the screens rail follows along
  • Flow — every screen at once, with where each tap goes
  • The device picker changes the size. The page always renders at the real device size and is only displayed smaller — the zoom is written beside the screen name
  • The bar above it sets what the design is standing in: the language, the Default or Free Trial side, what the store answers (Trial available, Trial spent — hide, Trial spent — disable, Store answered nothing), one plan missing from the offering, and sample prices in $ or ₹. Prices on the canvas are always samples

The inspector — right

Six tabs: the selected node (or Screen), Products, History, Test, AI and Stats.

With nothing selected, the first tab shows the screen: its name, background, glow and how it treats the notch and home bar. Under that are the settings for the whole paywall — see Paywall behaviour. Select a node and it also has Show when, States and On tap.

What you can put on a screen

Stack
layout

A row or a column. Everything else lives inside one. Direction, gap, padding, how children line up across and along.

Text
content

A line or a paragraph. Takes live values — see below.

Feature list
content

Rows of benefits. Each row may carry its own icon image, or they share one bullet — a dot or a tick. Optional tick after the words.

Icon
content

A line icon from the built-in set. Blank colour takes the ink around it.

Image
content

A picture by URL, from your asset library, or generated with AI. Height and fill/fit. A Bundled picture name draws a file from the app instead of downloading one, and falls back to the URL — see localImages in the SDK reference.

Video
content

A clip by URL. It starts muted, inline and autoplaying — a phone refuses to autoplay anything else, and iOS takes a non-inline video fullscreen over your paywall. It loops unless you pick Play once; Tap for sound and Controls are options. Set a poster: on a slow connection it is most of what people see.

Carousel
content

Slides that swipe, with an optional caption over each. Next slide every (ms) moves it by itself until someone swipes.

Lottie
content

A Lottie animation by the address of its JSON file. It plays as soon as the screen shows.

Drawer
layout

A sheet that opens over the screen, named so a button or tap action can open it. It can start open, and Tap outside closes can be off for one that has to be answered.

Progress dots
layout

Dots that follow the screens of the flow, or a carousel.

Text input · Multiple choice · Slider · Date picker
answers

Questions on the paywall. Each answer is readable as el.<id>.value, and Save as user attribute keeps it on the user. A slider can also pick a plan, left to right.

Plan card
selling

Sells a slot. Its own price line and note, and a second wording used while the trial switch is on.

Trial switch
selling

Swaps every plan card to its trial product. Leave its label blank and it says what the store allows — "Start with 7 days free".

Buy button
selling

Buys the selected plan.

Nav button
around it

Moves between screens: Next, Back, or Skip — skip jumps to the last screen, the one that sells. It can also open or close a drawer.

Close ✕ · Restore · Legal links
around it

The chrome. A legal link left blank uses the app's own legal URLs from Growth.init. With no address at all it is hidden rather than left dead — App Store Review 3.1.2 wants these reachable.

Live values

Type these into any text, button or plan line. They are filled on the phone from the plan being sold, in that user's currency:

TokenWhat it becomes
{price}The price, as the store writes it
{raw_price}The number alone, for a design that draws its own symbol
{currency}USD, INR
{per_day} · {per_week} · {per_month} · {per_year}The same price expressed per day, week, month or year
{period}week / month / year
{trial_days}How many free days the store is granting
{trial_period}3 days / 1 week
{save}How much cheaper, per week, than the dearest plan on screen

Add :slot to pin one to a particular plan — {price:secondary}. Inside a plan card a token with no slot means that card's plan, so {price}/{period} needs no slot. Anywhere else it means the plan the user has selected.

Device, user and state values use double braces instead — {{ device.platform }}. See Paywall behaviour.

Never type a price

A number typed into a headline is right in one country and wrong in every other, and the ones it is wrong in are the ones nobody on your team will see. {save} is computed from the plans on screen, so it stays true when a price moves.

Spacing and position

With a node selected, the phone shows its padding as a tinted band with green handles on the inner edges. Drag a handle to change it; a readout follows the cursor. A Stack also shows the gap between its children, with its own handle.

In the inspector:

  • Margin — four fields, T R B L. Space outside the node. Padding is inside; gap is between every child equally. Margin is the only one that pushes one thing away from its neighbours
  • Position — In flow, Sticky or Free. Sticky scrolls with the page, then holds the top or bottom edge. Free lifts a node out of the flow and pins it to a corner of the screen; you then drag it anywhere on the phone and it stays where you let go

Why a corner and not coordinates

A pinned node stores an anchor and an offset, never x/y. 16px from the left of a 393pt phone is not 16px from the left of a 440pt one — absolute coordinates drift on every device that is not the one they were drawn on.

Saving and publishing

  • Save writes a draft. Publish saves and makes it live for this placement
  • Phones pick a published paywall up on their next config refresh — no app release
  • Editing one of our templates always saves a copy; the template stays where the next person expects it
  • Saving over a design that is live asks first, and says so. You can save a copy instead
  • Unsaved work is kept in this browser and offered back when you reopen the paywall

The API enforces the same rule. On a live paywall, PUT /api/v1/paywalls/:id with a config, PATCH /api/v1/paywalls/:id/overrides and POST /api/v1/paywalls/:id/rollback answer 409 with paywall_is_live and change nothing, unless the body carries confirm_live: true. A rename is not guarded.

Set live on a paywall card asks which stores it serves: both, Apple devices or Android devices.

History

The History tab lists every save, newest first. Click one to see it on the phone, read-only. Restore saves it again as the newest version, so restoring is itself in the history and can be undone the same way. A version can carry a note. Restoring over a live paywall asks first, because users see it right away.

Preview on a phone

On phone gives a QR code that opens the saved design inside your app with its real products, drafts included. Nothing is set live.

  1. Enter your app's URL scheme, from app.json. The browser remembers it
  2. Scan the code. The link is <scheme>://?fictura_preview=<paywall id>
  3. A Preview ⋯ menu on the phone switches language, reloads after a save, and closes the preview

It needs an app build on SDK 0.23 or later, and a design that has been saved. GrowthProvider listens for these links. If your app consumes its own links before the SDK sees them, pass them on:

TypeScript
import { openPaywallPreview, previewIdFrom } from "@fictura/sdk";

// Returns whether the link was a preview.
if (previewIdFrom(url)) openPaywallPreview(url);

Test tab

Pin values to see the design as someone else would: appearance, phone size, what a purchase answers, and what the app answers to a custom action or permission. It also shows what every variable holds right now, and a log of every action a tap ran.

AI in the editor

These need the AI plan or your own Anthropic key in Setup → AI. Nothing is saved until you press Save, and ⌘Z takes back a change.

  • AI tab — say what to change and the design changes. You can attach a picture to match, or let it see the screen as it renders. Chats are kept per paywall, in this browser
  • AI… beside an image — describe a picture and get an illustration, uploaded to your asset library
  • Languages on the Screen tab — pick a language at the top of the editor, then Translate missing, Update outdated or Redo all, with a formality setting and a style guide. Lines that come back with a placeholder changed stay in the base language

Translations also round-trip as CSV, or as an Apple .strings file for one language, with no AI needed. Only words are per language: pictures and colours are shared. On the phone, Growth.setLocale() or getLocale picks the language, otherwise the device's.

Import from Figma

Figma takes a frame's link (Share → Copy link to selection) and a personal access token with file content read access. The layout replaces what is on the canvas; variables, theme, fonts, surveys, reminders and languages stay. Auto Layout frames become stacks, pictures and icons are copied into your asset library, and several phone-sized frames side by side become screens. The token is used for that one request. It is stored only if you tick the box, and then only in this browser.

Stats tab

How this paywall is doing over 7, 30 or 90 days: conversion, views, purchases, closes without buying, proceeds as the store reported them, views per day, how far people get through its screens, median time on it, plans bought, and splits by experiment arm and placement. Conversion is unique purchasers over unique viewers.

It counts events that name this paywall, so builds older than SDK 0.21 are not included.

Sharing and copying

From the ⋯ menu on a paywall card:

  • Share link — anyone signed in to Fictura with the link can copy the design into their own app, as a draft. Products, prices and results are never shared. Stop sharing breaks the link for good. Only designs made in the editor or as HTML can be shared
  • Copy to another app — a draft copy in another app you belong to. Its plans use that app's own products
  • Presentation — whether the feature behind it waits for a purchase, its style and delay — see Placements and campaigns
  • Archive — keeps it and its history, out of the list. Taking it back out makes a draft
  • Delete — removes it and its history. A paywall a campaign is using cannot be deleted

A live paywall cannot be archived or deleted. Set another one live first.

Other tools

  • Store shot downloads a 1290×2796 screenshot for App Store review
  • Agent gives a code that lets a coding agent read and change the open design through the MCP server. Its changes land on the canvas and nothing is saved until you save
  • A selected node can be saved as a piece for reuse in other designs, under Saved pieces

Products tab

Per paywall: which offering to fetch, which packages, what to do with a plan this user cannot buy, and who sees the intro offer (Store decides, Always show, Never show). Below that, the app-wide slot mapping and any warnings about it — see Slots and products.

Keyboard

None of these fire while you are typing in a field, where the browser's own undo is the one you meant.

⌘Z / Ctrl+ZUndo
⌘⇧Z or ⌘YRedo
⌘C · ⌘X · ⌘VCopy, cut, paste — between paywalls too
⌘DDuplicate the selection
DeleteRemove the selection
Arrow keysNudge a Free node. Hold ⇧ for 10
EscClear the selection

On this page