expo-next-react-navigation VS dripsy

This leads to the need for platform-specific routing, which in turn led me to expo-next-react-navigation, which didn't work for me out-of-the-box when following the Expo + Next.js guide linked above.

Dripsy unstyled UI primitives which are responsive (at the expense of SSR support though).

Here are libs to help you share code between web and mobile: - Shared UI primitives + style: https://github.com/nandorojo/dripsy

Try using dripsy. It allows you to create responsive themes a lot like the web.

Dripsy is a good solution for styling: https://github.com/nandorojo/dripsy

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).

Does NOT currently support SSR. Even though it still works with NextJS for other reasons such as code splitting and navigation, and SSG.

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).