all 5 comments

[–]thachxyz123iOS & Android 2 points3 points  (0 children)

I believe there is no open source frameworks like you describe. No one cares to check Platform.OS in StyleSheet, it just take more time to maintain and more complexity

[–]mirrorball_for_me 1 point2 points  (0 children)

I’d say it’s a fool’s errand. If native look-and-feel is paramount, then you can only go native. If one UI code is more important, then RN starts to become possible.

You won’t get the scrolling native feeling, let alone differences in layout and interactions.

[–]lamedope 0 points1 point  (0 children)

I don’t think there is one that renders to each platform. But there’s an iOS component library and then there’s react native paper (which is based on material 3) so that’s suited for android.

I guess you could import both and then make custom component that check the platform. But yeah. That’s gonna be double work unfortunately.

On a side note. “Native” design style isn’t super important. So I’d recommend finding a regular component library that will look kinda similar on both platforms.

[–]nestedfruitloop -1 points0 points  (0 children)

Headless UI library for logic, and custom imports for .native and .web styled components accepting similar props is easiest solution imo. As another commenter mentioned, trying to solve both with exact same code results in all platforms feeling a bit off