For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Join Community
WelcomeDocsAPI ReferenceWebhooksChangelog
WelcomeDocsAPI ReferenceWebhooksChangelog
  • Introduction
    • Welcome
    • Quick Start
    • Testing Your App
  • App Store
    • App Types
    • Listing Requirements
    • App Subscriptions
    • Deeplinks
  • Authentication
    • Overview
    • Quick Start
    • Implementation Guide
    • Scopes
    • Rate Limits
    • Working With Rate Limits
  • Versions
    • Overview
    • Management Strategies
  • Build With AI
    • Docs For Your LLM
  • Tutorials
    • Example Chatbots
    • Multipart Media Upload
    • Sending Mass Messages
    • Security
  • Integrations
    • n8n
LogoLogo
Join Community
On this page
  • Embedded apps
  • Configuring app surfaces
  • Request only the permissions you actually need
  • Off-platform apps
  • Listing, payment, and app type
  • Public listings and payment rails are coming soon
  • Choosing the right type
  • Next steps
App Store

App Types — Embedded vs Off-Platform

Understand the two app types, their constraints, and how they interact with App Store listing and Fanvue payment rails.
Was this page helpful?
Previous

App Store Listing Requirements

Requirements for being listed — and remaining listed — in the Fanvue App Store.

Next
Built with

Every Fanvue app is either embedded or off-platform. This choice shapes where your app appears for creators (and their fans), what rules apply to it, and whether it must be listed on the App Store.

Embedded apps

Embedded apps run inside Fanvue’s UI. They’re rendered in iframes on one or more app surfaces — predefined locations where Fanvue allows third-party UI.

  • Must be listed on the App Store to be available to creators. There is no way for a creator to install an embedded app without an App Store listing.
  • Always have a creator surface — a place in the creator’s own dashboard or settings where they can interact with the app.
  • May optionally have fan-facing surfaces — for example, UI embedded in a post or inside a chat, where fans who follow or subscribe to the creator interact with your app.
  • May or may not have a separate installation URL depending on your setup and configuration.

Configuring app surfaces

For each surface your app uses, you provide:

  • A URL that Fanvue will load in an iframe at that surface.
  • A set of iframe sandbox permissions (the HTML sandbox attribute values) the surface needs in order to function.
Request only the permissions you actually need

Iframe sandbox permissions should be the minimum required for your app to function. Over-permissive configurations are a common reason apps are rejected during review. If your surface doesn’t need allow-top-navigation, allow-popups, or allow-same-origin, don’t request them.

Off-platform apps

Off-platform apps run outside Fanvue’s UI — on your own domain, as a desktop app, CLI tool, mobile app, or any other standalone experience. They use the Fanvue API via OAuth, but creators interact with them somewhere other than Fanvue itself.

  • Do not require an App Store listing. You can build an off-platform app purely for yourself, a specific client, or a private user group without ever submitting to the App Store.
  • However, an off-platform app may still choose to be listed on the App Store to reach a wider audience — and if it is listed, the same rules apply as to any other listed app.

Listing, payment, and app type

Two connected rules govern how app type, App Store listing, and Fanvue payment rails interact:

Fanvue payment rails are available only to embedded apps on the App Store; any paid app on the App Store must use them.

Taken together, these rules mean that off-platform apps listed on the App Store must be free: they can’t use Fanvue payment rails (because they aren’t embedded), and they can’t use any other processor (because listed apps must use Fanvue rails).

Public listings and payment rails are coming soon

Both public App Store listings and Fanvue payment rails are still rolling out. Today you can submit any type of app for pre-approval — the rules above govern review decisions now, so your submission should already comply. Approved apps will appear on the App Store and (if applicable) be able to charge through Fanvue once those pieces launch. Off-platform apps are unaffected.

Every valid plan fits one of these rows. Anything not on this list is ruled out by the rules above.

App typePaid/FreeApp Store listingPayment
EmbeddedFreeRequired—
EmbeddedPaidRequiredMust use Fanvue payment rails
Off-platformFreeOptional—
Off-platformPaidNot permittedAny payment processor you choose

Choosing the right type

A quick decision guide:

  • Do you need to render UI inside Fanvue (in the creator’s dashboard, posts, or chat)? → Embedded.
  • Do you want fans — not just creators — to interact with your app from inside Fanvue? → Embedded, with a fan-facing surface.
  • Is your app a standalone product, CLI, or tool that runs on your own infrastructure? → Off-platform.
  • Do you want to charge creators and have Fanvue handle billing? → Your app must be embedded and listed on the App Store. Fanvue payment rails aren’t available to off-platform apps.

Next steps

  • Publishing Your App — submission flow, required fields, review, and app states.
  • Listing Requirements — the policy baseline for every listed app.
  • OAuth Implementation Guide — the authentication flow that powers every app, embedded or off-platform.