Tools
One switchboard for everything Fictura does in your app. Toggles reach installed devices on the next config refresh — no code change, no release, no review.
Dashboard → Tools. Every capability the platform offers, as a switch. Flip one and the change reaches devices that already have your app installed, the next time they refresh their config — no code change, no release, no App Review.
The page is split in two, and the split matters.
UI — things your users see
These render inside your app, and you control them from here instead of from code:
- Paywalls — the screen that asks for money. Design it here, ship it without an update.
- Onboarding Flows — the first screens a new person sees. Reorder and rewrite them the same way.
- Cancel Survey — asks people why they cancelled their trial, in the app, at the moment they do it. Answers land on your dashboard.
Turning one of these off does not hide a feature from your dashboard. It stops the app from showing that surface to users.
Tools — things that run on Fictura
These need nothing added to your app. They run on our side and show up in the dashboard:
A/B Testing, Churn Analytics, Event Tracking, RevenueCat billing signal, App Builder, Paid Acquisition, Error Tracking, Outgoing Webhooks, App Store Connect, Sentry, Web Checkout, and the payments connection.
Reading a card
Each card carries the tool's name, one line on what it does, and a switch. Two badges tell you when a switch is not the whole story:
- soon — listed but not built yet. The switch does nothing.
- not connected — the tool works, but it needs an account connected before it can do anything. The badge is a link to the page where you connect it.
A switch is not a connection
Turning on a tool that needs an account does not connect the account. Paid Acquisition without Meta connected, App Store Connect without Apple connected, Sentry without a DSN — all of these read as on and do nothing. Follow the not connected badge.
How a toggle reaches a phone
Your app asks for its config on launch and periodically after that. The answer includes which tools are on. Nothing is compiled into the build, so a switch you flip now applies to every install already out there, not just to people who update.
Almost everything here is on by default. An app that has never touched this page has the full stack running.
Web Checkout is the exception
Web Checkout is the one tool that is off by default, and deliberately so. It sends iOS users to your own hosted checkout instead of Apple's payment sheet, which is why you keep roughly 27% more of each subscription — and it is also a tool that reroutes money and has tax consequences. Something that moves money should be switched on by a person who has read what it does, never inherited from a default.
It also stays off until Stripe is connected. A switch that sends people somewhere with nowhere to send them is worse than no switch.
Web Checkout can additionally be limited by country, decided on our side rather than in your app. The same build sells through your checkout in one market and through Apple in another, and a device whose country we cannot determine falls back to Apple — the safe side of that mistake.