Skcript's Logo
Skcript's Logo
← Go back

Web Apps

We build most of our web apps with either ReactJS or Ember. We believe that these two are the most competent and the most battle tested Javascript frameworks out there. Thus we develop, make use of and contribute to these two frameworks for building web apps of any scale and form.

We aim to build our products that works from now to 10 years into the future or at least we try to do so. So our knowledge on Javascript frameworks are exact and thorough as we build all our projects based on this.

ReactJS basically is an open-source JavaScript library which is used for building user interfaces specifically for single page applications. It’s used for handling view layer for web and mobile apps. React also allows us to create reusable UI components. React was first created by Jordan Walke, a software engineer working for Facebook. React first deployed on Facebook’s newsfeed in 2011 and on in 2012.

React allows developers to create large web applications which can change data, without reloading the page. The main purpose of React is to be fast, scalable, and simple. It works only on user interfaces in application. This corresponds to view in the MVC template. It can be used with a combination of other JavaScript libraries or frameworks, such as Angular JS in MVC.

While according to the authors of Ember, the framework is designed “for creating ambitious web applications.” Not only single-page web applications (SPAs), but desktop and mobile apps, too. Apple Music is one of the most notable examples of an app built with Ember—a music streaming service that’s able to support millions of users.

At Ember’s core is an aspect of web development that was nagging its founders. Looking at the JavaScript framework landscape, the Ember authors wanted to address a few shortcomings they perceived in the other frameworks. They felt that the ability to bookmark and share URLs on the web had become more of a secondary framework feature. Routers were being treated more like afterthoughts, so Ember prioritized routers to solve this.

But that’s not all it solved. The popular model-view-controller (MVC)-style approach to back-end frameworks like Rails and .NET didn’t feel as user-friendly to the Ember team. Other MVC JavaScript frameworks tend to focus on the View, with the model and controller aspects (data and back-end tooling) more as afterthoughts. The Ember team wanted to address these issues up front, and provide a more desktop-like feel that was easier to work within. Thus, Ember is equipped with a great user interface (UI) and excellent client-side functionality out of the box.

Ready to work with us?