solito VS create-t3-turbo

I've been building for the past 3-4 months on the Solito starter repo that uses React Native to build the shared components that are used by both Next.JS for web and Expo for mobile. This theoretically should be harder/longer to build than one of these alone, but easier/shorter than building both separate projects. Has anyone built this kind of monorepo to completion/production before and can share this experience? Am I on the right path and this is a hump during the package configuration phase or would I be better off just using React and constantly maintaining two codebases that have to match feature parity?

I think this is what you are looking for: https://solito.dev/ 😊

We're encountering an issues on the web side while trying to run React Native Skia in NextJS as part of a Solito monorepo. Mobile (Expo) seems to work fine, but the "warning" Skia throws of not finding reanimated is causing Next.js builds to error out with the following error:

I’ve only just started using it but https://solito.dev/ seems to do exactly that.

I found Solito and see that it may perhaps support react-native-macos - does anyone have experience here?

It has become very practical / doable in the recent year or so. In my experience, if you have lot of frontend web experience, the easiest way to ship a RN app is by using Solito [0]. Also check out Nativewind [1] which allows you to style native apps the same way like you would on web. I was able to ship the first version of our app in about 1.5 weeks with this stack. Also checkout Tamagui [2].

[0] - https://solito.dev

Solito 4 - https://github.com/nandorojo/solito/releases/tag/v4.0.0

Another option is the Solito stack which has a single code base for react native and next js. https://solito.dev/

The [Expo docs for NextJS](https://docs.expo.dev/guides/using-nextjs/) recommends @expo/next-adapter, while I have a sense of what [Solito](https://github.com/nandorojo/solito) does as [explained by the author](https://www.youtube.com/watch?v=H1gSWXA3qfw). I'm not fully clear what the difference these two libraries are and whether they can or should be used together.

Check out this starter repo https://github.com/t3-oss/create-t3-turbo I didn’t use it because it didn’t really fit my needs but it I’ve heard good things about it. May work for you

You can checkout https://github.com/t3-oss/create-t3-turbo which is based on https://create.t3.gg

t3-oss/create-t3-turbo: Clean and simple starter repo using the T3 Stack along with Expo React Native (github.com)

I don't have experience with this personally, but create-t3-turbo might be useful for you if this is something you want to do.

https://github.com/t3-oss/create-t3-turbo is a great repo for getting started quickly and seeing the advantages of exactly this.

I’ve been using a monorepo from the create-t3-turbo that uses pnpm and I haven’t had any issues so far.

create-t3-turbo is an amazing example of a turborepo setup done right, im always referencing it for how Julius (the creator) has things setup.

Coming back to your question, for development velocity the best option would be: Trpc + next.js + react native(Instead of flutter) in a turborepo. Look into this https://github.com/t3-oss/create-t3-turbo

create-t3-turbo is an excellent starting point IMO. There are forks of it that include things like Solito, Clerk (for authentication) and others. It does leverage tRPC quite heavily, but if your API is malleable enough to work with it, it really helps simplify everything for your shared API logic.

Understood. Can I swap out next trpc and plug in express trpc? I'm using T3 monorepo https://github.com/t3-oss/create-t3-turbo