AppLab launch help and how-tos

Choose web or mobile, answer the short questions and review the plan before building your pack. Your AI builder implements the app; the ZIP is a set of files and instructions, not a finished signed app.

Upload your pack and send the current prompt to your builder. Run its visible checks, paste its reply back and only then continue. A tick you entered is not independent proof that a payment or device feature works.

Use the Build monitor and your app's own manual. Waiting, not tested and stale are not passes. Test sign-in, owner access, real data writes and payments when your app uses them.

Publish from your builder, connect your own domain and test the public address while signed out and signed in.

Adapt the native project, arrange store accounts and signing, test real devices and submit for review. Upload, approval and public release are different stages.

Pick one method and measure actual visits or replies. No revenue or launch date is guaranteed.

Open My apps and your saved build to download the original ZIP. A successful private backup keeps the same plan and branding on another device. Older packs without a backup may need their original browser or logo files.

Personal includes 3 app slots. Agency includes 50, commercial rights and the Agency Hub. Deleting an app does not return its slot. Agency buyers already have the Hub and do not need OTO 1 again.

Ask FrankenBot for one next step or open the Repair Bay with the exact error. For purchase access, send support your receipt number and buying email. Never send passwords, payment card details or private signing keys.