Publishing makes a micro app discoverable and runnable by other community members. Review checks whether the public description, actual behavior, safety boundaries, and community rules are consistent.
Pre-submission checklist
Before submitting, confirm that:
- the name, icon, and summary accurately explain the purpose;
- the main workflow has been tested in the desktop app;
- empty input, invalid input, and cancellation do not cause unexpected results;
- requested permissions directly support the main function and are explained clearly;
- external links are trustworthy and necessary;
- no password, token, private file, or other sensitive data is included;
- you have the right to use all text, images, audio, trademarks, and other material;
- the content follows the Community Guidelines.
Submit for review
Open the draft in creation management, complete its public information, and submit it. The submitted version enters the review flow; do not repeatedly submit the same version while a decision is pending.
Review time depends on content complexity, risk, and queue conditions. Aelrox does not promise a fixed completion time unless the product explicitly provides one.
Statuses
- Draft: only you can continue editing and previewing; it has not been submitted.
- Pending review: the version is in review and some fields may be temporarily locked.
- Approved: the version can be published or is already visible to the community.
- Rejected: changes are required and this version will not be public.
- Delisted: a previously public version is no longer distributed because of safety, compliance, rights, or other policy concerns.
The real-time status in creation management is authoritative.
What review considers
Review generally covers:
- Accurate representation: the title, summary, and behavior do not mislead users.
- Safety and privacy: the app does not request unrelated access or hide data handling.
- Usability: the primary flow works and does not trap users with fake controls or loops.
- Content compliance: the app does not contain illegal, harmful, infringing, harassing, or deceptive content.
- Publishing quality: the icon, screenshots, description, and links work and match the version.
Approval is not a permanent endorsement. If new risks are discovered, Aelrox may still require changes, limit distribution, or delist a version.
After rejection
- Read the review note and separate required changes from recommendations.
- Address the specific issue instead of only renaming and resubmitting.
- Repeat the pre-submission checklist.
- Save a new version and submit it again.
If the note is unclear or you believe the decision is incorrect, use Feedback and include the micro-app name, version, review time, and your explanation. Keep the report specific and do not disclose sensitive review information in public discussions.
Update a published micro app
When functionality, permissions, data handling, or external links change, update the public description and submit a new version. Whether the current public version remains available while the update is reviewed depends on the product status.
Do not present an unverified major change as a stable capability. Release notes should briefly explain user-visible changes and any necessary transition steps.
Reports and urgent issues
If a published version develops a security, privacy, or serious misrepresentation problem, stop promoting it and report it immediately through Feedback. Do not rely only on a community post for account or payment risks.