Gustavo Leon

A MySQL database stores the instructions and messages sent and received respectively. MySQL

Devise handles user registration with low effort. Also is configurable in so many levels, from custom views to create-your-own controllers. Devise

With Gulp we managed development tasks using plugins, as eslint, jscs, uglify and Browserify. gulp

With Browserify we could create the inspector snippet used to connect the user's devices with the Dashboard. Using CommonJS modules we could organize large amounts of code alongside third-party JavaScript modules. Browserify

Our Console section uses React to create a view for each message logged from our users' devices. Each message has a different type of information, from simple strings to cookies data or DOM trees. Define each type of message declaratively eases our product's development cycle. React

JavaScript is used to build the DOMScope Inspector, which connects our users' devices with their Dashboard. JavaScript

Faye is in charge to send and receive any instruction and message logged between our users' devices and their Dashboard. Faye

Rails is our product's backend app. It handles user registration/logging, product's logic and Inspector communication with our users' devices. Rails

Ruby is, with JavaScript, the main language used in DOMScope. With Rails, it handles our product's backend, from the landing page to the communication between our user's devices and their Dashboard. Ruby