Firebase Dynamic Links alternative: Brevily
Google shut down Firebase Dynamic Links. Move your app links to Brevily: what each feature maps to, the migration steps, and what changes for users.
<p>If you're looking for a Firebase Dynamic Links alternative, Brevily's deep links do the jobs most app teams used them for. One short link opens your app at the right screen, sends people without the app to the App Store or Google Play, and keeps that screen through the install. Google shut Dynamic Links down on 25 August 2025 (its Dynamic Links FAQ, read 18 October 2026), so the links in your emails, posts and printed codes need a new home.</p>
<p>Moving means adding your app once and recreating your links. On a domain you own, the old addresses can even keep working.</p>
<blockquote><p><strong>Before you start:</strong> read <a href="/guides/deep-links-to-app-screens">deep links to app screens</a> for how a link opens an app, and ask your app developer for its details. Deep links depend on your plan; see <a href="https://brevily.com/pricing">pricing</a>.</p></blockquote>
<h2>A Firebase Dynamic Links alternative, job by job</h2>
<ul>
<li><strong>A short link on Google's domain or your own:</strong> a Brevily short link on your own domain, or on the shared <code>brvl.app</code>.</li>
<li><strong>Open the app at a path:</strong> a deep link on the link, with the <strong>App</strong> and the <strong>Path in the app</strong>, such as <code>/offers/autumn</code>.</li>
<li><strong>Send a phone without the app to the store:</strong> set <strong>Without the app</strong> to <strong>The app store</strong>, or to <strong>The link's destination</strong> for your web page.</li>
<li><strong>Carry the link into a fresh install:</strong> on Android, through the Google Play install referrer. On iPhone, when the visitor taps <strong>Get the app</strong>, which copies the link for the app's first launch. Brevily never guesses from the device.</li>
<li><strong>A preview card in chats and social posts:</strong> your own title, description and image per link, with <a href="/guides/custom-link-previews">custom link previews</a>.</li>
<li><strong>Clicks and app opens by platform:</strong> each link's stats by country, device and system. On plans with website and app keys, your app can report its opens and installs for links on your own domains.</li>
</ul>
<h2>How to move from Firebase Dynamic Links to Brevily</h2>
<ol>
<li><strong>Add your app.</strong> In <a href="https://console.brevily.com/mobile-apps"><strong>Link setup</strong> › <strong>Mobile apps</strong></a>, choose <strong>Add an app</strong> and fill in what it <strong>Opens with</strong> and its store addresses, for iOS and Android.</li>
<li><strong>Connect your domain.</strong> Add it under <a href="https://console.brevily.com/domains"><strong>Link setup</strong> › <strong>Domains</strong></a>; see <a href="/guides/own-domain-for-short-links">own domain for short links</a>.</li>
<li><strong>Recreate your most-used links first.</strong> On <a href="https://console.brevily.com/links/new"><strong>New link</strong></a>, fill in the <strong>Destination</strong>, then the <strong>Deep link</strong> section, and choose <strong>Create link</strong>.</li>
<li><strong>Bring in the rest.</strong> <strong>Links</strong> › <strong>Import CSV</strong> creates many links at once (see <a href="/guides/import-links-from-bitly">import links</a>). The CSV has no deep-link column: links take their folder's app and screen if its preset sets one, and you give each its own screen on the link's <strong>Routing</strong> tab, under <strong>Deep link</strong>.</li>
<li><strong>Update the app.</strong> Your developer adds the first-launch code from <a href="/developer-guides/deferred-deep-links">deferred deep links</a>, and Universal Links and App Links from <a href="/developer-guides/add-a-mobile-app">add a mobile app</a> if your plan includes them.</li>
<li><strong>Test on real phones,</strong> with and without the app.</li>
<li><strong>Swap the links</strong> wherever you can still edit them.</li>
</ol>
<p>[screenshot: the New link page's Deep link section with App, Path in the app and Without the app]</p>
<h2>Keep your old link addresses working</h2>
<p>If your Dynamic Links used a domain or subdomain you own, point it at Brevily and recreate each link with the same back-half. The old addresses then work again, printed QR codes included. A back-half can carry a path in front, such as <code>go.example.com/promos/autumn</code>, on plans with paths in links.</p>
<ul>
<li><strong>Does the domain also serve a website?</strong> Pointing it at Brevily moves the website too, so use a subdomain kept for links.</li>
<li><strong>Links on Google's own domain</strong> can't be moved: that domain isn't yours to point elsewhere. Replace them wherever you can.</li>
</ul>
<h2>What changes for people who tap your links</h2>
<ul>
<li><strong>Android, app installed:</strong> the app opens at the screen straight away.</li>
<li><strong>iPhone, app installed:</strong> a short page on your link's domain offers <strong>Open in the app</strong>, one tap. With Universal Links set up on your own domain, the app opens directly instead.</li>
<li><strong>No app:</strong> the store or your web page, as you chose for that link. With the store, the screen survives the install on Android, and on iPhone for anyone who taps <strong>Get the app</strong>.</li>
<li><strong>Computers:</strong> your web page, as for any link.</li>
<li><strong>Privacy:</strong> a short link sets no cookie, so it needs no consent banner.</li>
</ul>
<h2>A migration, start to finish</h2>
<p>Say a shop's app has an offer link in its newsletter and a QR code on its delivery boxes, both on <code>go.example.com</code>.</p>
<ol>
<li>The app goes into <strong>Mobile apps</strong> once, and <code>go.example.com</code> is connected under <strong>Domains</strong>.</li>
<li>The box link is recreated with its old back-half, so every box already printed opens the app again.</li>
<li>The newsletter link is recreated with <strong>The app store</strong> as its fallback, so new users land on the offer after installing.</li>
</ol>
<p>On <a href="https://console.brevily.com/analytics"><strong>Traffic</strong></a>, the <strong>App</strong> filter then shows those links beside every other click.</p>
<h2>Common questions</h2>
<h3>Do old Firebase Dynamic Links still work?</h3>
<p>No. Google shut the service down, and old Dynamic Links return a 404 (Google's Dynamic Links FAQ, read 18 October 2026). Links on a domain you own can work again through Brevily.</p>
<h3>Do I need an SDK or app changes to replace Firebase Dynamic Links?</h3>
<p>No SDK: Brevily has none yet, and deep links don't need one. The app only needs to handle its own <code>exampleapp://</code> links; the screen after an install takes a few lines more.</p>
<h3>Can I import my Firebase Dynamic Links into Brevily?</h3>
<p>Yes, with <strong>Links</strong> › <strong>Import CSV</strong>, on plans with bulk import. The CSV has no deep-link column: links take their folder's app and screen if its preset sets one, and you give each its own screen on the link's <strong>Routing</strong> tab.</p>
<h2>Next steps</h2>
<ul>
<li><a href="/guides/deep-links-to-app-screens">Deep links to app screens</a>: set the app, the path and the fallback on a link.</li>
<li><a href="/developer-guides/deferred-deep-links">Deferred deep links</a>: for your developer, the right screen after an install.</li>
<li><a href="/guides/own-domain-for-short-links">Own domain for short links</a>: keep old addresses working.</li>
<li><a href="/guides/import-links-from-bitly">Import links</a>: bring many links in from a CSV.</li>
<li><a href="/developer-guides/brevily-api">Brevily API</a>: do the same from your own code.</li>
</ul>