AppsinityAPPSINITY
Getting started

Create a developer account

A developer account is created at Studio and verified by email. Nothing else — no payment method, no company record — is required before you can publish.

Open Appsinity Studio

The registration fields and their real limits

FieldRule enforced by the APINote
EmailMust be a valid address and must be verifiableThe OTP is sent to it; a wrong address locks you out of the account
Display nameTruncated to 120 characters on profile updatesUsed for the publisher name shown on listings
PasswordMinimum 6 charactersHashed with bcrypt cost 12; there is no complexity rule
Account typeSet to user for store sign-upsDeveloper accounts are created through Studio
Marketing consentDefaults to offSee Mail preferences
Note: Six characters is a low floor. Because Studio can publish and delete builds, use a password you do not reuse anywhere; the account is the only gate between an attacker and your users' downloads.

Email verification

On sign-up the API generates a 6-digit numeric code in the range 100000–900000, hashes it, and emails it. The code expires after 10 minutes. Verification is a separate step from registration: the account exists before the code is entered.

  • There is no rate-limited resend delay on the OTP endpoint, so asking for several codes in a row is possible — but only the newest hash is valid.
  • If the code never arrives, check spam first, then the address itself. A typo in the email is not recoverable from inside the dashboard.
  • Verification state is stored on the account and surfaced as emailVerified.

What the account can do immediately

Payouts are the exception: they require the merchant and tax information described in Merchant account and Taxes, and the earnings dashboard stays locked until the app reaches 20,000 visits.

  • Create projects and edit every section of them.
  • Upload builds to storage and trigger signing.
  • Publish, unpublish and delete its own apps.
  • Read analytics for its own apps.
Watch out: There is no two-step verification for developer accounts today. See Two-factor authentication for the honest state and the compensating controls.

Individual versus organisation

An individual account publishes under the display name you chose. An organisation account exists so the publisher name is the company rather than a person, and is required when you want team seats under a shared owner. The two behave identically in the store; the difference is account metadata and who can delete the account.

See Organisation account and Developer profile.

Frequently asked questions

Can I have more than one developer account?

Nothing prevents it, but a second account for the same product breaks team roles and payout attribution. Use one account and add members instead.

How do I change the email on the account?

There is no self-service email change. Contact [email protected] from both the current and the new address so the request can be matched.

Why does the store keep asking me to verify my email?

Store sign-up requires the OTP step to complete before the finish panel appears. Enter the code, then choose a username and picture — see Username and avatar.

Need help?

Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]