But then I would be maintaining 2 repos one mono repo Laravel+React and another one for RN. Also I would have to maintain 2 endpoints for each action (one for web and another one for app).

The problem doesn't end here, the content on the website was not made keeping mobile apps in mind so there are a lot of interlinking through fully qualified URLs, wont they break in app?

Hey guys,

I’m facing a bit of an architectural dilemma. I currently run traveljunky.in, a travel itinerary and package platform.

Current Stack: * Laravel (Backend)

Inertia.js (The bridge)

React (Frontend)

Server-Side Rendering (SSR) enabled via Node.js

The Dilemma: We are considering a move to React Native to provide a better mobile experience (offline access to vouchers, push notifications, etc.). However, SEO is our lifeblood. We rely heavily on organic search for package discovery and lead generation.

My concerns:

SEO Impact: If I "shift" to a decoupled React Native approach, I effectively lose my SSR benefits for the app content. How do you guys manage the SEO vs. Native App trade-off?

Maintenance Overhead: Is anyone successfully running a "hybrid" setup where the same Laravel controllers serve both Inertia (for the web) and a JSON API (for React Native)?

PWA vs. Native: For a high-intent, low-frequency industry like travel, does it even make sense to go Native, or should I double down on a PWA/optimized mobile web experience?

Specifically, I'd love to hear from anyone who has:

Refactored an Inertia monolith to support a mobile app.

Managed SEO-critical content alongside a native mobile app.

Used Capacitor or Turbo Native as a middle ground for Laravel apps.

Looking forward to your insights!