Few days ago one of my friend asked me how does Gmail change its URL while user operates inside it without page refreshing, I've no idea about that at that time, he then shared a link Ajax Pattern - Unique URLs
which deep dives into this topic, as the article mentioned: Unique URL make your website's link "Bookmarkable, Linkable, Type-In-Able", plus Sharable
IMHO, easy to be shared to Social network which is extremely important nowadays.
The key technology to achieve the ""Unique URL" goal could be summarized into two points:
- If the content in the page has been updated by Ajax significantly enough, update the URL (
location.hash) as well.
location.hash = 'Blogs&Page5';
- Every time the Ajax page loads, JS should understand the URL and render related content as well.
var urlHash = location.hash;
var curPageNo = urlHash.replace('Blogs&Page','');
What I want to emphasize is the hash value, i.e. the content behind # is originally expected an HTML element's name attribute used for In-Page navigation, it is completely the contract between client Browse
r, HTML content
, server side cannot get the information directly except we explicitly pass the value to the server side (hidden post, URL query string, Ajax etc), therefore,if some user access the unique URL, your website's client side JS should parse the hash and retrieve relevant data from server side.
- Better user experience.
Every time user accesses the unique URL Ajax page, the fixed part of this page loaded first, and then loads the main content asynchronously, if the main content is large enough, for example, contains images or rich media content, the "async loading" is much better than the page loading blocked by downloading those images/medias.
For instance, originally loading one specific page requires 2 seconds totally, after applying the this "async loading", the fixed part cost 0.4 seconds to be loaded and the main content costs 1.8 seconds, from user's point of view, usually the latter case would be better because the user see your page is partially loaded within a short period (0.4) which feels good enough, plus a graceful loading/splash screen, eventually the UX got improved significantly!
- Better SEO support (Performance Aspect)
The page rendering speed is an important fact for a search engine's crawler, by applying "async loading", the crawler will deem the page it is crawling has a good loading speed - 0.4 seconds.
- Easy to support W3 web standard
This is sort of kidding Since your main content is Ajax loaded, W3 validator (so does Search Engine) won't validate the main content which is very possible does not strictly adhere all the standard rules.
- Main content cannot be indexed by Search engines
- Harder to development and to maintain
P.S. I spent two days in updating my blog (http://WayneYe.com
), revised the paging style from traditional into the Ajax Unique URL pattern above, it is no doing Ajax paging and update URL like "http://wayneye.com/#Blogs&Page5
", it definitely "Bookmarkable, Linkable, Type-In-Able and Sharable
", plus a loading panel and content fades in effect, I believe its UX is much better than before.