Fission
Product
▾
Platform overview
Cross-platform apps
Static sites
Server-rendered sites
Terminal apps
Charts
Production lifecycle
Developer tools
Design systems
Blog
Setup
Learn
Build
Test
Publish
Docs
Start
Introduction
Quickstart
Project structure
Add platform targets
Learn Fission
Overview
Runtime model
State, handles, and providers
Rendering pipeline
Layout and widgets
Input, events, text, and environment
State, resources, and async
Theming and internationalisation
Design system
Media, animation, portals, and 3D
Develop
Development workflow
Platform shells and CLI
Platform capabilities
Capability guides
Capability matrix
Notifications
Deep links
NFC
Biometrics
Passkeys
Barcode scanner
Camera and flashlight
Clipboard
Geolocation
Haptics
Microphone
Bluetooth
Wi-Fi
Volume control
Examples and targets
Video calendar
Terminal user interfaces
Static sites
Content routes
Custom static pages
Package static sites
Server-rendered sites
Server data and actions
Server security
Workers and islands
Charts
Charts overview
Catalog
Series and datasets
Data and interaction
Three-dimensional and GL
Test and debug
Testing lifecycle
Testing and diagnostics
Write a live UI test
Build and package
Packaging overview
Desktop packages
Mobile packages
Web packages
Terminal packages
Static site packages
Server site packages
Release and distribute
Release overview
Release content
GitHub Releases
Static hosting
App stores
Docker registries
Object storage
Release lifecycle details
Cookbook
Build a counter
Run typed host work
Keep a timer or service alive
Theme and locale toggle
Modal text flow
Build a documentation site
Build a server-rendered store
Package Docker images
Reference
Reference overview
CLI reference
Widget reference
Chart reference
Home
›
Release and distribute
›
App stores

App store distribution

Store distribution is provider-owned. Fission should orchestrate readiness, metadata validation, package upload, tracks, testers, rollouts, and receipts while using the platform owner's tools and APIs for the provider-specific operation.

1. Package the store artifact

fission package --project-dir . --target android --format aab --release
fission package --project-dir . --target ios --format ipa --release
fission package --project-dir . --target windows --format msix --release

2. Validate release content

fission release-content validate --project-dir . --provider play-store
fission release-content validate --project-dir . --provider app-store
fission release-content validate --project-dir . --provider microsoft-store
Release content includes localized notes, screenshots, preview videos, privacy answers, review attachments, tester groups, rollout settings, and provider-specific listing fields.

3. Check provider readiness

fission readiness distribute \
  --project-dir . \
  --provider play-store \
  --artifact target/fission/release/android/aab/artifact-manifest.json \
  --track internal
Readiness should report missing credentials, package identity mismatches, unsupported tracks, missing first-release setup, invalid screenshots, and provider CLI or API problems before upload.

4. Distribute

fission distribute \
  --project-dir . \
  --provider play-store \
  --artifact target/fission/release/android/aab/artifact-manifest.json \
  --track internal
Use the same pattern for App Store and Microsoft Store providers, changing the provider, artifact, track or flight, and release profile.

5. Keep receipts

Store distribution can involve review, certification, beta tracks, staged rollout, and later status changes. Keep Fission receipts in CI artifacts or release records so the team can see what was uploaded, which provider id was returned, and what follow-up state remains.
1. Package the store artifact
2. Validate release content
3. Check provider readiness
4. Distribute
5. Keep receipts
Setup
Quickstart
Add targets
Project structure
Learn
Overview
Runtime model
Widgets
Design systems
Charts
Build
Platform shells
Terminal UI
Static sites
Server sites
Packaging
Test
Testing lifecycle
Diagnostics
Live UI test
Publish
Release overview
Lifecycle details
CLI reference
Examples
Fission
A cross-platform, GPU-accelerated user interface framework for Rust. MIT licensed.
Copyright (c) 2026 Fission
Ready to use today. Widget APIs are expected to remain stable; some runtime and shell APIs may change before 1.0.0.
GitHub
Quickstart
Reference
main - v0.1.0 alpha