How mobile publishing works
From VULK source generation to native packages and your store release.
How mobile publishing works
VULK generates the project source and provides a preview. Native packaging, signing, uploading and store review are distinct stages of the release.
Flutter Android in Studio
Create Flutter project → test preview → set app identity
→ build APK or AAB → sign with the app key → download
→ upload AAB in your Google Play account → testing and reviewIn Dashboard → Mobile app, the build service compiles the project and signs the package. The ready state provides a download and SHA-256 digest. A Play bundle has an increasing version code and the app's upload key, so subsequent releases retain its signing identity.
Flutter iOS from exported source
Export the source, configure the app and signing in your macOS/Xcode environment, create the release archive and upload through your Apple developer account. Follow the Flutter iOS release guide. The current Studio iOS platform choice saves your intended target; it does not start that external archive/signing process.
React Native/Expo
Copy a React Native/Expo project from the VULK gallery and inspect and test it in preview. Export the source for the Expo native build workflow. Configure the identifiers, signing and distribution in your own Expo and store accounts.
Release checks
Check the downloaded package and test it on the target device. Prepare the store listing and required declarations, then use the testing and submission steps offered in your developer account. A preview confirms browser behavior; a native package confirms a build; the store's release status confirms publication.
See Mobile builds for the exact Studio controls and Requirements for release preparation.