I really don't understand an actual use case for this. Any ideas?
Definitely nice, but WAY too easy to trigger. The way it works now, it's so sensitive that simply trying to scroll to the top of the page triggers it for me every time.
Agree. I kept trying to do it because I was curious, and got annoyed when I accidentally (always) triggered it :p
I’ve actually been working on a script similar to this and I’m doubtful that it’s possible to achieve the same feel on the web as you do on mobiles. The biggest issue is that this behaviour makes most sense with touch devices, and there are currently no events for touch on desktop environments to be able to detect touch holds.
This is what I came up with but it’s far from perfect: http://jsfiddle.net/JyzhD/
BTW Brandon and Jordan, I’m happy for you guys to help yourselves to my code if it helps you out. If you do decide to use it, a credit someplace would be nice though I’m not gonna hold a gun to your head either way :)
It would be nice if it worked exactly as on mobile, so that you can choose not to refresh by just scrolling back and release the scroll wheel to refresh.
Exactly, it's triggered way too easily. It should include a confirmation mechanism like the "release to refresh" on iOS. Desktop usability vs Touch/Mobile usability are quite different.
Pull up to refresh makes sense on a touchscreen, but I don't think it translates well to mouse/keyboard. Tried this on my S3, and though it's a little wonky, it worked! I could see this being useful for mobile web after some kinks are worked out.
I don't know. I've gotten very much used to pull-down-to-update on native OS X apps like Sparrow and Twitter. I don't seen any reason this pattern couldn't work just as well in a web app, assuming it is implemented appropriately and not just for the sake of it.
This is awesome, and looks really easy to use.
Hey there, I'm Brandon, one of the co-founders of Hook. Thanks so much! You're absolutely correct, Hook is super easy to use & implement into your sites.
…Chrome extension? There already is one, but it's sluggish — this one's nice n' smooth. Do that! Please :)
I'm very much intrigued by this.
Why is this better than cmd+r/f5 or clicking the refresh button that every browser has?
Totally agree. The concept is great on mobile and tablet devices. But, on the browser it's inconvenient. Command+R or the Icon refresh button is a more convenient route.
I can see this concept being pretty great for non-full page refreshes of elements like timelines and feeds that frequently update (on the seconds scale). The Twitter.com timeline, for example, would be great.
But without seeing that in action, it's unclear whether having the pull to refresh on a specific page element, and not on the whole page, is too much of a disconnect from the experience on mobile, where you're literally moving the entire screen down.
Hey Colin, I'm Brandon, one of the co-founders of Hook. Thanks for the feedback! The functionality you mentioned is definitely on our list. :)