Getting Started
Managing Integration Modules
Enable required native capabilities while keeping unnecessary SDKs and permissions out of a build.
Before you start
- An app project
- A list of required native features and external services
Configure and verify
Open Integration Modules
Review modules available for the selected platform.
Enable a feature
Turn on the module. Its configuration page appears under Active Modules.
Complete required settings
Open the module page, read its contextual documentation, add credentials or assets, and save.
Check readiness
Return to Overview and resolve external SDK warnings before a production build.
Rebuild after dependency changes
Enabling or disabling SDK-backed modules changes generated dependencies and requires a new build.
Default modules
Loading Indicator, Error Screen, Pull to Refresh, and Splash Screen are enabled for new apps.
SDK-backed modules
- AdMob
- AppsFlyer
- Firebase
- Google Sign-In
- Google Play Billing
- Meta SDK
Platform-specific modules
- Android only
- Dynamic App Icon and Google In-App Purchase
- iOS only
- App Tracking Transparency and Apple In-App Purchase
- Both
- Remaining modules, subject to the current iOS worker limitation
Test before release
- Every enabled SDK has valid credentials
- Unused permissions are disabled
- Module URL rules were tested
- A new build follows module changes