Any future support for React Native (expo) ? #116
Replies: 6 comments
-
Hi @octalpixel, At the moment, we don't plan to support React Native but I imagine that we can make this work easily once we get the modeling of the component correctly. I'll move this to a discussion in the meantime. |
Beta Was this translation helpful? Give feedback.
-
This would be a great addition. |
Beta Was this translation helpful? Give feedback.
-
Hoping to see this eventually roll out! |
Beta Was this translation helpful? Give feedback.
-
Zag looks perfect for a cross platform UI. The main challenge is that React Native does not have a defined document as its rootNode, so I guess we'd have to refactor how the rootNode is found when scope is created (createScope()) and make the typings more agnostic. Once that was done I imagine it would be easy to add a react native framework based on the existing react one. I'm not familiar enough with how Zag initialises its scope to get a proof of concept working, but I'd like to help in the future if someone else can break the ice :) |
Beta Was this translation helpful? Give feedback.
-
Yes please! Libraries like react-native-web and react-native-reusables may provide some inspiration on how to. |
Beta Was this translation helpful? Give feedback.
-
Expo 52 supports React DOM components. Hint hint, nudge nudge... |
Beta Was this translation helpful? Give feedback.
-
🚀 Feature request
Would there be support for expo/react-native in the future? Wondering if it's possible given the architecture
Beta Was this translation helpful? Give feedback.
All reactions