Overview
Every app version you publish is a release. A release moves through one pipeline: you upload it, submit it, Elata scans it, and a moderator approves it.Step 1: Upload
Upload a.zip (or a single .html file) from the wizard or your app’s edit
page. Elata checks it straight away:
- the file type and size are within limits
- the bundle has an
index.htmlentry and safe file paths - the bundle uses an Elata sensor SDK
elata.json.
You can try a draft in Elata’s play window, and share it with up to 10
playtest friends, before anyone else can see it.
Step 2: Submit for review
When you submit, Elata checks that your listing is complete. You need an app icon and a header image. Screenshots are optional but recommended. The listing details are frozen onto the release at this point, so later edits don’t change what was reviewed. You can withdraw a submission while it is pending.Step 3: Automated security scan
Every submitted release is scanned automatically. The scan looks for things like wallet-draining code, attempts to escape the sandbox, credential access, obfuscated code, and missing SDK usage. A release that fails the scan is held back from Elata.Scan findings are reviewed by the Elata team and are not shown in detail to
uploaders. If your release is held, you’ll hear from us through Elata.
Step 4: Moderator approval
An Elata moderator reviews the release against the submission policy. Once approved, it becomes your app’s live release and you’re notified in Elata and by email. If it’s rejected, fix the issues and submit again.After you’re live
Approval makes a release eligible to be played. Whether people can find and play it also depends on:
To ship an update, upload a new build. It goes through the same pipeline, and
your current live release stays up until the new one is approved.
Next
Requirements
What every upload needs
Publish Your App
The wizard, step by step
Review and Policy
What reviewers look for