Browser Handoff Landing

Use the existing app domain only when all of these are true

• The user explicitly wants it under that app.
• The route will not be swallowed by SPA fallback or service worker behavior.
• The target is simple and there is no reason to isolate it.

Implementation workflow

1. Inspect the current site for SPA redirects, service workers, and route handling.
2. Decide whether the page belongs inside the app or as a standalone site.
3. Build the smallest page that satisfies the request.
4. Add browser handoff logic only if the user asked for forced escape from in-app browsers.
5. Verify the final target URL itself is healthy before blaming the page.
6. If Netlify is involved, prefer a separate site for a separate landing page.

Browser handoff logic

Detect likely in-app browsers from the user agent:

• YouTube
• FBAN, FBAV, FB_IAB
• Instagram
• Messenger
• TikTok
• Android WebView markers like wv

iPhone best-effort handoff

• Try googlechrome://navigate?url=...
• Then try x-safari-https://...
• Always show manual fallback steps because iOS may ignore the handoff attempt

Android best-effort handoff

• Prefer a Chrome intent URL: