Everybody, I’m Dave Hecker and today we’re going to talk about a term that we are are hearing all the time these days, and a lot of clients are asking about. It’s the single page application. We’ll talk about what it is, and how it’s going to affect you and your project. Okay to start, this is not going to be a super technical explanation of what a single page application means. This is more going to be for the layman all the way up to somebody who is just considering and trying to get a very broad understanding of what it means.
So here we go. Let’s start with the Wikipedia definition of the single page application. A single page application, also known as a single page interface, which I have never heard, is a web application or website that fits on a single web page with the goal of providing a more fluid user experience
akin to a desktop application. That’s a good definition. Let’s talk about what it kind of really means. In the past, the way that web applications worked was like
this, you have a browser and you have a web server over here. You’re sitting at your browser and you type in www.whatever.com, and your browser sends a request to the server and says, “Send me the home page of that site.” Server sends it back to you, and you look at it, and you click again, send another page. “Now send me this page.” Now that page comes back. Now you type something in the box, “Send me the search results for this term.” Server thinks about it sends you a new page back. You are always getting new pages, and that’s why we see a lot of reloading, especially in older websites. You’re always waiting for the page to refresh. A single page application doesn’t do that at all It’s a completely different approach. When you first come to the website, behind the scenes
complex applications. It’s faster, it’s better in a lot of ways, it is harder to