With Google's deprecation of Firebase Dynamic Links (FDL) arriving rapidly, the scramble to find a reliable alternative has consumed mobile engineering cycles. A developer on r/SideProject perfectly captured the urgency, sharing how they built a custom Firebase Dynamic Links replacement because existing solutions were too bloated. The thread highlights a massive pain point for app teams everywhere.

Community Spotlight
This post was inspired by a discussion on Reddit: I built a Firebase Dynamic Links replacement
Posted by u/deleted in r/SideProject

The FDL Vacuum

For years, Firebase Dynamic Links was the default, free utility for routing users seamlessly into mobile apps. Whether from an email campaign, an SMS, or a social media bio, FDL handled the complex logic of deferred deep linking. It remembered where a user was trying to go even if they had to install the app first.
Now that the product is deprecated, engineering teams are facing a frustrating choice. As one commenter noted, building a reliable routing service from scratch is technically complex and requires constant maintenance for iOS and Android OS updates.

Why Legacy Alternatives Frustrate Developers

The alternative to building in-house is usually adopting a legacy deep linking provider. However, many teams discover too late that their new measurement provider charges separately for deep linking, enforces steep minimum contracts, and requires weeks of integration work.
A major complaint surfaced in the Reddit discussion is the sheer weight of these SDKs. Developers want a simple routing utility. Instead, they are forced to install massive, legacy attribution SDKs that slow down app startup times and create technical debt.

The Requirements of a Modern Replacement

To successfully replace FDL without breaking user experience or marketing measurement, a solution must handle three core technical requirements perfectly.

• Universal Links and App Links: It must reliably open the installed app without redirecting through the browser when possible.

• Deferred Deep Linking: If the user lacks the app, it must survive the journey through the App Store or Google Play and pass the context payload upon first open.

• Analytics and Attribution: It must tie the routing event to downstream in-app behaviour, revenue, and user acquisition campaigns.

How a Modern MMP Handles This

A well-architected mobile measurement partner would not treat deep linking as a separate, monetised product feature. A modern MMP would unify deep linking and attribution in a single SDK, routing users to the correct in-app destination even through deferred installs, while attributing the source accurately.
Linkrunner, for instance, does exactly this. Built as a direct, unified platform, it makes every generated link dynamic and deferred by default. Rather than forcing developers through a multi-week migration, the SDK integration is typically completed in 2 to 4 hours.

Implementing the Migration

Replacing FDL is a structural change. Growth teams must audit every existing deep link placement.

1. Inventory Links: Export a list of all active FDL URLs used in CRM, paid ads, and social profiles.

2. Map the Payload: Ensure your new provider can accept the same custom parameters and query strings your app expects.

3. Update Domain Configuration: Provision new subdomains and update your Apple App-Site-Association (AASA) and Android Digital Asset Links files.
   The original thread raised a valid point. Developers should not have to choose between building a custom routing engine and paying exorbitant enterprise fees for a bloated SDK. For teams ready to move beyond Firebase with a clean, developer-friendly architecture, Linkrunner unifies attribution and deep linking seamlessly. See how it works at linkrunner.io.