2012 Will Be The Year Page Refreshing Dies & Realtime Lives
2012 is going to be the year that page refreshing in a lot of websites well and truly dies. Page refreshing feels so benign and old, the next logical step and something that should have been more common place but hasn’t is realtime web interfaces.
But we already have AJAX Dwayne, that’s hardly anything new, we’ve been able to load pages asynchronously for ages now. While that might be the case, most implementations of AJAX make a request in the background and most of the time are loading full web pages complete with titles, styles, headers and whatnot (especially when it comes to loading a page via AJAX for example).
2012 will be the year that developers start utilising things like Websockets as support grows, loading in pieces of content as needed instead of loading a new page which in turn creates multiple connections for each piece of static content you load – why load the same things twice when you only want to replace a small section of text or dynamically load in a new title or image?
As you may have seen recently I redesigned Kill Hipsters, but what I have planned next will probably seem crazy and inaccessible to a lot of developers, everything is going to be ajaxed and loaded in as needed. It will be accessible in that the single pages of content are still there, links to everything are still there but every piece of content loaded like a link will have an event binded to it and hijacked loading only what’s needed and shuffling the current page around by using a simple technique of changing class names to change the layout.
If it’s successful and I know it will be, then that is how all of my future sites and applications will work. I’ll probably open source the code as well if it’s good enough so others can create dynamic sites and blogs.