Whenever I read about Single Page Applications (SPA) or Single Page Interfaces (SPI) they are defined as a huge html file. But I would say that’s not true. You can still separate them into multiple files and include them either with a framework or more easily but “uglier” with jQuery. You will then show these parts or pages without any roundtrip to the server (but there are hybrid apps where the server returns html).
A Single Page App is not only a huge html file which hides and shows pages, it can also update data on the page without refreshing the page (pressing F5). That means most of the work happens on the client side.
There are no side effects, right?
So why I should develop a Single Page App?
The fact that the most work is on the client, there are less server calls, so the user does not have to wait for the response. Therefore it feels very smooth and like a native app. The server could be only a REST API (Raspberry PI), which can be requested from almost everything. The data consumption is less (good for Mobiles without WIFI) because it only loads the needed data in a simple format (like JSON or XML).
And it clearly gives a better user experience – you really want to discover the page.
To get into the approach of Single Page Apps is not that easy, but when you’re in, you’ll have fun and love it. Single Page Apps are really interesting for mobile devices which don’t have the same network speed as a computer connected with a LAN cable. It opens a new experience for users. Even well-known sites such as Facebook and Soundcloud use the approach of Single Page Apps.
Now it’s over to you. Try to build a Single Page App.