Update 2024-11-24: Just use tamagui.dev for UI (or onestack.dev for a crossplatform framework).
First, a primer on React Native Web (RNW), for th...
For further actions, you may consider blocking this person and/or reporting abuse
NativeBase is worth checking out: "Mobile-first, accessible components for React Native & Web".
It works with RNW, and it looks like you can get SSR with it (without an utility-first approach, but more like Dripsy, since "NativeBase V3 allows you to provide object and array values to add responsive styles."):
github.com/GeekyAnts/NativeBase/pu...
But maybe not, since compatibility with NextJS is still questionable:
github.com/GeekyAnts/NativeBase/is...
Even though NativeBase has docs for NextJS:
docs.nativebase.io/install-next
NB: Many people are reporting performance issues at scale with NativeBase. Heard in various Discord channels, and also here: github.com/GeekyAnts/NativeBase/is...
Chakra UI vs. Nativebase code comparison (usage, functions, components): nativebase.io/blogs/nativebase-cha...
NativeBase doesn't seem to have the same polished aesthetics as Chakra UI.
But you could potentially use Chakra UI's theme with NativeBase's unstyled components: github.com/chakra-ui/chakra-ui/iss...
See also the successor to Nativebase, made by the same team, called Gluestack UI ui.gluestack.io/ which can be used with the accompanying dank.style style library. It is part of the overarching suite they call Gluestack.io
Nativebase is discontinued for performance reasons: github.com/GeekyAnts/NativeBase/is...
SnackUI is another alternative.
SnackUI's name has been changed to Tamagui (tamagui.dev)
Tamagui looks like a worthy competitor to Dripsy and Magnus UI!
Update: Yeah, I would definitely use Tamagui over Dripsy and MagnusUI, and even over NativeBase (due to its performance issues).
You sure? Seems like different maintainers…
I think so