Developer Formatting & Upload Guidelines
Thank you for choosing to publish your extension on our store. To ensure a smooth review process, please follow formatting rules strictly. Our store supports both desktop and specific mobile app implementations.
1. The manifest.json Requirement
Your extension archive (.zip, .crx, .xpi) must contain a valid manifest.json in its root directory. Our automated parser extracts metadata from this file.
name: Overrides the manual title (if manual title is empty).version: Auto-tracked. New updates create version history archives automatically.permissions&host_permissions: Parsed and displayed to the users.
Note: We strictly monitor for dynamic execution codes such as
eval() or document.write(). Inclusion of these will flag the extension as malicious and it will be rejected.
2. Format for Mobile Usage
If your extension is designed to run in Kiwi Browser, Yandex, or other Android apps that support Chrome extensions:
- Ensure responsive UI for popup actions (max width 350px).
- Include touch event handlers where necessary instead of relying entirely on
clickorhover. - Add a manifest note or store description clearly stating mobile compatibility.
3. Review Process & Statuses
We use a robust 5-state system for extensions:
- Pending: Awaiting manual review.
- Reviewing: An administrator is currently checking your source code.
- Approved: Live on the store and searchable!
- Rejected: Review failed. You will receive an automated email detailing the specific rejection reason.
- Taken Down: Forcefully removed after approval for policy violations.
4. Developer Verification (Blue Tick)
Active and trusted developers are granted verified status visually on their extensions. Keep a clean record of approvals and maintain active extensions to become eligible.