I don't get the hype. Nearly every interaction with the LinkedIn iPad app feels very clunky, not to mention completely non-native. The momentum and "bounciness" of scrolling is as blatantly non-native as can be. They've done a bunch of great work to get things as close as possible, but it's still a clunky non-native experience.
What's the deal about the infinte scroll? Everytime I have to use it, it feels very unpleasant. The problem is the scrollbar which suddenly does not accurately hint the position of the document I'm in.<p>A solution might be to change the scrollbar hinting from absolute to relative. A simple ∞ added below the "scroll down button" on the scrollbar might just fix this.
This attention to detail and desire to get an excellent experience is what makes an app go from good to great. I really like the LinkedIn app and since LinkedIn curate an excellent news feed I use the app for reading news and I love it.<p>Looking forward to reading the other articles in the series.
I liked the article for technical reasons, but it also got me thinking: given the relatively large percentage of views coming from IPads, at what point does it become a requirement for a developer to own one?
Great writeup. I am currently writing an "infinite scroll" (all directions) web app and it is good to know that someone has documented these issues.<p>Thanks linkedin team
Anybody knows if there's a jquery plugin or similar that implements the concepts from this article? I'm in the same situation and would rather not reimplement the wheel.