Slides: Responsive web design from the future
speakerdeck.com
Slides: Responsive web design from the future
1–8 of 8 posts
Re: Slides: Responsive web design from the future
#2For the curious, here's a few extra links from this talk: http://warpspire.com/talks/responsive/
Hope you enjoy!
Re: Slides: Responsive web design from the future
#3Loved this, would suggest anybody further interested in real data on page load speed to check out:
How site speed impacts conversion rate / engagement:
http://www.webperformancetoday.com/2010/07/01/the-best-graph...
How site speed impacts Google rankings (and tools to asses / fix):
http://www.conversionvoodoo.com/blog/2010/04/official-google...
Re: Slides: Responsive web design from the future
#4I loved the site hosting the slides—does anybody here have an invite or the ability to setup a new account? Would be much obliged.
Re: Slides: Responsive web design from the future
#5I'm glad that designers are starting to see the problems with page state that's not tied to URL state. Nearly all the sites I've seen using #! state have got this wrong.
Re: Slides: Responsive web design from the future
#6The infinite scroll example he linked to in the presentation is very nice. Putting the max_id in the URL is a great way to save the state.
Re: Slides: Responsive web design from the future
#7The infinite scroll example he linked to in the presentation is very nice. Putting the max_id in the URL is a great way to save the state. http://warpspire.com/experiments/history-api
the idea is good, but the implementation (from user perspective) is not 100% correct. try scroll somewhere, say you see text "My dad just told me I'll get my late grandfather's cornet" on top and refresh the page, you will see different stuff.
Re: Slides: Responsive web design from the future
#8I'm glad that designers are starting to see the problems with page state that's not tied to URL state. Nearly all the sites I've seen using #! state have got this wrong.
You have to be specific as to what state you're referring to; should color changes and element position be tied to a URL?