Hacker News Reader

Comment by onedognight | Hacker News Reader

I want to believe, but every time I try their menus on my iPhone 4 I'm disappointed by jerkiness and delay. In particular if you scroll down on the demos page and click a menu item, you see

  1) the page *jerk* to the top
  2) a loading dialog with a spinner over the whole page
  3) a *nice* smooth animation into the new page

Then when pressing the back button:

  4) a nice smooth animation to the *top* of the screen

I've lost my place! Actually navigating a hierarchy with this is painful, slow and disconcerting.

Can anyone from the project comment on what the technical reason for this is?

View on HN

If you think it's bad on the iPhone 4, imagine how bad it is on a 2 year old Samsung Moment running Android 2.1. I've spent a lot of time trying to make basic touch interaction halfway responsive on older phones (read: anything but the newest phones), and all my efforts (which include trying jQuery Mobile, Sencha Touch, and jQTouch, as well as a bunch of from-scratch CSS and JS work) have been met with failure. I've concluded that, if you really care about and are paying attention to the details of user interaction in your app, the current state of native-feeling web apps just isn't there yet. The issues I've encountered are split about 50/50 between slow JS/rendering performance and non-standardized DOM event behavior.

Sigh... Yeah, just evaluated this, Sencha, M-project and a bunch of others on Android 3.2 tablet and decided to stick with the native UI.

There is enough jerkiness and little things that make it annoying to use. Heck, Sencha ended up displaying a big giant white blank rectangle covering most of the screen. And these are their own demos (!).

Try SproutCore 2.0.

A couple of things:

1. I don't believe their site/demos are running the latest version of jQuery mobile (weird, I know). 2. Secondly, the resetting behavior can be easily handled now with the addition of beforechangepage by setting the current scroll position before transition and using $.mobile.silentScroll to update on page re-entry.

Trying out http://jquerymobile.com/test/ which is synced to the latest code base, it seems that they have added one final step

   5) delay a long time then scroll back to where you were

Not losing your place is significant, but the steps are still quite distinct and the delays quite painful.

I suspect this is a testament to the difficulty of cross browser/device mobile development in general.

Sounds like this may all be resolved with the new improved fixed toolbars/page transitions in iOS 5.

Reply on news.ycombinator.com