App signing and mobile builds
Signing identities for VULK Android packages and exported mobile projects.
App signing and mobile builds
A signing identity lets the platform recognize an app and accept later updates from the same developer.
Android builds in VULK
For a Flutter project, open Dashboard → Mobile app and configure the app identity. VULK builds APK or AAB files and keeps the app's upload signing key for subsequent builds. Each Play bundle receives an increasing version code. The download state includes the artifact's SHA-256 digest.
Upload the AAB to your own app in Google Play Console. Follow the signing and release requirements presented by Google for that app.
iOS and Expo development workflows
Flutter source can be built and signed with macOS/Xcode and your Apple developer account. React Native/Expo source can use Expo tooling and its signing configuration. Configure the signing identity in the tool that performs the native build.
The current Studio mobile panel builds Android packages and records an iOS target preference. Follow Mobile builds and source export for the available path and links to the framework release guides.
Access and release preparation
Use VULK pricing for current feature access and commercial conditions. Use the release checklist for store preparation.