Why we build Fox Store
Publishing an app may look like uploading a package, but in practice you repeatedly switch between local tools, developer resources, store consoles, testing channels, and error logs. Every platform has its own terminology, permissions, and constraints. When something fails, what is usually missing is an explanation of what happened and what to do next, rather than another button.
Fox Store aims to turn this work into publishing infrastructure that can be inspected, recovered, and traced. It is not a general-purpose CI platform and does not try to replicate every official console. A headless Engine unifies Provider capabilities, the desktop client offers the complete workspace, and the CLI hands deterministic publishing steps to your team's existing CI/CD.
Our principles
Local first
Provider credentials, certificate private keys, packages, task records, and release assets are stored on your computer first. Packages you publish are uploaded directly to the target Provider, without passing through a Fox Store-operated relay.
Official workflows first
When an official API or local tool is available, we do not maintain a hidden private upload protocol. If a platform offers no public capability, the interface explains the limitation instead of pretending data is synchronized.
Explain before asking for action
High-risk operations must explain their impact. Failed uploads should preserve stages, responses, and actionable suggestions wherever possible. Buttons on the same page should not all compete for attention.
Current scope
Apple App Store is currently the most complete publishing workflow. Google Play, Huawei AppGallery, WeChat Mini Programs, Tencent MyApp, Honor, Samsung, Pgyer, vivo, Xiaomi, and OPPO are connected as independent publishing Providers. Alibaba Cloud OSS, Tencent Cloud COS, Amazon S3, and MinIO are object storage Providers. Each platform retains its actual terminology and capability differences. Fox Store does not handle legal agreements, commercial contracts, or official console operations not covered by public APIs.
What's next
Our first priority remains making “connect a Provider → import a package → preflight → official upload → view results” reliable. Image optimization, AI app checks, reviews, and Analytics add publishing context around this workflow. See Pricing and the Refund Policy for pricing and purchase policies, and Licensing and activation for license details.
Contact us
For product feedback, licensing, or after-sales support, email the contact address in the footer. Include your Waffo order number or the last four characters of your license Key where possible; do not send the full Key.