Android 4 list is performing worse in ST2 then ST1 (slow scroll)

[olouvignes]

Has anyone of you tried the latest 2.1.0-rc to see if things were improved with this release. I'm not sure whether I should retry the 2.1-branch or wait.

[hotdp]

There are improvements. But still not performing as ST1 do.

[Steffen Hiller]

Not happy with performance yet (iOS and Android 2). Will probably wait for GA and then try to either optimize the existing list implementation, or use the one from 2.1 beta 2.
Haven't tested on Android 4 yet. But even on the iPhone 5 with iOS 6 it doesn't seem to be smooth, but may be just me.

[olouvignes]

Since going back to ST1 is not an option for me... I found the latest 2.0.3 to be really smooth on an iPhone4S/5, good enough on 3GS/4 (2G/3G are now deprecated since you can't build against armv6 anymore). Performance is also relatively good on a GalaxyS2 (2.3.6 gingerbread) so I'm happy enough on this branch.

I suspect I'll get worse perf on 2.1-rc1 (any of you tried 2.0.3-master vs 2.1-rc1?), but I'll let you know when I test it.

[hotdp]

Not happy with performance yet (iOS and Android 2). Will probably wait for GA and then try to either optimize the existing list implementation, or use the one from 2.1 beta 2.
Haven't tested on Android 4 yet. But even on the iPhone 5 with iOS 6 it doesn't seem to be smooth, but may be just me.

No its not just you.
If not fixed in GA I am forced to use DataView and style it as List. (And keeping the number of items under 50 fx.)

[Steffen Hiller]

I suspect I'll get worse perf on 2.1-rc1 (any of you tried 2.0.3-master vs 2.1-rc1?), but I'll let you know when I test it.

Not sure if I'm right,ut I think 2.0.3 is the same as 2.1 beta 1 regarding scrolling performance (that beta basically only included the first version of the new charts)?
In beta 2 I saw some improvements (on iOS and Android 2), and in beta 3 came the new list.

[Steffen Hiller]

No its not just you.
If not fixed in GA I am forced to use DataView and style it as List. (And keeping the number of items under 50 fx.)

Yep, that seems to be that best option. Unfortunately I need a group view (I already disabled pinnedHeaders for Android and it seems to be disabled by default on RC1), so I really need to copy the beta 2 or before implementation. :-s

[profunctional]

Any update on this? We got a ton of bad reviews regarding performance on the Android. Users complaining about it being unusable. So we started building in ST2. Not only that, we stared to promise users a faster experience on the Android. But after 6 months on ST2 I'm seeing that ST1 is faster than ST2.

What is the future of ST2? Has anyone else considered abandoning ST2 and doing a native app instead?

Anyone use anything else for cross platform development with better performance? I'm reading some blogs out there that ST2 is only acceptable for ioS.

[hotdp]

Any update on this? We got a ton of bad reviews regarding performance on the Android. Users complaining about it being unusable. So we started building in ST2. Not only that, we stared to promise users a faster experience on the Android. But after 6 months on ST2 I'm seeing that ST1 is faster than ST2.

What is the future of ST2? Has anyone else considered abandoning ST2 and doing a native app instead?

Anyone use anything else for cross platform development with better performance? I'm reading some blogs out there that ST2 is only acceptable for ioS.

I understand what you are saying. I am in the same situation and its critical. I guess we have to wait for 2.1 GA?

I just don't see how this is "fixed" in 2.1 unless there is something in GA that is not in RC2 this problem is not fixed at all. But I guess if that's the case I have to open a bug report for 2.1 with the same topic and wait xx months.

profunctional: I guess there is no Silver Bullet, every framwork have pros and cons. But the frustrating part about Sencha Touch is that there is many promises and we tell customers what they are saying and end up lying. When the customer demos a old ST1 app that performs much better than there new ST2 app that should have been 200% better in performance? (What they tell us) That makes us look like ****.

[profunctional]

Well that's just it. Our company is looking bad. We try to explain that it was the framework we built upon causing the issues. But ultimately it is our fault for choosing the framework. I'm just looking for an official answer for Sencha on this.

If you guys remember, anyone that built an ST1 app was left in the dust. No more updates and very little support with migration. We actually paid for the support. If ST2 is such a bad performer, I just don't wnwant them abandoning it again for an ST3 or something.