dripsy
solito
dripsy | solito | |
---|---|---|
7 | 26 | |
1,948 | 3,254 | |
- | - | |
6.2 | 8.1 | |
3 months ago | 11 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.
dripsy
-
The different strategies to building a cross-platform app
Dripsy unstyled UI primitives which are responsive (at the expense of SSR support though).
-
React-native with next.js question
Here are libs to help you share code between web and mobile: - Shared UI primitives + style: https://github.com/nandorojo/dripsy
-
Styling RN apps
Try using dripsy. It allows you to create responsive themes a lot like the web.
-
Expo + Next.js for mobile + web
Dripsy is a good solution for styling: https://github.com/nandorojo/dripsy
-
How to combine React Native Web + responsivity + NextJS SSR, to get SEO
This article is extracted from this github discussion, which goes into greater detail on how to achieve this with the libraries Dripsy (a component design system) and Fresnel (SSR w/ media queries).
-
Magnus UI vs. Dripsy - Chakra UI alternatives for React Native (+Web)
Does NOT currently support SSR. Even though it still works with NextJS for other reasons such as code splitting and navigation, and SSG.
-
How to use ChakraUI on native mobile?
Dripsy is very declarative: it allows you to provide object and array values to add mobile-first responsive styles. Instead of manually using the Dimension API (on native), and adding media queries and nested styles throughout your code (on web). This API is very inspired by Chakra UI's array syntax for declaring responsiveness. (Which Magnus UI also is inspired by).
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?
react-native-extended-stylesheet - Extended StyleSheets for React Native
t3-turbo-and-clerk - A t3 Turbo starter with Clerk as the auth provider.
react-native-media-query - Media queries for react-native and react-native-web
create-t3-turbo - Clean and simple starter repo using the T3 Stack along with Expo React Native
expo-next-react-navigation - ⛴ Make Next.js and react-navigation play nicely together with an Expo/React Native Web app.
moti - 🐼 The React Native (+ Web) animation library, powered by Reanimated 3.
expo-cli - Tools for creating, running, and deploying universal Expo and React Native apps
showtime-frontend - Showtime makes digital collectibles useful, accessible and social.
detect-responsive-traits - Determine responsive traits to only server-side render markup truly needed.
tamagui - Style React fast with 100% parity on React Native, an optional UI kit, and optimizing compiler.
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
react-native - A framework for building native applications using React