CUA
solito
Our great sponsors
CUA | solito | |
---|---|---|
6 | 26 | |
1,013 | 3,243 | |
- | - | |
6.3 | 8.4 | |
5 months ago | 6 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CUA
-
How to architect a Web and Mobile React Native app
Bias: I maintain a fullstack universal app template called CUA that uses Expo/Nextjs/tRPC/Solito/Tamagui.
- Which is the best lib/framework option for a single code base for web, Android & iOS?
-
Is react native ready to be used on the web?
Most of it is, but there are still parts that arent smooth integrated, such as navigation and authentication, and others that may need separate implementations due to not having a ready-made wrapper. create-universal-app and create-t3-turbo are good starting points.
- The right way to build multi platform apps in 2023 using web tech. ?
-
Ask HN: What would be your stack if you are building an MVP today?
I'd likely go for a mobile first approach and start with:
create-universal-app : https://github.com/chen-rn/CUA
Which would give me:
-
Tamagui 1.0 – Cross-platform React apps in ½ the time with 2x performance
Yes, try either:
The official «Tamagui + Solito + Next + Expo Monorepo» starter:
https://github.com/tamagui/tamagui/tree/master/starters/next...
Or the more recent version that builds on that and adds tRPC and authentication (with Clerk):
create-universal-app - https://github.com/chen-rn/CUA
solito
-
React Native in Next.JS for Hybrid Web/Mobile Monorepo: Should I give up? ($250 Bounty)
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?
-
Easiest Way to Build a Cross-Platform App (Web & Mobile) with Minimal Code Duplication
I think this is what you are looking for: https://solito.dev/ 😊
-
How to edit Next.Config.js to add plugins like Skia?
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:
-
Tamagui – UI kit that unify React Native and Web
I’ve only just started using it but https://solito.dev/ seems to do exactly that.
-
Suggestions for converting a Next.js (app router) / Tailwind CSS website hosted on Vercel to a OSX app
I found Solito and see that it may perhaps support react-native-macos - does anyone have experience here?
-
Expo – open-source platform for making universal apps for Android, iOS, and web
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
-
2 big announcements - Tamagui Takeout & Solito 4
Solito 4 - https://github.com/nandorojo/solito/releases/tag/v4.0.0
- NextJS on iOS & Android????? How???
-
Deciding between RNW and React
Another option is the Solito stack which has a single code base for react native and next js. https://solito.dev/
-
NextJS + Expo question: What's does @expo/next-adapter and Solito do? Can they be used Together?
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.
What are some alternatives?
tamagui-expo - An Expo template with Tamagui
t3-turbo-and-clerk - A t3 Turbo starter with Clerk as the auth provider.
expo-image-editor - A super simple image cropping and rotation tool for Expo that runs on iOS, Android and Web!
create-t3-turbo - Clean and simple starter repo using the T3 Stack along with Expo React Native
le-shef - Kitchen Timer Application Built In React Native Expo
moti - 🐼 The React Native (+ Web) animation library, powered by Reanimated 3.
next-galaxy-template
showtime-frontend - Showtime makes digital collectibles useful, accessible and social.
rn-bounceable - 🏀 Native bounceable effect for any React Native component. Built with Reanimated 2. Compatible with Expo (Web).
tamagui - Style React fast with 100% parity on React Native, an optional UI kit, and optimizing compiler.
react-native - A framework for building native applications using React