Recover the links that still matter, map their destinations to structured Ferry payloads, then validate both the direct-open and first-install journeys before cutting over.
Read the full guideFrom the Ferry team
Notes from the route.
Clear thinking about deep links, attribution, mobile growth, and building integrations that both humans and coding agents can understand.
How to move from Firebase Dynamic Links to Ferry.
A practical, post-shutdown plan for rebuilding links, moving a custom domain, replacing the mobile integration, and validating deferred deep linking.
Read the guide THE LATEST
Ideas worth carrying forward.
How to move from Firebase Dynamic Links to Ferry.
A practical, post-shutdown plan for rebuilding links, moving a custom domain, replacing the mobile integration, and validating deferred deep linking.
+
What should replace Firebase Dynamic Links?
A concise map of the routing, deferred matching, domain, and attribution capabilities a replacement needs.
+
Start from the user journey rather than the short-link feature list, then choose a replacement that covers the app, store, install, and measurement paths.
Read the full guide How to move from Branch to Ferry.
A migration guide for teams leaving Branch over pricing: what actually drives the MAU bill, how Branch concepts map to Ferry, and why your routing code stays the same.
+
Audit what Branch actually meters, rebuild your links and domain in Ferry, then swap the SDK calls that produce a payload without touching the router that reads it.
Read the full guideNo posts in this topic yet.
PUT IT INTO PRACTICE
Build the link journey once. Learn from every open.
Connect an SDK or hand the integration to your coding agent.
Read the docs