ZipQuantum Documentation

Everything you need to use Smart Links, Deferred Deep Linking, and QR Smart Codes — safely.

No proprietary SDK · No fingerprinting · Privacy-first

Create your first Smart Link in minutes

API integration, parameters, and error handling

Endpoints, parameters, and platform behavior.

Docs

React Native

Connect ZipQuantum’s verified HTTPS links to React Native navigation without a ZipQuantum-specific SDK.

Current ZipQuantum Integration Model

ZipQuantum requires no proprietary React Native SDK. React Native receives the HTTPS URL through the native iOS Universal Link or Android App Link configuration.

Prerequisites

  • The iOS and Android native association checks pass for the exact production host.
  • The Smart Link has the required mobile package, store, and fallback settings.
  • The application has a stable mapping between URL paths and navigation screens.

Configure React Navigation

When the app uses React Navigation, add the exact ZipQuantum production host to the linking prefixes and map supported paths explicitly.

const linking = {
  prefixes: ['https://your-production-host'],
  config: {
    screens: {
      Home: '',
      Product: 'product/:id',
      Campaign: 'campaign/:code',
    },
  },
};

<NavigationContainer linking={linking}>
  {/* navigators */}
</NavigationContainer>

Native Project Requirements

  • On iOS, configure Associated Domains for the application target and the exact host.
  • On Android, configure an auto-verified HTTPS intent filter for the exact host.
  • Ensure the Android activity can receive a new link while the app is already running.
  • Rebuild and reinstall the native applications after changing entitlements or manifest declarations.

URL Handling Rules

  1. Allow only the production prefixes controlled by your application.
  2. Map only documented paths to screens.
  3. Parse identifiers and query values with explicit validation.
  4. Send unknown paths to a safe screen rather than executing arbitrary navigation.
  5. Handle both the initial URL and URLs received while the app is active.

Test With ZipQuantum

  1. Create a Smart Link whose path matches a configured React Navigation screen.
  2. Install a production-like build.
  3. Tap the Smart Link from a message or browser on another domain.
  4. Confirm the correct screen for cold-start and already-running states.
  5. Remove the app and verify the ZipQuantum store or web fallback.

Deferred Recovery

React Navigation handles installed-app URLs. For fresh installs, integrate Play Install Referrer on Android and the signed, user-initiated handoff on iOS, then submit the opaque token to ZipQuantum’s public recovery endpoint. No privileged API secret belongs in the application bundle.

Troubleshooting

  • The app opens but navigation does not change: compare the incoming path with the linking.config map.
  • A warm app ignores the link: verify the activity launch behavior and the URL subscription.
  • Only iOS or Android works: return to the corresponding native guide and verify the host association.
  • Multiple handlers fire: use one authoritative link-to-navigation flow.

Get Started

Create your first ZipQuantum Smart Link in minutes — no proprietary SDK, no fingerprinting, and no attribution stack.

ZipQuantum links are install-aware by design.
They work before install, during install, and after install — using standard platform mechanisms only.

What You’ll Do Here

In this section, you’ll learn how to:

  • Create a Smart Link from the dashboard

  • Configure install-safe routing

  • Verify correct behavior across install states

  • Deploy links to production safely

No SDK integration is required.
No runtime interception.
No background services.

Prerequisites

Before you begin, make sure you have:

  • A ZipQuantum account

  • Access to your app’s App Store / Play Store listing

  • A destination URL or in-app route you want users to reach

That’s it.

Next Step

Create Your First Smart Link

This guide walks you through:

  • Creating a link

  • Testing install vs non-install behavior

  • Sharing it safely across channels