---

Study-Room

Chat, Talk, Study....

Study, collaborate, conference ... over click of a button.

---

A fully functional 🚀 web application where students create/join rooms and communicate using text and audio channels. No registration required . The application connects peers using WebSockets and WebRTC. Check it out here.

New Features

• Generate room ID and share with friends
• Directly connect to room with shared link, valid for 12 hours
• Better UI

Installation

Clone the repo

git clone https://github.com/Sudheer121/Study-Room.git 

Start client and server in different terminals

cd client 
npm i 
npm start

cd server 
cp .env.example .env
npm i 
npm start

You are good to go !!!! .

Note : The server uses a Twilio API (for TURN servers) for voice chat. Not required locally

---

Desktop and Mobile Views

The application is compatible with both desktop and mobile phones. 

Blog describing how the entire system works

• Checkout the blog.

Features

• Chat using text and voice channels
• Easy to use UI with everything on one screen
• Mobile Compatibility
• Connect with multiple people by choosing unique room ids

Technologies Used

• Server - Nodejs
• Client - Reactjs
• Chat - WebSockets
• Voice - WebRTC

The need of WebSockets and WebRTC ( short summary )

What's the best application level protocol for enabling a bidirectional communication channel(i.e both client and server can update each other at any time) ?. HTTP works fine when the client has to request data fewer times. HTTP opens up a connection and closes the connection as soon as it gets required response. In case of a chat application we continuously need to listen for data from server, one solution is keep requesting the server for data every few milliseconds, but its resource consuming for both the sides. The solution is WebSockets, it enables a full-duplex bidirectional communication, that is, the client is always ready to listen for data pushed by server. But WebSockets are still not peer to peer, in case of audio/video streaming between multiple peers, creating a direct peer to peer connection is a better option (because loads of data is being streamed), but this is also one of the most difficult things to do. WebRTC helps us create a direct peer to peer connetion. WebRTC is one of the most complex communication protocols because it tries all possible ways to create a peer - peer connection, if it still fails then the data is relayed via a TURN server.

---

Pull Request

Steps for pull request are a bit different than installation mentioned above.

Fork the repo

Clone the forked repo locally using git clone ==> git clone forked_repo_link.git

Checkout to a new branch, name it appropriately ==> git checkout -b new-feature-xyz

Make the changes and commit them

Push changes to the forked repo ==> git push origin

Start a pull request ==> After pushing, you will see a Compare and Pull Request button on forked repo