react-native-webrtc VS Socket.io

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

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).

For apps that require real-time communication, Socket.IO can be a valuable addition. It enables bidirectional, event-based communication between the server and client, making it an ideal choice for implementing real-time chat features.

Community stats: Socket.IO has a community with 59.2k stars and 10.2k forks on GitHub.

Socket.IO is a NodeJS framework built on top of WebSockets that enables realtime client-server communication. Socket.IO is event-driven and compatible with older browsers and environments.

I'm glad to announce the version 0.7.0 of my library socketioxide! It is a socket.io server implementation working as a tower layer/service. Therefore it integrates with any hyper based http framework like salvo, axum, warp or hyper itself.

Check the quickstart of Socket.io. Support Socket.io on GitHub ⭐