solito VS capacitor

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.

It should also be mentioned that the official VSCode Ionic Plugin is also capable of migrating your existing application. Capacitor v6 now also supports bun as a package manager.

> PWA optionally bundled with some native components for filing the gaps, as in Tauri.

Isn't that essentially Capacitor?

https://capacitorjs.com

Have you experienced slow scrolling issues?

https://github.com/ionic-team/capacitor/issues/4187

Project: Build This Webpage (just this one page, make sure it is responsive (useful on all screen sizes)) => https://capacitorjs.com/

Capacitor

For the longest time, building desktop apps was a daunting task to web developers. That is, until technologies like Electron made creating these apps more approachable to a wider audience. Today, we’ve got a wide array of native applications built with solutions like Electron, Tauri, Capacitor, and many more. While these are great solutions, sometimes configuration can be tricky and the applications we create can become somewhat bloated in terms of memory usage.

The traditional alternative to Electon on mobile platforms is Capacitor (which uses the system webview):

https://capacitorjs.com/

(fka Apache Cordova, fka PhoneGap)

Ionic Framework UI Components are used to build a website and then a mobile application is built using Ionic Capacitor. Ionic UI components are not required but are used for UX. The vue js code presented here will work fine in a separate application.

Welcome to Part Two of this four-part series on building a mobile game using open source technologies. We'll be using Phaser, along with Ionic, Capacitor, and Vue.