3 ms·

"- Simple way to implement pull to refresh (via dedicated off-bound-scroll events?). " At first when I read this suggestion I thought it didn't seem like somet

by k2xl 14y ago

"- Simple way to implement pull to refresh (via dedicated off-bound-scroll events?). " At first when I read this suggestion I thought it didn't seem like something to include. This would force every smart phone to support this type of scrolling wouldn't it? I think there's an issue with many developers just doing too much on mobile web without realizing the limitations of the device they're using. People today are used to developing on systems where they don't have to think about memory, hard drive space, or performance. But when you get to mobile web you have to think about these things AND more (screen resolutions, landscape vs portrait etc). The problem with many suggestions for w3c is that they are often tied to what specific companies (ahem Apple) are integrating (or not). In terms of the Facebook app, I (along with many others) have just been flabbergasted that they've not been able to make their app load fast. Tobie's post gives some great insight, but I don't think it's impossible to create a smooth, well run webview - especially when you have the resources Facebook has.

54mf 14y ago
It's definitely possible to build a Facebook-like app with HTML5 that's fast. I won't assume why they couldn't - my instinct is that the app is significantly more complicated than it appears - but I am a bit confused by some of their concerns. Pull To Refresh is trivial to implement with JS; I know, because I've done it. Perhaps it wouldn't have worked with the code structure they were using, but still, confusing.
- mrwilliamchang 14y ago
  Given that the request for a pull to refresh API is a subpoint to "Scrolling performance", I am guessing they found that their implementation of pull to refresh had all the drawbacks they listed under "QoI issues". From the post, "[Scrolling performance] is one of [their] most important issues."
  - othermaciej 14y ago
    Yeah, achieving many of the scrolling effects they want often requires sites to do scrolling entirely "by hand", which degrades the quality of scrolling.

by k2xl 14y ago

54mf 14y ago

It's definitely possible to build a Facebook-like app with HTML5 that's fast. I won't assume why they couldn't - my instinct is that the app is significantly more complicated than it appears - but I am a bit confused by some of their concerns. Pull To Refresh is trivial to implement with JS; I know, because I've done it. Perhaps it wouldn't have worked with the code structure they were using, but still, confusing.

mrwilliamchang 14y ago
Given that the request for a pull to refresh API is a subpoint to "Scrolling performance", I am guessing they found that their implementation of pull to refresh had all the drawbacks they listed under "QoI issues". From the post, "[Scrolling performance] is one of [their] most important issues."
- othermaciej 14y ago
  Yeah, achieving many of the scrolling effects they want often requires sites to do scrolling entirely "by hand", which degrades the quality of scrolling.