Over a million developers have joined DZone.

The Single Page Interface Manifesto

DZone's Guide to

The Single Page Interface Manifesto

· Java Zone ·
Free Resource

Download Microservices for Java Developers: A hands-on introduction to frameworks and containers. Brought to you in partnership with Red Hat.

I have published The Single Page Interface Manifesto. The objective of this manifesto is to promote the progressive disappearance of the use of pages not only in web applications also in dynamic web sites.  

The Web based on pages as Tim Berners Lee invented have had an extraordinary success, however, the Web has evolved so that the initial idea of linking scientific documents with hyperlinks has been largely overcome by a new dynamic Web, most of web sites are "web applications" forcibly based on pages.  

The page based web programming tends to be a source of problems, despite efforts of frameworks to mitigate this pain, such as the use of Back/Forward buttons, unwanted caching, unwanted form auto-fill etc. Page based programming is strange, repetitive (plagued of includes to achieve some reusing) and inefficient (both in bandwidth and computing power rebuilding complete pages) compared with programming in a single main window like in desktop.

The approach of Single Page Interface (SPI) tries to surpass the page concept as the center element of web programming with the concept of state (fundamental or secondary) and with a programming model event based similar to desktop.

The manifesto shows how the Single Page Interface approach is technically possible even in public web sites. The SPI does not imply to give up Search Engine Optimized (SEO) web sites, bookmarking or page-based services such as ads or counters of visits, in these cases the manifesto shows how you can convert "fundamental states" of a SPI web site on simulated pages.  

The manifesto briefly reviews the evolution of web programming techniques and justifies this "new" way of programming could be named "Model 4".

Although the technical point of view and the sample web site are based on ItsNat (a Java based web framework), I think other frameworks could be able to help developers to produce SPI web sites without losing the advantages of traditional programming based on pages (SEO, bookmarks...).

Finally because is good "to eat your own dog food", the corporative web site of my company, Innowhere.com, has been ported to Single Page Interface, the sample web site of the manifesto. It is basically the same as the old version based on pages (same aesthetic and similar functionality), showing a real working example of the revolution of Single Page Interface.


Download Building Reactive Microservices in Java: Asynchronous and Event-Based Application Design. Brought to you in partnership with Red Hat


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}