Auditable, agent-first reference integrations for direct and deferred deep links.
 |  |
| One verified link Universal Links and App Links open the intended route. | Intent survives install Native, explicit handoff restores the destination. |
These examples use platform APIs directly:
- no proprietary ZipQuantum SDK;
- no fingerprinting or cross-app user identifier;
- signed, short-lived handoff receipts;
- explicit clipboard recovery on iOS;
- aggregate funnel acknowledgements only after the destination route opens.
| Platform | Direct deep link | Deferred deep link | Route acknowledgement |
|---|---|---|---|
| SwiftUI | Universal Links | UIPasteControl user action | Signed route_ack receipt |
| Kotlin | Verified App Links | Google Play Install Referrer | Signed route_ack receipt |
| React Native | Linking + verified HTTPS links | Native UIPasteControl / Install Referrer adapters | Signed route_ack receipt |
| Flutter | app_links + verified HTTPS links | Native UIPasteControl / Install Referrer adapters | Signed route_ack receipt |
The sample identifiers and hosts are placeholders. Replace them with values verified in your ZipQuantum dashboard before running an app.
Start with AGENTS.md, then read the machine-readable mobile contract, AI manifest, and agent integration guide. Every verification command is non-interactive, uses stable ZQ_* output prefixes, and returns a non-zero exit code on failure.
./scripts/validate.shThe apps call the public endpoints documented in docs/mobile-contract.md. The server resolves routing and issues a host- and app-bound acknowledgement receipt. Apps never manufacture or decode this receipt.
See SECURITY.md. Device context is optional and coarse. Do not add advertising identifiers, pasteboard reads at launch, device fingerprinting, or a locally generated substitute for a server receipt.
MIT
