macrumors 68000

Watching how laggy and unresponsive their application was on that device made me cringe. All the power that phone has, quad core 1.6GHz CPU and it still lags just selecting an item from a drop down menu.

macrumors G4

Watching how laggy and unresponsive their application was on that device made me cringe. All the power that phone has, quad core 1.6GHz CPU and it still lags just selecting an item from a drop down menu.

macrumors demi-god

Watching how laggy and unresponsive their application was on that device made me cringe. All the power that phone has, quad core 1.6GHz CPU and it still lags just selecting an item from a drop down menu.

Click to expand...

I ddn't notice anything super slow. At what time point are you talking about?

It looks like it's probably an HTML5 based application, which means it's not going to be lightning fast.

macrumors 68030

Watching how laggy and unresponsive their application was on that device made me cringe. All the power that phone has, quad core 1.6GHz CPU and it still lags just selecting an item from a drop down menu.

Click to expand...

Huh? I saw a couple seconds of stutter, but its most likely an HTML5 based App, and its used 100% for getting work, how fulid the UI animations are doesn't really matter as long as it gets its job done.

I can see why they went with the Note, much more portable than an iPad, and much larger than the iPhone, and screen size matters I would guess in this situation.

macrumors demi-god

59s - the male flight attendant selects an item from a drop down list and the device even after acknowledging his finger press freezes the list in place.

Click to expand...

Thank you very much for your quick reply.

Yep, I see it: the fade-out of the menu pauses for a split second:

I've seen this a lot in HTML5 apps after someone adds a fade transition, trying to be cool. Depends partly on the browser being used and mostly on what's going on the background.

For example, if the developer didn't wait for the animation to end, but went ahead and accessed the seat chart information while triggering the fade at the same time, then that could cause the fade to jump... from full display to full fade... in only a few steps. This looks laggy, but it's just visual, because the time used will always be the same:

You see, the total amount of time taken for the fade does not change... only the number of fade steps will. (Animations are given a time period in which they must finish. In this case, probably 1.5 second. That could end up as being 15 steps at 0.1 sec each, or 3 steps at 0.5 second each. The first looks smooth; the second looks laggy, but they both take the same amount of time.)

As someone mentioned, a JB update will probably help with the visuals.

MacRumors attracts a broad audience
of both consumers and professionals interested in
the latest technologies and products. We also boast an active community focused on
purchasing decisions and technical aspects of the iPhone, iPod, iPad, and Mac platforms.