Dynamic Links shutdown fuels Clerk migrations

The Dynamic Links shutdown matters less as a Firebase auth outage than as a forced re decision point, where teams already touching login flows may decide to swap bundled Google auth for a more polished standalone product. Google kept email link auth alive by moving it onto Firebase Hosting in newer SDKs, but any team still relying on legacy mobile email links, old OAuth flows, or Dynamic Links domains has to update code anyway, which creates an opening for Clerk's fast drop in sign up and sign in UI.

• Clerk is strongest in startup self serve and Next.js style workflows, where developers care about getting auth screens, account management, and passkeys working quickly without stitching together low level primitives. That makes migration most plausible for teams who picked Firebase for convenience, not deep platform loyalty.
  4 sacra 5 sacra 6 clerk
• Firebase is not disappearing. Google replaced the old Dynamic Links based path for email link auth with Firebase Hosting based links in updated SDKs, so many teams will simply patch and stay. The real opportunity is among apps that also want better UI control or were already frustrated by Firebase's more rigid auth architecture.
  1 google 2 google 3 google 5 sacra
• This follows a familiar backend pattern. Firebase won by bundling auth inside a larger developer stack, but as apps mature, teams often unbundle pieces like auth to get better product UX. Clerk sits in that unbundling lane, similar to how Auth0 once pulled auth out of homegrown stacks.
  5 sacra 7 sacra

Going forward, auth winners will capture migrations at moments when developers are already forced into code changes. Firebase will keep winning on free tier and platform bundling, but every forced touch point, whether caused by deprecations, agent support, or passkey rollouts, gives Clerk a chance to convert simple bundled auth users into dedicated identity customers.