A Progressive Web App is in essence just a website.

Think of it as a website built using web technologies but that acts and feels like an app.

To achieve that, a PWA makes use of recent advancements in the browser and in the availability of service workers and in the Cache and Push APIs that have enabled web developers to allow users to install web apps to their home screen, receive push notifications and even work offline.

The intent behind PWA is to make development, deployment and maintenance of mobile applications easier.

The post PWA (Progressive Web App) appeared first on BlogGeek.me.

WebRTC stands for Web Real Time Communications. It is at the intersection between the internet and telecommunications.

WebRTC’s main driver is bringing real time communications into the browser, and to the hands of many more developers – enabling a considerable reduction in the barrier of entry for those who need to add communication capabilities to their applications; and a reduction in the level of friction end users face when dealing with communication services.

WebRTC enables sending voice, video and any arbitrary data across browsers in a peer to peer fashion.

WebRTC the specification

WebRTC is a specification that is being defined by two separate standardization organizations – the IETF and W3C.

W3C is “in charge” of the JavaScript API layer for WebRTC as part of HTML5. The latest working draft is available online.

IETF has an active working group with the name Rtcweb which handles the network part of WebRTC – defining what gets communicated over the network.

WebRTC is a “work in progress”. Version 1.0 of the specification hasn’t been released yet, although it is already implemented by Chrome, Firefox and Opera browsers.

WebRTC the project

WebRTC is an open source project released and maintained by Google.

It is an implementation of the WebRTC specification that fits into Google’s Chrome browser. It can be ported to other operating systems and uses as well.

The project is licensed under the permissive BSD license, enabling its commercial use by any organization and individual.

The project is found at webrtc.org.

The post WebRTC appeared first on BlogGeek.me.

It is an alternative implementation to Google’s WebRTC code base.

Unlike Google’s WebRTC project, which is built out of a proprietary media engine (based on their GIPS acquisition), OpenWebRTC makes use of GStreamer, a popular open source media engine.

OpenWebRTC supports multiple operating systems and has an implementation of both VP8 and H.264 for its video codecs.

The post OpenWebRTC appeared first on BlogGeek.me.

Node.js enables writing backend services using Java Script.

Node.js uses the same V8 Java Script engine that is used in the Chrome browser to optimize the execution of Java Script code.

Node.js is event driven in nature, and built towards the creation of services that require a lot of messaging and networking. This makes it suitable for signaling.

Node.js is very popular in the development of many WebRTC related services.

The post Node.js appeared first on BlogGeek.me.