Submitting your app

From the developer portal

1. App detailsName, category, tagline, description, data note and the plans it works on. The support email comes from your developer profile.
2. Media and codeA cover, up to 8 screenshots with alt text, the app icon, and your app's code: connect GitHub and pick the repository and branch (required).
3. PricingFree, one-time or monthly, and the price. You see what you keep at the 80/20 split.
4. Customization and this updateWhat an owner's sentence may change (test a sentence to see what would change), the version number you propose and, from the second version on, the update notes.
5. Review checklistConfirm the six promises, then press Submit for review.

Open it at Submit an app. The form saves as you go.

Your app's code comes from GitHub

There is no ZIP to upload. Under App code on the Media step, connect GitHub, pick the repository and pick a branch. The repository has ezystudio-app.json at the top and follows the rules in The bundle.

• When you pick the branch, we check its latest commit right away, so a missing manifest, a file an app may not ship, a secret or a repository that is too big shows up there, with the reason. After a push, press Check again.
• When you submit, we freeze the branch's latest commit. We keep a copy of that commit: it is what reviewers test and what customers install, whatever you push afterwards. The next version takes the newest commit when you submit it.
• There is no demo link to add. We build a test site from the frozen commit and host the preview ourselves.

Every update says what changed

Customers have their own copy of your app, often customised. When they update, their AI applies your changes to their copy. So from the second version on, the Customization step asks for three notes:

You also propose the version number (1.2 or 1.2.3). It must be higher than the live version, or submit answers 422 E_DRAFT_INCOMPLETE. The reviewer who publishes it confirms the number, or sets another one, when it goes live.

The six promises

Every submission confirms all six. Missing any answers 422 E_ATTESTATIONS_INCOMPLETE with the missing ones in meta.missing.

After you submit

• You get a reference like SUB-1042 and an email (“{app} {version} was submitted for review”). A person reviews it within 7 business days, and we email you at every step.
• We build a test site of your version straight away, with its own database: your migrations run on it and it is filled with sample customers and your sampleData. A build or sample data problem shows up on your submission before a reviewer looks.
• The draft is locked while the submission is queued or in_review. Saving answers 409 E_APP_IN_REVIEW.
• Withdraw (POST …/apps/{appId}/withdraw, or in the portal) to make changes. The version goes back to draft; sending it again starts a new place in the queue.
• If a reviewer asks for changes, fix them and submit again. A resubmission keeps your place in line: same reference, same target date. Each ask is ticked off as soon as your draft changes the part it points at.

Limits

Errors you may see