Couple of days ago Saurav Panda requested a tutorial on building a video chat application using Node-webkit and WebRTC. So, here it goes.
Smooth and easy right!
As mentioned in the video, this client is built using Node-webkit, WebRTC and Peerjs. We will leverage the power of Peer.js & WebRTC to enable the connection between 2 node webkit clients. We will host our own peer-server on Heroku (with one click deploy) and use this server for creating the initial connection.
We will be using Angularjs via Lumx (an Angularjs Material Design implementation) as our client side framework.
First we will understand how the application is designed and then we will build the node-webkit client from scratch.
The application we are building leverages Peerjs to implement WebRTC.
As you can see from the above diagram, the client 1 & client 2 are our node-webkit clients. When the client is launched for the first time, it would establish a connection with the peer server. Then the peer server would provide a random ID or a unique ID for that client. And when the second client is launched, it acquires its own unique ID.
Now, when the two clients want to talk to each other, we will use the Peer API to establish the initial connection between the two clients and then using WebRTC, they continue talking to each other without the server.
Since we are using Angular.js, we will be building our own custom directive for managing the client and interacting with the Peer API. We would create a new tag called
nwk-video-chat and this tag will take care managing the chat UI for us.
Now that we have an understanding of the application design, we will get started with the development.
Create a new folder named nwk-videochat. Open a new terminal/prompt here. We will be using a slush generator, named slush-wean to quickly scaffold a node-Webkit, Express, Angular and Node application. The scaffolded project has everything you need to develop a node webkit app as well as distribute it.
First let us install bower, gulp, slush and slush-wean globally.
npm install-gbower gulp slush slush-wean
This will take a couple of minutes. Once that is done, we will scaffold a new WEAN app. Run
It would prompt you for a project name. You can call it anything or use nwk-videochat. Then it would take a couple of minutes to scaffold the project and setup dependencies.
The project structure would look like
The app folder consists of the HTML, CSS and JS to develop the app. And the assets outside are used for project management.
Now, let us launch the app and test it out. You can do it in 2 ways
I would recommend the second approach for saving some time, but either of them would do.
Once you launch the application, you should see a sample splash screen and then see this
For development purposes, we will enable the toolbar, so you can debug using the developer tools. For that, open package.json and set toolbar property value to true. Then launch the app again and you should see a URL bar and a settings icon next to it.
When you click on the settings icon, you should see
You can use this to debug your applications as you would do with any browser based app. The updated package.json would be
We will modify the splash screen first. Open app/index.html and updated it as
<span class="toolbar__label fs-title">NWK Video Chat</span>
I would highly recommend going through all the Lumx components and then building your app. The above head.html consists of a stripped down version of the toolbar component.
Finally we will be focusing on the
nwk-video-chat directive. We will create a template for this directive to work with the UI. For that, create a new file named nwk-videochat.directive.html inside the app/public/partials folder. Open this file in your favorite editor and update it as
Line 6 : We point the template URL to the template we have created in the partials folder
Line 8-12 : We set the initial state of the application
Line 14 : We show a modal to the user while the client is connecting to the server
Line 20 : We get the webkitGetUserMedia and assign it to getUserMedia
Line 23 : We create a new instance of peerjs by passing in our custom server details. When we setup our own peer server on Heroku, you can update the same here.
Line 30 : The peer is connected to the client, we show a couple of status messages and update close the modal we open on app load
Line 43 : The event
call would be fired when a peer initiates a call to this client. As you can see from the comments, I wanted to show a answer or reject call modal and then if the user answers it, we show the video else we reject it. But this approach, for some reason, is not displaying the video for the call initiator. Not sure why!
Line 85 : Before we connects the two clients, we need to get the video of the current client. Here, we request the stream. And once that is done, we will invoke the callback on line 92.
Line 53 : Once we get the current user’s video stream, we will answer the call and invoke a
Line 98 : We cancel out all in progress calls. And then we stream the video from the peer to the current client.
Line 71 : If the current client wants to connect to another client, we invoke the
peer.call() and pass the call object to the
handleCall() on line 75.
Line 80 : End the active call
That is it! With this we complete our app.
We are going to setup our own peer server on Heroku with their one click deploy. All you need to do is naviagate to the below URL in your browser
Recently I started using Vagrant for one of my clients. The requirement was to have a unified working environment for all the developers, so that they can focus more on code and less on the onboarding and setup. So, I built a Vagrant box that is ready to be used for M.E.A.N. Stack development.
If you are new to Vagrant take a look at
In this post, I will show how to consume the mean-box I have created as is and get started with M.E.A.N. development. Later in the post, I will also show how you can build a customized version of your own Vagrant box and then share it with your team.
In this post, we will take a quick dig at setting up our own private Node Package Registry with Sinopia.
sinopia is a private/caching npm repository server
Maintaining a private NPM for your organization/team is very helpful when you would like to share the code only with them and not the entire universe. You can develop and maintain all your organization specific projects and their components as node packages that can be reused.
If there are multiple teams working, each of them can upload their own reusable node modules to the private NPM and other teams can use them. For example a File upload component or an organization specific HTML5 boilerplate and so on. This way, when you need something all you have to do is run
npm install my-h5bp , which will download the boilerplate for you.