Single-Page Application


What is a single-page application?

Single-page applications are web applications where all necessary code - HTML, JavaScript and CSS - is retrieved with a single page load at the beginning, and after the initial pageload, they are able to redraw any part of the UI without requiring a server roundtrip to retrieve HTML. This is achieved by separating the data from the presentation of data by having a modal layer that handles data and a view layer that reads from the models. The big upside of this is that the user experience can become seamless and the performance can be better, since only the necessary parts of the page are refreshed – and even then, we only make the request for and then get the data.

Why would one want to build such apps?

The reason of the apparent spreading of Single-Page applications seems to be that they provide a more native-app-like user experience. It is only natural, that sensenet ECM, too, shall provide support for such development endeavours. We are adamant in bringing developers a front-end development ecosystem with which single-page applications can be implemented with ease.

Where is sensenet ECM in the picture?

In a traditional SPA architecture, sensenet ECM Content Repository (as of now, SenseNet.Services is the NuGet package name) will serve as your backend. You can store, retrieve and modify data through the OData API. Our javascript client layer (sn-client-js) can be the base of your web application and you can use it to effectively call the repository actions and functions.

Building blocks for your SPA’s

Right now, the new SN7 GUI is a work in progress, but components are being rolled out continuously written in React and Aurelia. These components can be perfect building blocks for a native-app-like intranet or really any other data-driven application.
Tell us, what you think! Try out sensenet ECM with our SPA building blocks and give us a shout-out on gitter, github or in an e-mail.

Please help us by completing this survey

Go to survey