I have been playing with Windows Live this morning - it is interesting and a real improvement over the old start.com. They have worked hard to create an interactive experience that avoids the dreaded page reload (can someone explain again why everyone is trying to avoid that in obvious situations?). This can be nice, streamlining some experiences, but it has a real downside- one that is pretty destructive in this case.
Consider the following use case:
- Do a search for a term like 'Onfolio'
- Scan the results, click one of the results to view the page
- Click the back button to return to the list of search results
What you'll find is that you aren't back on the search results, instead you're on the homepage again (with your search term in the search box, but no search results to be found). Try figuring out how to email a friend a search result page from live.com- I have no idea how to do this now!
One of the critical things that used to come for free with web application is the browser navigation- forward, back, etc... As rich internet applications gain traction, maintaining this behavior is going tol pose a real challenge for developers as they are now creating single url state machines whose states may not even be addressable by a url. What a disaster for users- forget bookmarks, emailing a friend a URL, using the back button, all things that helped make the web great.
I've run into this problem with a large number of the rich internet apps that I've used- things like Google reader, Gmail, and now live.com. And here's the thing- I'd rather have the page reload round trip if it means I get stateful Urls back.