RNR with Solito

[VimalSwaroop]

I want to create a mono repo to run mobile and web from single code base, solito gives a starter kit. We have a web app built using tailwind, we have to build a mobile app now. We want to use NativeWind so that we can reuse the existing styling from web app. As part of our research we came across RNR which eliminates/reduces the development time for us, since it gives components with some NativeWind styles.

Now, the challenge is we are not able to setup the project with solito minimal setup with RNR as a shared component between mobile and web. can someone help me?

SOLITO: https://solito.dev/starter

@mrzachnugent
@the-simian

[the-simian]

Hi @VimalSwaroop, thanks for sharing your setup questions! I’m not one of the lead maintainers, so please note this is my personal opinion and may not reflect the official stance of Solito or @mrzachnugent.

I’ve found that after Expo 52, maintaining a monorepo for web and native can be more trouble than it’s worth—particularly because configuring Metro across multiple packages tends to be brittle. Instead, Expo’s newer features often make a single codebase more straightforward, where you can selectively use .web vs. .native files and share components via React Native directly.

If you absolutely need server-side rendering (SSR) or other specific Next.js features, a monorepo might still make sense. However, be aware that Expo is actively improving its web support and plans to introduce SSR in the future, which could reduce the need for a Next.js + Solito approach down the line. It’s also important to note that Expo Router and Next.js’s router both aim to solve similar problems, and you may encounter some friction if you want a single shared setup for core routes like Auth.

Ultimately, how you structure your code (monorepo vs. single repo) is a business and engineering decision. You might choose a dedicated web project and gradually migrate pieces to React Native, or keep all platforms in one codebase and rely on .web/.native file extensions. It depends on your team’s priorities and whether you’re comfortable juggling the extra complexity that a monorepo can bring.

Hope that helps! Let me know if you have any other questions or want more details on setting up Expo for web and native in a simpler repo structure. Good luck with your project!

[VimalSwaroop]

Thanks for the response @the-simian. After a lot of research, we decided to go with Expo setup!