Create Free APK

Documentation

AppMint & Appwright integration guide

Everything a page inside a generated app can do - purchases, ads, push, sign-in, databases, the phone's own hardware - written as 357 numbered steps across 47 chapters. This is the same guide that ships inside both builders, published here so you can read it on a laptop, link to a single step, and hand it to whatever you use to write code.

AppMint and Appwright are sibling builders that share an engine. A chapter that applies to both is written once and marked AppMintAppwright; where the two genuinely differ, both sets of instructions are on the page.

Start here

What the builders are, what an app costs to make, and how to give them something to build.

Making money

In-app purchases, subscriptions, ads and card payments inside a generated app.

Backend and accounts

Databases, sign-in and live chat, wired without running a server.

Notifications

Push from a server, and reminders scheduled on the device itself.

Device features

The JavaScript bridge: sensors, files, media, camera, biometrics and the rest of the phone.

App shell and navigation

Deep links, the side menu, offline behaviour, injected CSS/JS and remote updates.

Content apps

Turning documents, photos, audio and video into an app of their own.

Publishing on Google Play

Ownership verification, signing keys, and the errors Play returns on upload.

Reading this with a tool

Every page here has a plain Markdown twin at the same address with .md on the end, linked from the page's own <head>. If you would rather not crawl at all, two files cover the whole thing.