Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pull to refresh. For the web

usehook.com

Post reply on HN
Print view View original

31–40 of 50 posts

Re: Pull to refresh. For the web

#31

Post by Encosia »

gojomo wrote: post #18
lowboy wrote: post #15

This is not a good idea because it breaks years (decades?) of expected behaviour on desktops. When a user scrolls a page back to the top, the expectation is that they'll see the top of the current page from the most recent pageload. With this, there's no way to revisit the top of the page in its current state and it's just gone when you scroll back to the top. This doesn't save much time/effort as a refresh is a comm…

In the best touchscreen implementations, you have to overscroll past the top by a certain amount to get the reload behavior. Further, while overscrolling less than the threshold amount, you get a visual hint that further pulling will reload, while letting go will avoid a reload. This Hook.js implementation doesn't yet seem to have that level of refinement... but if it could, I don't think the user expectations or con…

Unfortunately, there aren't any events to track overscroll with regular mouse wheel or trackpad scrolling. I looked into it for a bit, wanting to create something exactly like Hook, but with the expected UX. Once the viewport hits the top of the window, scroll and mousewheel events stop firing even if the fruitless user input continues.

Touch is different, because you continue receiving touchmove events even if the page is scrolled to the top and the touchmove events don't have any visible effect.

Re: Pull to refresh. For the web

#32

Post by choult »

jakub_g wrote: post #27
lowboy wrote: post #15

This is not a good idea because it breaks years (decades?) of expected behaviour on desktops. When a user scrolls a page back to the top, the expectation is that they'll see the top of the current page from the most recent pageload. With this, there's no way to revisit the top of the page in its current state and it's just gone when you scroll back to the top. This doesn't save much time/effort as a refresh is a comm…

I'd like to second @lowboy and add a bit unrelated but annoying thing I've been recently noticing: It's enough that many popular news pages break my habit (in Firefox/Chrome) to use [Ctrl +] Shift + Left/Right to highlight the text I read with the Left/Right arrow buttons doing some magic like going to next article etc. Never mess with the keyboard shortcuts of the browser unless you really know what and where you're…

My current pet hate with a number of sites is the fact that a number have started capturing / for focussing on their site search - where in Firefox it's been Quick Find for ages. Slows me down something rotten.

Re: Pull to refresh. For the web

#33

Post by city41 »

aroman wrote: post #14

I would definitely not want to use this for my desktop (or my laptop really), but this seems like it would be a great way to make mobile sites feel a little bit more mobile-y. Kudos on the clever idea and well designed website.

I know at least Sencha Touch provides this functionality for mobile sites. But it doesn't do so with hijacking the scrollbar, it implements it just like in native webapps.

Re: Pull to refresh. For the web

#34

Post by shanselman »

Clever, but doesn't behave like it does on a phone. I have a touch enabled laptop running Chrome. I visit the page. Try to Pull to Refresh. It doesn't work. It seems to be setup to watch for scrolling rather than actual Pulling to Refresh.

Re: Pull to refresh. For the web

#39

Post by mbell »

lowboy wrote: post #15

This is not a good idea because it breaks years (decades?) of expected behaviour on desktops. When a user scrolls a page back to the top, the expectation is that they'll see the top of the current page from the most recent pageload. With this, there's no way to revisit the top of the page in its current state and it's just gone when you scroll back to the top. This doesn't save much time/effort as a refresh is a comm…

> This is not a good idea because it breaks years (decades?) of expected behaviour on desktops.

I don't think thats really valid.

How long have facebook and twitter (among others) been automatically updating the page with new tweets/feed content?

It seems to me that the expectation of 'static page state' is already gone for pages where this would be useful - sites with fast moving feeds of data. I'd really love reddit among others to have this feature.

I'd also add that there is a lot going on around 'push' technologies for many apps that also destroy the concept of a static page state, and many of those applications are loved by users and developers alike.

Re: Pull to refresh. For the web

#40

Post by rothlis »

ntaylor wrote: post #38

Cool idea, but this is a total anti-pattern. People do not expect this behavior from scrolling on a desktop and without a proper ajax implementation the result is far from ideal.

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.
Post reply on HN