feat: React Native clarification

[weboko]

This is a **support request** ## Problem I notice that some hackers spend time figuring out how to build React Native application with `js-waku` only to find themself switching to `go-waku` or even moving back to browser stack. ## Proposed Solutions Make it clear how `js-waku` can or cannot be user with React Native: - [ ] update `readme` with message that `js-waku` cannot be used in React Native as of now; - [ ] add links to example with `go-waku`; Next steps: - [ ] make a simple app with React Native to see what works and what doesn't with `js-waku`; - [ ] try running `go-waku` example to see if it works and gain experience to share later during hackathon with participants (https://github.com/waku-org/go-waku/tree/master/examples/android-kotlin); Note that there is a bounty for React Native - https://github.com/waku-org/bounties/issues/12

[weboko]

@chaitanyaprem could you point out example where go-waku is used with React Native?

[chaitanyaprem]

@chaitanyaprem could you point out example where go-waku is used with React Native?

https://github.com/waku-org/waku-react-native/tree/master/example i am aware of. Haven't run this in a while though as we archived this repo.

[fryorcraken]

Do we want for a community member to try to make js-waku work in react native? https://github.com/waku-org/bounties/issues/12

@weboko wdyt?

[weboko]

@fryorcraken I think it should be done by us due to following concerns:

• potential need to fix / change build system;
• any bad UX / runtime troubles;
• gaining some experience in building an example / app so that we can provide better support during hackathons;

[fryorcraken]

Let's close https://github.com/waku-org/bounties/issues/12 and https://github.com/waku-org/pm/issues/124 is already scheduled