1. 6
  1.  

  2. 4

    For him the scrolling becomes natural, comfortable and predictable.

    I would have picked better examples. The intence page doesn’t feel natural or predictable at all. It has the wrong “intertia” on iPhone. Exactly what this library claims to get right, it gets wrong. And it breaks tap on status bar to scroll to top, to boot.

    I don’t understand these scrolling libraries. The worst native browser scrolling crushes (crushes!) even the best fake scrolling JavaScript. And typical js scrolling is far from the best.

    1. 1

      Had a similar experience on Android, but maybe it’s only supposed to make a difference in desktops?

      1. 1

        In general, I agree with you regarding the intence page.

        However, the natural scrolling has good applications in places where automatic scrolling has to happen – especially when 2 dimensions are involved. A project I worked on this summer needed to highlight the relationship between a list and an SVG, and we used automatic (smooth) scrolling to make sure the thing that was to be highlighted was actually visible

        1. 1

          Yeah, kinda makes you wonder: if JS is in fact going to take over the world, wouldn’t it have done so by now? JS is butting up against technical limits, and I don’t see browser vendors having any real incentive to push things further. Three of the four major browser vendors (Google/MS/Apple, but not Mozilla) have a major source of income established on top of native apps. That is probably a safer revenue stream than the web can ever be.

          (Though from the app economy’s POV, wouldn’t it be nice to reclaim some of the economic surplus being extracted by the app stores? I don’t think it’s possible though, I think app store success is somewhat derived from there being a consistent and optimized way to pay – i.e. a payment system monopoly is a precondition to the current native app distribution success.)

          Maybe it would work to build JS a new UI toolkit that is not dependent on HTML (but polyfilled to it). Surely it would be easy to write useful apps in JS if you were targeting a different toolkit, i.e. one not hamstrung by HTML. Android showed that it is possible to write OK user facing apps in Java. It seems within reason to do so in JS as well.

          Then again, I think it’s fair to say that any web developer turned app developer that cares about UX enough to switch to a more native language has already done so. And therefore the JS developers that remain have been selected down to those that don’t care about UX as much or aren’t as capable. I guess it’s a question of how many such JS developers there really are.