4 ms·
I've done it. Once you're setup, it really does work quite out of the box. What you do have to be mindful of is clear separation of concerns when designing plat
by phist_mcgee 4y ago
I've done it. Once you're setup, it really does work quite out of the box. What you do have to be mindful of is clear separation of concerns when designing platform specific components - you have to think in terms of Button.native.ts and Button.web.ts when you're doing things like haptic feedback or animations.
The only thing that's really a pain is that react dev tools has a harder time dealing with RNW components, and debugging in general can be a bit of a pain.
- no_butterscotch 4y agoHow are you liking it so far? Perf issues or no? Any concise/clear resource or guide you used?
- phist_mcgee 4y ago>How are you liking it so far? Perf issues or no? Perf seems totally within reasonable bounds for a react app, no issues so far. In terms of resources or guides, it's pretty spotty out there. The project has definitely slowed down in terms of dev and i'm not sure where things like react 18 fit into the picture across platform, but we've setup our own config that works just fine for now. We may need to reappraise in 2-3 years if react does change architecturally too much.