AppsinityAPPSINITY
Builds and uploads

Windows builds

Windows releases ship as a .zip and install through the Appsinity desktop client. .exe and .msi are on the upload denylist, so the archive is the only legal container.

Open Appsinity Studio
On this pagePackagingWhat the listing showsHow the client installs itAuthenticodeFrequently asked questions

Packaging

  1. Build. x64 for Intel/AMD, ARM64 for Snapdragon and Surface. There is no 32-bit path.
  2. Make it self-contained. The client unpacks and runs; it installs no dependencies, no runtime and no VC++ redist.
  3. Put the entry point near the root. The client searches up to three folders deep for the first .exe, skipping names matching unins, uninst, crash, helper, uploader and update.
  4. Zip it. A plain .zip. RAR and 7Z are not accepted.
  5. Upload as an app file or game build. The key becomes apps/{appId}/files/{version}/… or games/{gameId}/builds/{version}/….
Watch out: Name your real executable something specific. MyGame Launcher.exe is skipped as a helper and the client may pick crashreporter.exe instead — which is a filtered name — leaving the game unlaunchable.

What the listing shows

A Windows-targeted listing opened in a browser shows a gate above the button: Download the Windows client to download these games, with an architecture chooser (64-bit / ARM64) and the note For Intel or AMD PCs running 64-bit Windows 10 or 11. The gate is hidden inside the client itself.

  • Set the listing's platform so a PC visitor is not sent an Android package. If the build is Android-only, the page shows Will not install on your Windows PC and the button reads Not available on this device.
  • Supply pcScreenshots and pcFeatureGraphicUrl so desktop visitors see desktop art.
  • The Protection row appears only when licence protection is on, reading License protected - 2 devices - 72h offline by default.
Important: The client's download interception only fires while the page URL matches a listing. A PC user who downloads your archive from anywhere else gets a normal Save-As and no library entry.

How the client installs it

Launch spawns the game detached and records the session in a local play log. See Client library and installs.

Chip textMeaning
DownloadingBytes are arriving; percent is capped at 99 until the file completes
UnpackingThe archive is being expanded
Ready - shortcut on your desktopSuccess
Ready - shortcut blockedInstalled, but Windows refused the shortcut
Download cancelled / Download failedThe transfer did not complete
Could not add to libraryThe manifest write failed

Authenticode

Appsinity does not sign Windows executables. The Android signing pipeline has no Windows equivalent, and nothing here applies Authenticode to your .exe.

Not available: Expect SmartScreen warnings on an unsigned download, especially on a low-reputation file. If your audience is PC-first, sign your own binary before zipping it.

Frequently asked questions

Why can't I upload the .exe directly?

.exe and .msi are denylisted to stop arbitrary executables being served from the store's own domain. The zip is the container, and the client decides what to run.

Do PC listings appear in the Games store?

Yes, in the same rails as mobile titles, but visitors can filter the store grid by Device: All, Mobile, PC, Web.

Where do I get the client for my players?

The gate links /download/Appsinity-Setup.exe. If that link 404s, tell [email protected] — the installer filenames have moved before.

Related documentation

Windows desktop clientLicences and protected downloadsAPK versus AABUpload a build
Need help?

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