dripsy
web-examples
dripsy | web-examples | |
---|---|---|
7 | 1 | |
1,945 | 269 | |
- | - | |
6.2 | 0.0 | |
2 months ago | almost 3 years ago | |
TypeScript | JavaScript | |
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).
web-examples
-
Expo + Next.js for mobile + web
To be honest, I wouldn't recommend this solution. Expo is quite mature tool, however, during the expo and react-native development you might experience several issues related to maintenance and features implementation (depends on complexity of your requirements). I do not know how it might look like when you want to do web additionally, also with Next.js configs. It's really hard to maintain this solution in long-term in my opinion as you have multiple dependencies related to each-other: Next.js <-> Expo <-> React Native . Every solution is quite complex and developed invidually. I would use simple Expo for Web if needed and use simple React (https://github.com/expo/web-examples/tree/master/create-react-app-example) but it depends on your case which is priority of platform.
What are some alternatives?
react-native-extended-stylesheet - Extended StyleSheets for React Native
expo-next-monorepo-example - Create a universal React app using Expo and Next.js in a monorepo
react-native-media-query - Media queries for react-native and react-native-web
expo-next-react-navigation - ⛴ Make Next.js and react-navigation play nicely together with an Expo/React Native Web app.
expo-cli - Tools for creating, running, and deploying universal Expo and React Native apps
detect-responsive-traits - Determine responsive traits to only server-side render markup truly needed.
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.
rendertron - A Headless Chrome rendering solution
react-native-magnus - A Utility-First React Native UI Framework 🚀🧩
electron - Deploy your Capacitor apps to Linux, Mac, and Windows desktops, with the Electron platform! 🖥️
capacitor-codepush - Capacitor plugin for CodePush