Deep links that open the right screen: production checklist for Expo apps

UpdatedSeptember 7, 2026

Password-reset emails, referral invites, and order confirmations all end the same way: a link that should land on the right screen. In development the link works because the simulator is warm, the session is fresh, and you tap it from the same device. In production it breaks because the app was killed, the session expired, or the user pasted the link into a notes app first.

Deep linking is not one feature. It is three layers that have to agree: the operating system deciding your app owns the URL, the router mapping that URL to a screen, and your app handling whatever state it wakes up in. When AI coding tools scaffold the router for you, the middle layer looks done while the other two are still missing. This post closes that gap for Expo apps built with Expo Router.

This is an excerpt. Read the full post at otf-kit.dev/blog/deep-linking-expo-production-checklist — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

#react-native #cross-platform

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

React Native cold start drops when Hermes, lazy screens, and trim bundles ship together

Cold start is the first promise your app makes. A user taps the icon, the splash shows, and then there is a gap — sometimes half a second, sometimes three — before anything usable appears. Most of tha

Sep 9, 20261 min read

React Native cold start drops when Hermes, lazy screens, and trim bundles ship together

Supabase migrations ship safely when every change is reversible and tested first

Shipping a mobile app backend feels calm until the day a schema change locks your users out. On the web you can deploy, migrate, and roll forward in one pipeline. On mobile you cannot. Old app version

Sep 9, 20261 min read

Supabase migrations ship safely when every change is reversible and tested first

Expo push notifications arrive reliably when tokens, receipts, and retries are wired right

Push notifications are the one feature that fails silently. When a chat message, a delivery update, or a reminder never arrives, the user does not file a bug report. They just stop trusting the app. A

Sep 9, 20261 min read

Expo push notifications arrive reliably when tokens, receipts, and retries are wired right

Biometric enable in Expo apps ships when every fallback is handled

Why biometrics belong in your auth flow Passwords are the weakest link in most mobile apps. Users reuse them, forget them, and abandon sign-in screens that demand them too often. Biometric authenticat

Sep 9, 20261 min read

Biometric enable in Expo apps ships when every fallback is handled

Crash triage that ships fixes: read every Sentry issue like a release engineer

Every AI-built app reaches the same Tuesday morning. The Sentry inbox grew overnight, the loudest crash is something obscure on an old Android build, and nobody knows which issue deserves the next hou

Sep 9, 20261 min read

Crash triage that ships fixes: read every Sentry issue like a release engineer

OTF — kits your AI coding agent can ship to production

540 posts

Engineering notes on shipping production apps with AI coding tools — Claude Code, Cursor, Codex, Lovable, Bolt — and the stack underneath: React Native, Expo, Next.js, Supabase. Honest takes on what works, what breaks, and the full-stack kits that get you to production faster. By OTF.

Command Palette

Comments

More from this blog