Deep links

Every Deskifier app registers a custom URL protocol (set in the dashboard, e.g. myapp://). When a user clicks a link with that scheme — from an email, a browser page, or another app — the OS launches your Deskifier app (or brings it to the foreground if it's already running) and hands the full URL to your web content via the deeplink namespace.

Common uses: OAuth callbacks, magic-link sign-in, "open this specific record" links from your marketing site, invite acceptance flows.

The one method

const unsubscribe = window.deskifier.deeplink.onUsed(({ url }) => {
  // url is the full string the OS handed us, e.g. "myapp://reset?token=abc123"
  const parsed = new URL(url);
  if (parsed.pathname === '/reset') {
    routeTo(`/reset-password?token=${parsed.searchParams.get('token')}`);
  }
});

Register the handler as early as possible in your app's lifecycle — Deskifier queues the URL if the app was launched by a deep link, and fires it as soon as a handler is registered.

Testing locally

Deep links only fire when the OS knows about your protocol, which happens after the app is installed. During development, install a dev build once and every subsequent deskifier dev will honour deep links via the same registered handler.