mintter VS solito

I have been using different UI toolkits over the past ~13 years of my professional front-end development career. Probably starting with Bootstrap.

Tamagui has a really elegant combination of a Styling system (the mechanics of applying styles to the underlying systems), a Theming system (the way sizes/colors are passed down within different contexts of the UI), and a Component system (high level components that are ready to use out of the box. In my opinion, this is where Tamagui shines above the competition- each abstraction effectively builds upon the underlying ones, but it gives you a bunch of ready-to-use components so you can start building quickly and worry about the details later. Way better than the "just copy and paste" model of Tailwind which forces you to maintain components and manually create a consistent UI for your app.

We are using Tamagui for our open source electron app + web site. We hope to have a React Native app in the future, so we are strongly opposed to any solution that is overly tied to CSS. If you want to see an example (real-world, messy) codebase that uses Tamagui, please take a look here: https://github.com/MintterHypermedia/mintter/tree/main/front...

The biggest downside, in my experience, is the heavy/complicated/fragile setup process of Tamagui, although this is typical of any TS monorepo. If you struggle to integrate Tamagui in your codebase, I encourage you to power through the setup phase- the payoff is totally worth it!

I was recently tasked with a SPIKE ticket to research the gap analysis of getting our app to Google Play and App Store. What immediately popped up in my head was react-native. So I searched for popular frameworks that supported this. The top choice was Solito. It solved 2 things:

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/