solito VS t3-turbo-and-clerk

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.

In this tutorial, we will implement single sign-on using Clerk, and use GitHub as the OAuth server that'll verify the user’s credentials. We are going to modify an existing application to add protected routes and use the pre-built UI components.

Clerk official example using Nextjs & expo: (no express, webhooks or credential auth) https://github.com/clerk/t3-turbo-and-clerk

I’m currently checking out https://clerk.dev, seems pretty decent so far. The pricing model isn’t ideal but apparently they are redoing it at this moment.

t3-turbo-and-clerk

If you want a complete out of the box easy setup for web and mobile, check this rep out https://github.com/clerkinc/t3-turbo-and-clerk

No I signed up with clerk.dev which made it a lot easier. tbh if it wasn't for them I would have had to hire a developer to help set that up because I had no idea about auth, user databases, and all that.

Some open-source identity solutions I learned could help; integrate with the Logto /Clerk, Ory... API to securely store access tokens that allow Chat GPT to access the user's Logto account; this is a start. But, like these, Security and privacy of service / Technical requirements for integration / User interface for authorization, there’s much to do. It's funny to rethink this topic.

https://clerk.dev meets all of your requirements except ABAC and OSS/self-host. Recommend checking it out if you want something that "just works"

I've def felt your pain before, and it's why I started https://clerk.dev - auth "should just work".