solito VS Wails

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.

This is basically the same tech stack of an app I’ve been planning to build, but deployed as a desktop application using Wails: https://github.com/wailsapp/wails

Wails 2.6k

The wails project does this when. You can check it out here https://github.com/wailsapp/wails/blob/master/v2/internal/typescriptify/typescriptify.go for inspection.

I have built Web front-ends (React or Svelte) with Go-backend. Embed in a web-view to make it a native desktop app, or get funky and give it native chrome/menus etc. [Wails](https://github.com/wailsapp/wails) is a good candidate to start if you want to cut on boiler plate.

Is that what wails is doing here? (On mobile)

In a "local" environment, where an executable can be provided to someone with the entire game contents. In this case, the game won't use WebSockets, and will instead use a Go/JS bridge (something like Wails) to connect.

Have you seen wails? https://github.com/wailsapp/wails

You should check out https://github.com/wailsapp/wails/pull/1959