Firebase Dynamic Links Are Shutting Down – What’s Next for Notifications & Deep Linking?

Introduction

Firebase Dynamic Links (FDL) have long been a go-to solution for developers looking to create seamless deep linking experiences across mobile apps, websites, and multi-channel notifications. Whether through push notifications, SMS, or email, FDL allowed apps to direct users to the right in-app content, even handling complex scenarios like deferred deep linking for new installs.

However, Google has officially announced that Firebase Dynamic Links will be fully shut down on August 25, 2025. This means that any links powered by FDL will stop working after that date, potentially causing major disruptions for developers who haven’t migrated to an alternative solution.

In this post, we’ll explore the impact of this deprecation, its consequences for deep linking in notifications, and how developers can transition to new deep linking strategies.

Why Firebase Dynamic Links Mattered

FDL was a critical tool for developers because it simplified the deep linking experience across multiple platforms and communication channels. Some of its key benefits included:

• Seamless Deep Linking: Whether a user was coming from a push notification, SMS, or email, FDL ensured they were directed to the right in-app content, regardless of whether they had the app installed.
• Deferred Deep Linking: Users who didn’t have the app installed were first sent to the App Store or Play Store. Upon installation, FDL continued the deep link journey, opening the intended content.
• Multi-Channel Support: FDL worked well across push notifications, SMS marketing, and email campaigns, making it a versatile option for user engagement and retention.
• Tracking & Analytics: Firebase provided insights into link performance, user acquisition, and conversion tracking.

The deprecation of FDL means that developers now need to rethink how they handle deep linking across these critical channels.

The Impact of the Sunset

The shutdown of Firebase Dynamic Links comes with several major challenges:

• Existing Links Will Stop Working: After August 25, 2025, all FDL-powered links will break, meaning they will no longer open apps or redirect users as expected.
• Deep Linking in Notifications at Risk: Push notifications, SMS, and emails that rely on FDL will fail to direct users correctly, leading to broken experiences and potential drops in engagement.
• Google’s Migration Recommendations Have Limitations: Google suggests transitioning to Android App Links and iOS Universal Links, but these come with setup complexities and may not fully replace all of FDL’s capabilities.
• Impact on Deferred Deep Linking: Without FDL, developers need alternative solutions to handle deep links when a user installs the app for the first time.

With this in mind, it’s crucial for teams to explore and implement new deep linking strategies before the deadline.

What’s Next for Deep Linking in Notifications?

Push Notifications

To ensure deep links continue to work in push notifications:

• Replace FDL with Android App Links and iOS Universal Links.
• Update your notification payloads to use these new links.
• Ensure your app is properly configured to handle incoming deep links.

SMS Links

For SMS-based deep links:

• Use custom short links pointing to your own domain.
• Implement a redirect service that detects whether the user has the app installed and routes them accordingly.
• Consider third-party deep linking services that offer better tracking and install attribution.

Email & Other Channels

For email and cross-platform deep linking:

• Utilize universal deep links that work across platforms.
• Ensure web fallback pages are properly set up for users without the app installed.
• Maintain tracking capabilities using tools like UTM parameters or third-party deep link platforms.

Alternative Deep Linking Solutions

As Firebase Dynamic Links are phased out, developers have several alternative deep linking strategies:

1. Apple Universal Links & Android App Links

These native deep linking mechanisms are Google’s recommended approach. However, they require:

• Hosting apple-app-site-association and assetlinks.json files.
• Configuring app entitlements and intent filters.
• Ensuring proper handling within your app’s routing system.

Pros:

• Direct linking without intermediary redirects.
• Secure and verified deep linking.

Cons:

• No built-in deferred deep linking (unlike FDL).
• Setup requires changes to both the app and backend infrastructure.

2. Third-Party Deep Linking Platforms

Many third-party deep linking services offer alternatives to FDL, including:

• Branch
• Adjust
• AppsFlyer

Pros:

• Feature-rich platforms with analytics, deferred deep linking, and attribution.
• More flexibility than Google’s native solution.

Cons:

• Often require paid plans.
• Vendor lock-in concerns.

3. Building a Custom Deep Linking Infrastructure

If your use case demands complete control, consider building a self-hosted deep linking system:

• Use URL shortening services with custom tracking parameters.
• Implement backend logic to detect and route users.
• Create web-based fallbacks for users without the app.

Pros:

• Full control over deep linking behavior.
• No reliance on third-party services.

Cons:

• Requires engineering resources.
• More complex setup and maintenance.

Conclusion

Firebase Dynamic Links are shutting down on August 25, 2025, and developers need to act now to avoid disruptions. The key takeaways:

• All Firebase Dynamic Links will stop working after the shutdown date.
• Push notifications, SMS, and email campaigns must transition to alternative deep linking solutions.
• Google recommends App Links & Universal Links, but third-party services offer additional capabilities.
• Courier helps developers manage deep linking across multiple notification channels.

To ensure your deep linking strategy remains intact, start planning your transition today. Whether using platform-native links, third-party providers, or a custom solution, taking action before the deadline will prevent broken experiences and lost user engagement.