Skip to content
Praxical Store
Start here

Publish your first app

From a publisher workspace to an approved, signed release.

Create your publisher workspace

  1. Sign in with Sapphire Accounts and create a publisher organization. Complete the publisher application and wait for an independent review.
  2. Open For developers, select your organization, and create an app. Choose its permanent reverse-DNS application ID, store address, release family and initial offer.
  3. Prepare the listing with a clear description, permissions, support and source links, license declaration, screenshots and an icon. Owners and release managers can edit the app; billing and signing controls require their specific roles.

Prepare an installable release

A release binds its version, channel, release family, compatibility requirements, permissions and exact artifact digests. Choose community access for a free build or official access for builds that require a commercial entitlement. AppDir is the validated installation profile in this preview; a listed package format does not imply that every client can install it.

  1. Create a draft in the app’s Releases tab. Select the release family and channel, then enter the version and meaningful release notes.
  2. Upload the package. Complete the upload before requesting validation. The worker inspects the archive in an isolated process and records its profile, entries and expanded size.
  3. Review validation output and correct failures. A change to release inputs invalidates the previous approval. Initial app review is independent of publisher package signing.
  4. For an approved release, review publication preflight, then publish now or schedule its approved revision. Publication completes asynchronously when signed metadata is ready.

Keep the trust boundaries clear

The publisher’s Ed25519 assertion proves control of a registered publisher key. Praxical’s TUF metadata authorizes distribution of an approved target. Neither proves that a build is reproducible. A desktop client independently verifies its trusted root, current metadata, target length and hash, package limits and host requirements before installation.

This is an implemented preview contract. Commercial onboarding, real identity registration, independent client compatibility and production activation remain separate readiness gates.