![](https://hackernoon.com/images/1*YSJE2eyu_BNBu5ErqoOSyQ.gif)

[Source](https://github.com/vinnyoodles/react-native-socket-io-example)

I never thought I would be writing an article on Medium, but I honestly couldn’t find a decent guide or example of using [React Native](https://github.com/facebook/react-native) with [Socket.io](http://socket.io/) for this use case. I did find [some](https://medium.com/@ekryski/how-to-actually-use-socket-io-in-react-native-39082d8d6172#.qjp8o5hs3) [relevant](https://github.com/badfortrains/wsExample) [examples](https://github.com/skellock/phoenix-react-native-mashup), but they were either not descriptive enough or were using a different tech stack. So now it’s time for me to contribute to the wealth of knowledge.

Let’s dive right into it. First, a server and client need to be created. The example will be using an Express server and a plain React Native project. Once they are both created, they will both have to point to the same web socket which is how the data is transferred between the two.

Multiple sockets can be opened between a server and multiple clients. Socket.io makes it super simple to talk between a single client, many clients, or all the clients.

Once a socket is established, the two ends can speak freely and without delay (faster than HTTP requests 😊.).

To use the web socket, just send the data/message over a named channel.

socket.emit('channel-name', 'Hello world!');

This is identical for both server and client. The other end just has to listen to that named channel.

socket.on('channel-name', (message) => ... /\* some logic \*/);

Simple data structures can be sent over the sockets too, so arrays and objects are fair game.

Back to our use case. When a user types and sends a message, it’ll be sent to the server, which can perform some logic, and then the server will emit the message to all sockets (other users). Messaging apps are expected to store data between sessions, so we’ll just save the message in the database while it’s being relayed.

The message model could be something like:

{   
  text: _String_,  
  createdAt: _Date_,  
  userId: _ObjectId_,  
  chatId: _ObjectId_   
}

To keep track of an open chatroom where any number of people can join, an _identifier_ field will be helpful to keep track of the messages. For mobile apps, each device will act as a user and for new users, they will be assigned an _id_ field which should then be kept in the device’s local storage. We can determine if a user has or has not joined the chatroom if there is an _id_ field saved on the device. To deal with multiple chatrooms, some sort of mapping structure should be used so that we know which rooms that user is in if it does exist.

Regarding the persistence I mentioned earlier, when a user joins a room, we should give it any pre-existing messages that are saved in the database for that specific room.

I’ve created a working example of a [working messaging app](https://github.com/vinnyoodles/react-native-socket-io-example). Big thanks to [Farid Safi](https://medium.com/@faridsafi) for his [messaging component](https://github.com/FaridSafi/react-native-gifted-chat) which made this so much easier. Enjoy!

I’m a Computer Science student at Virginia Tech that loves to write code and lift weights 💪. [LinkedIn](https://www.linkedin.com/in/vinnyoodles) [Github](https://github.com/vinnyoodles)

Facebook

Super

Too Long; Didn't Read

Cassandra Forward a free Cassandra-focused community event

A simple messaging app with React Native and Socket.io

Too Long; Didn't Read

Companies Mentioned

@vinnyoodles

RELATED STORIES