Submit for Review & Publish

Once you've integrated the platform capabilities and verified everything in local preview, you're ready to publish from the Developer Console. There's no local packaging tool needed anymore — just produce static files using your own build process.

Prepare artifact
Package as .zip
Create app
Get a generator name
Listing details
Title / description / cover
Code artifact
Upload the packaged artifact
Submit for review
Auto-published once approved

1. Prepare the Artifact

Build a static Web bundle that's ready to deploy (with the platform SDK already included in the page), then package it into a single .zip file (50 MB max).

Before packaging, confirm the artifact still includes the SDK

Your app depends on the platform-sdk.js script tag in the page to connect to platform capabilities in production. Some build configurations can cause the production entry page to drop this script, which results in "works fine in local preview, but export stops working after publishing." Before uploading, make sure the entry page in your production artifact is the same one you verified locally — and that it still includes the SDK.

2. Create the Application

Click "Create Application" in the Developer Console, and give your generator a name to serve as its runtime identifier (must start with a lowercase letter, and contain only lowercase letters, digits, and hyphens). This name is tied to the production subdomain and access path, and cannot be changed after creation — choose carefully. The card title shown to users is configured separately in the next step.

Create Generator
Give your generator a name as its public identifier. Once created, you'll move to the details page to finish its listing info and code artifacts.
Generator name *
e.g. pixel-avatar
Must start with a lowercase letter, and can contain only lowercase letters, numbers, and hyphens (-). It can't be changed after creation.
+ Create & ContinueCancel

3. Configure Listing Details

Go to "Application List Details" on the app detail page, and fill in the card title, short description, and cover image. A live preview of the app card is shown on the right. This information determines how users see your app on the Creative Tools page, and any changes here also require review.

Card title *
Vintage Photo Frame Generator
Short description *
Upload a photo and instantly apply a vintage film frame.
Cover image *
Save Details

4. Upload the Code Artifact

Switch to "Code Artifact" and upload your packaged .zip (containing index.html and other static files). For live local debugging during development, use the online DevTool — see Local Debugging for details.

Code Artifact
Click to select or drag & drop here
Supports .zip / folder / single .html · Max 50 MB

Upload a packaged static artifact (including index.html).

5. Submit for Review

In "Submit for Review," the platform checks that both the listing details and the code artifact are complete. Once everything is ready, click "Submit for Review" — the listing changes and the new artifact are bundled into a single "pending change" and submitted together. The review result (approved / rejected, with reasons) is sent back to your console via a message.

Submit for Review
Pre-submission Checklist
Listing details complete (title / description / cover image)
Code artifact uploaded
Submit for Review
No resubmission while under review

Once submitted, the application enters "Under Review." You'll need to wait for the result before submitting new changes.

Automatically published once approved

Once approved, the application is published automatically, and its runtime URL becomes https://www.atomm.com/creativetools/community/generator/[generator-name] — users can open it directly from the generator gallery.

Esc
Search all docs · to navigate · to open