Any benefit of using native-only components over universal components?

[shovel-kun]

Hi.

According to this old comment (#27 (comment)), it seems like you're gradually making native components more web-friendly. Currently, there are two ways of using rn-reusables: native-only or universal.

1. Do you plan on continually supporting native-only components in the future?
2. Is there any benefit in choosing native-only over universal components in a mobile-only project?

Thanks!

[mrzachnugent]

Good question.

This is tech-debt. Once upon a time, the @rn-primitives were not npm packages. The files were added into your /components/primitives folder and depending on the selection of "native-only" or "universal", it would add different files into your primitives folder.

Added an issue to fix this: #228