PublishKit

Developers building mobile apps through browser-based tools still need to manage distribution certificates, provisioning profiles, beta builds, versions and store submission states. The supplied research confirms an active official distribution API and event webhooks, plus adjacent integration and automation products. It did not find the exact standalone dashboard in its reviewed set.

PublishKit connects with least-privilege account access and inventories certificate metadata, profile metadata, bundle identifiers, builds, beta states, app versions and submission events. It favors read-only monitoring. Private signing keys should remain in the customer's controlled signing or build environment; the dashboard stores only the minimum identifiers and expiry information needed for alerts.

Observed state, alert, operator acknowledgment, renewal request, credential creation, build upload, submission authorization, platform receipt, review decision and public release remain separate. A webhook can be delayed or duplicated, an expiry alert does not renew anything and an accepted upload does not guarantee review approval.

The first release should support one official account interface and manual runbook links. Any write action requires explicit scoped authority, preview and readback. The product wins on reliable visibility, not one-click publishing or control of secrets.

Independent mobile developer or small product team using browser-based build services and managing its own app distribution account