Developer FAQ

1. How do I become a developer?

Click "Become a Developer" in the navigation, fill in your developer info (name, email, contact, payout account) and submit. After approval you can publish products.

2. What do I need to publish?

Product name, description, features/scenarios, images or videos, installer/source (client software), and deployment/pricing info for server software.

3. How long does review take?

Products are reviewed as soon as possible and go live after approval; if rejected, check the reason, fix and resubmit.

4. How do I configure licenses?

Enable "license activation" when publishing, set default machine count and self-issue permission; define editions (Basic/Pro/Ultimate by default, editable), choose an upgrade strategy; the system generates a "software API secret".

5. How to integrate in-app payment?

After payment inside your software, sign the request with the software API secret (HMAC), call the open API to generate a license bound to the machine, and users unlock features via the verify API. See the License Open API Document.

6. How is revenue settled?

The Developer Center "statements/revenue" module shows order income, sharing ratios and bills, settled to your payout account per platform rules.

7. Where do I see user feedback?

Product feedback is emailed to your developer email automatically (public email first, otherwise your account email).