Hacker News Reader

Comment by hunterb123 | Hacker News Reader

Wouldn't Remix be a better fit? It's easier to run in more client-orientated environments.

Currently, I like to have the API and web pages (signup, marketing, policies, etc.) made with Remix.

Then, the cross-platform app (native & web) can be made with React Native / React Native Web using React Navigation as the router.

I can certainly see being able to combine those two into one as a plus, but React Router / Next Router and React Navigation conflict. React Navigation is needed for a nice app experience.

View on HN

Someone has brought up adding a Remix integration to Solito, too. It's certainly possible from my end, the question is if Remix would make it possible. Many remix APIs like Form seem to be very browser-specific, so it wouldn't share nicely with React Native.

That said, I opened this discussion on the Remix repo a while ago: https://github.com/remix-run/remix/discussions/1578

If you're using shared screens outside of Remix marketing pages, though, then I imagine a solito/remix could exist to bring the same features the Next integration has to a Remix one.

Understandable with web specific apis like form. My main wish is a React Navigation and Remix adaptation to bridge native to full web.

Doesn't remix very much want to handle the routing? Homestead you mashing that with react-navigation?

As does Next.js, does it not? Solito uses next/router. I updated my comment to reflect this dilemma.

This is why I currently separate web pages & API from the cross-platform native/web app.

Adapting Remix to React Navigation would be the solution if possible.

Sure and that's what this library bridges. I see the appeal in remix for building interactive apps the "remix way" with forms, relying on web/http conventions etc. I also like that it brings nested routing back to metaframeworks. None of that will translate well to native. As an api+website framework it doesn't look more appealing then next.js to me, which is a little more unopinionated and thus easier to adapt to cross-platform.

I guess my point was this library bridges next router similar to how it could bridge react router with Remix. Neither are a great native experience that React Navigation provides.

Reply on news.ycombinator.com