One-Time App Setup
Prepare your app and domains once so ZipQuantum links can open the correct destination safely across install states.
Purpose
The one-time app setup connects your mobile application, verified domains, and store fallbacks. Complete it before using Smart Links in production.
What This Setup Changes
- Your app is authorized to open links from the domain you configure.
- Supported in-app destinations are mapped to stable routes.
- Visitors without the app receive an appropriate App Store, Google Play, or web fallback.
ZipQuantum does not require an SDK, background service, or runtime interception.
Prerequisites
- Access to the iOS and/or Android application project.
- The application identifier for each platform.
- Access to the verified web domain and its association files.
- The production App Store and Google Play listing URLs, when applicable.
Setup Checklist
- Register the application and its platform identifiers in the ZipQuantum dashboard.
- Choose the domain that will be used by production Smart Links.
- Configure iOS Universal Links for the domain if you support iOS.
- Configure Android App Links for the domain if you support Android.
- Map the supported link paths to routes in your application.
- Add store and web fallbacks for unsupported or non-installed states.
- Deploy the platform association files over HTTPS.
- Install a production-like build and run the tests in the next guide.
Platform Guides
- Use iOS — Universal Links for Associated Domains and the Apple association file.
- Use Android — App Links for intent filters and the Android association file.
- Use Flutter or React Native for framework-level route handling after the native platform association is working.
Expected Result
A supported Smart Link opens the mapped route when the app is installed. When the app is unavailable, the same link follows the configured store or web fallback.
Safety Checks
- Keep association files publicly readable over HTTPS without authentication or redirects.
- Use exact production identifiers; development and production signing identities may differ.
- Do not place secrets, tokens, or private user data in link paths or query parameters.
- Test fresh installations as well as already-installed applications.