Firebase Dynamic Links shutdown forces deferred deep-link migration

Question

Firebase Dynamic Links is documented as reaching an end-of-service cutoff rather than a gradual API version deprecation, which removes the resolution layer that previously survived app installs. Teams relying on deferred deep linking or link-based attribution face a compatibility boundary where the short page.link host stops redirecting and the console and API surface are withdrawn. Native App Links and Associated Domains remain functional for users who already have the app installed, but they do not restore post-install routing.

The unresolved decision is architectural: implement a self-hosted redirect endpoint that records intended destinations and passes them to the app on first run, adopt a third-party deferred deep-link provider, or drop post-install routing and accept that old links fail for new installs. Existing short links embedded in emails, ads, QR codes, and past shares cannot be rewritten retroactively, so link rot in uncontrolled material is a persistent risk. Any replacement that passes install identifiers also changes the project's privacy and data-processing posture.

Because deprecation dates and console availability move over time, what migration scope is safest for a project that still depends on deferred deep linking? Should the replacement preserve the same user-visible URL structure, or is a controlled domain change acceptable? How should teams confirm that native App Links and Universal Links are fully independent before retiring the Dynamic Links SDK?

Tasadduq Burney · Answer

Recommended Migration Scope
The safest migration scope for projects requiring deferred deep linking is to adopt a new, independent domain and implement a hybrid routing strategy. Because Firebase Dynamic Links (FDL) is a complete service shutdown rather than a version update, the page.link resolution layer will cease to function. Attempting to preserve the same user-visible URL structure is impossible for existing FDL short links, as you do not control the page.link domain.

Architectural Options for Deferred Routing
Since native App Links (Android) and Universal Links (iOS) only function if the app is already installed, you must choose one of the following to restore post-install routing:

Third-Party Attribution Providers: The fastest path to parity. These services manage the fingerprinting and deferred routing logic, though they require updated privacy policies and data-processing agreements.
Self-Hosted Redirects: Implement a custom endpoint that captures the destination and a unique identifier, stores it in a database, and provides an API for the app to query this destination during the first-run sequence.
Acceptance of Link Rot: If deferred routing is non-critical, migrate only to native links. New installs will land on a fallback web page, and only users with the app installed will experience deep linking.

Verifying Native Link Independence
To ensure native App Links and Universal Links are fully operational before removing the FDL SDK, verify that the OS-level handshake is successful. Native links bypass the SDK entirely and rely on domain-hosted configuration files.

Verify Host Files: Ensure your primary domain serves the following files with the correct content-type: application/json:

iOS: /.well-known/apple-app-site-association
Android: /.well-known/assetlinks.json

Test Direct Routing: On a device with the app installed, click a link using your primary domain. It must open the app immediately without triggering a browser redirect or the FDL resolution page.
SDK Isolation: Temporarily disable the FDL SDK initialization code in a staging build. If the app still opens via the primary domain links, the native implementation is independent.

Assumptions and Constraints
This guidance assumes you are using current versions of iOS and Android that support AASA and Digital Asset Links. Note that implementing a custom deferred deep-linking solution on iOS may be limited by App Tracking Transparency (ATT) and the deprecation of IDFA, making precise device matching difficult without a third-party provider.

Missing Diagnostic: Are your existing legacy links embedded in static media (QR codes/Print) or dynamic channels (Email/Push) where you can update the URLs?

Firebase Dynamic Links shutdown forces deferred deep-link migration

1 answer

Recommended Migration Scope

Architectural Options for Deferred Routing

Verifying Native Link Independence

Assumptions and Constraints

Your perspective belongs here.

0 question comments