react-native-webrtc VS react-native-web

Hi, I am using react-native-webrtc along with react-native-simple-peer for my webrtc video calls. I tried using a custom turn server and twilio's servers as well. All the servers that I am using give IceGatheringState: complete on this website, so I feel that the servers are working fine. I am unable to connect the calls whenever I'm using mobile data or am on different networks and get the error Ice Connection failed. Have tried toggling values for trickle and also tried completely relying on the turn severs by using iceTransportPolicy: 'relay'. Have beat my head for quite some time regarding the solution for this and would appreciate any help, thanks!

I think WebRTC could be an alternative; it requires a signalling server and more manual setup, but at least with this—you don't get unexpected bills—the only thing that could go wrong is your signalling server crashing, but downtime shouldn't matter in this case. The other thing to consider is the effort it takes to go down this route & maintenance.

heres the stuff that IS available in the expo sdk: https://docs.expo.dev/versions/v47.0.0

You then use 3rd party modules (or build your own) for anything else you need. For example, webtrc: https://github.com/react-native-webrtc/react-native-webrtc

Maybe using WebRTC Data Channels, https://github.com/react-native-webrtc/react-native-webrtc/blob/HEAD/Documentation/BasicUsage.md

I am building a react native application using Expo and i need to add audio calling and video calling functionalities, however it seems that i cant use react-native-webrtc (Link here) without ejecting Expo.

maybe https://necolas.github.io/react-native-web/? https://github.com/vercel/next.js/blob/canary/examples/with-react-native-web/README.md

I am following a tutorial that is 4 years old that states that react native 0.55.4 is last compatible with react native web and anything later is not compatible yet. He showed the documentation page in the video as his source.

Personally, if you're trying to find a stack that can be applied everywhere with Next.js as your chosen framework, best bet would be React Native Web or similar. Which would let you share the maximum amount of frontend code between Web, iOS, and Android. Then you could reach for electron (barf) or something to bundle it for desktop if that was a requirement.

Some of the top cross-platform frameworks do have support for web targets. React-Native-Web and Flutter on the Web are both ways to target the web with your cross-platform app.

https://github.com/necolas/react-native-web/discussions/2201 it can be done.

If you want a single codebase for web and mobile I would look into react-native and react-native-web. You could probably code the web app with react-native-web, make it responsive and build it through react-native for mobile. Designing an app for mobile and for web can lead to significant difference though since the experience is quite different. Some things might make sense for a mobile and not for a desktop or the opposite. So I wouldn't discard completely the idea of having separate codebases. Highly depends on the app though, totally valid for many use cases.

Another fun thing you could do is build it for mobile + web using React-Native through Expo or manually with https://necolas.github.io/react-native-web/

If you're using Expo (which I assume most are on RN) they have web support. This is via React Native Web, which is a separate project if you wanted to use that directly too.

Personally though, I've found the DX of Flutter far above RN. I always had random packages break on RN that I had to fix every time, while with Flutter most of what you need is already included in the framework, including a component UI library for Android and iOS.

[0] https://docs.expo.dev/workflow/web/

[1] https://github.com/necolas/react-native-web

So the RN-R part is done by https://necolas.github.io/react-native-web/ and it's really good! However, there are some code that is kind of outside of the scope of React. Ie. Navigation, that's more in the realm of Next.

I don't have personal experience with this, but React Native Web claims to solve this issue: https://necolas.github.io/react-native-web/, not sure if anyone has had experience with this. Of course, you will have issues with dependency hell/package maintenance.

Another great option seems to be Flutter web. I was really impressed by the "batteries included" approach to Flutter, and Dart has a pretty comprehensive standard library. This is in contrast to React's "just find a random package on npm and pray it doesn't bite you in the future."

Obviously rewrites are expensive, but I personally think both approaches are worth considering versus abandoning native components completely. WebView isn't without problems (and also, you don't need React Native to use WebView).