Documentation
How Ripping works
Using it, what a generated app can do from its own code, taking payments, and the machine-readable copies of all of this for agents.
Guide
- Getting startedFrom the idea box on getripping.com to a running app, including the free first build and what it contains.
- The editorWhat each part of the build screen does, from the chat and its modes to the tabs on the right.
- TemplatesThe pre-built apps you can start from, with the prompt each one answers.
- TemplatesWhat a template is, where the gallery appears, and what a click does in each place.
- App users and dataThe accounts your app's users get, how sign-up is controlled, and what the Data tab shows.
- PublishingDeploying to a URL, connecting a custom domain, packaging a Chrome extension, and sharing a project.
- Plans and tokensWhat each plan includes, how tokens are counted and capped, and what the Billing page shows.
- Affiliate programEarn a share of every payment from the accounts you send to Ripping, and how it is paid.
Building apps
- Generated app anatomyWhat a Ripping app is made of, where it runs, where its data lives, and which scaffold it started from.
- The kitEvery component, hook and helper that @ripping/kit exports, with the props that matter.
- App accountsHow people sign up and sign in to a generated app, what a session is, and the auth endpoints behind it.
- Saving dataPer-account data with useStore and useSynced, shared collections with useShared, and the routes and limits behind them.
- File uploadsHow a generated app stores files people upload, the size and type limits, and how public and private files are addressed.
- Taking paymentsSelling the owner's products from a generated app: the pay module, the pay provider actions, and who owns what.
- Connected servicesThe call route that lets a generated app use the owner's connected services without holding a secret, and the limits on it.
- Routing and SEOHash routes, page titles, share previews, the SITE config every public string comes from, and crash and visit reporting.
- RecipesThe tested UI and data patterns the builder drops into an app instead of writing them from scratch.
- RecipesReady-made pieces the builder reaches for: their code, verbatim.
Payments
- Payments overviewThe three ways an app can take money, what each supports today, and what each costs.
- Ripping PaymentsSetting up Ripping Payments, what the Payments page shows, and how the fee and refunds work.
- Your own processorConnecting your own Stripe or PayPal account, and what changes for buyers when you do.
- Products and salesThe product catalogue, what a buyer sees at checkout, the Sales tab, and the buyer's Purchases page.