What is this?
The App Setting tab prepares your platform’s branded mobile app. The app is built with Capacitor, which runs your web platform inside native Android and iOS apps while still supporting native features such as push notifications — so you don’t maintain separate codebases. Use this tab to set the app’s identity, upload its branding and Firebase configuration files, set up signing, and trigger builds for the Play Store and App Store.
Mobile app builds must be included in your plan. If they aren’t, the Build section explains that the feature is unavailable and asks you to contact support or purchase the add-on.
What can I do here?
- Set the App Name, App Version, Android Package ID, and iOS Bundle ID
- Choose Primary Color and Secondary Color to match your brand
- Upload the App Icon and Splash Screen
- Upload the Firebase configuration files: Google Services (Android) and Google Services (iOS)
- Add your App Store URL and Play Store URL once the apps are published
- Set custom Android Signing details (optional)
- Connect your Apple Developer account for iOS Signing
- Start a Build for Android, iOS, or Both, watch the build logs, and download the APK, AAB, or IPA
- Review the Store submission & data collection checklist for Apple and Google
How to use it
1. Add the app to Firebase
Create Android and iOS apps inside your Firebase project so the mobile app can use notifications and sign-in. Firebase gives you two configuration files:
Upload these under Google Services (Android) and Google Services (iOS). See Firebase Settings for the project setup itself.
2. Set the app identity and branding
- Go to Platform Settings → App Setting and click Edit Settings.
- Enter the App Name, App Version, Android Package ID (for example
com.example.app), and iOS Bundle ID. - Choose the Primary Color and Secondary Color, then upload the App Icon and Splash Screen.
- Add the App Store URL and Play Store URL when your apps are live.
- Click Save.
3. Set up signing
- Android
- iOS
Under Android Signing, default auto-signing is generated by the system. Fill in Keystore Base64, Keystore Password, Key Password, and Key Alias only if you want custom signing, then click Save Android Signing. If you publish with Google’s default Play App Signing, you usually don’t need this.
4. Build the app
- In the Build section, choose Android, iOS, or Both.
- Click Trigger Build and follow progress in the log panel. Use Refresh to update the build status.
- When the build finishes, download the APK or AAB (Android) and IPA (iOS).
5. Prepare your store listing
Building the app is separate from publishing it. Both stores require you to declare what data your app collects.- Apple App Store — App Privacy: declare contact info, user content, photos and videos, audio, location (only if used), and device identifiers such as the push notification token.
- Google Play — Data safety: in Play Console, complete Policy → App content → Data safety.
- Also required: a public privacy policy URL, store screenshots for the required sizes, app name and descriptions, and a support URL and contact email.
Troubleshooting / Technical Notes
- “Mobile app builds are not included in your current plan.” Contact support or purchase the mobile builds add-on.
- Notifications don’t work in the app. Confirm both Firebase files were uploaded and that the Firebase apps use the same package ID and bundle ID you entered here.
- You can’t connect your Apple Developer account. The App Store Connect API key needs App Manager access, and the
.p8file can only be downloaded once when you create it. - The Build buttons are disabled. The buttons follow your plan’s build eligibility — your plan may not allow that platform, or you may have no build triggers remaining.
- The store rejects the app. The App Privacy and Data safety answers must match your actual app behaviour.