My impression- there is still a huge different in the "feeling" of a native app v. a Sencha app. As a "mobile first" developer, I wouldn't dream of using Sencha.
The good news for Sencha is that many companies will prioritize cost/platform reach and a "good enough" experience will be, well, good enough.
This alone, makes the app clunky.
On "feeling fast enough", let's pick a jquery mobile case, I tried http://www.jqmgallery.com/2012/02/11/sharksfrenzy/ on galaxy s2 (dual core, etc) and iPhone 4s. The list (notice its translucent, and overly decorated) scrolls like snail on the android phone. While it flows very smoothly on iPhone 4s.
A similar list would do better than that on Android if done in Sencha Touch 2.
As for "feeling", however, there are a ton of little things that are broken: the blue touch highlight sometimes clears and sometimes doesn't (seemingly dependent on the target of the link, not the source), they are doing some silly HTML5 pushState mechanism to mess with the back button incorrectly (specifically, pushing a new state when you go "back" in the UI when that should really pop a state), etc..
The thing that is really freaking me out is that I'm having a hard time figuring out if they are using native scrolling or not (as in, on iOS 5.0, you can just say "this div is scrollable", and not have to re-implement the behavior): the curve seems wrong and glitchy, but they have nailed enough of the actual visual elements that it is no longer obvious to me that it isn't just that they figured out a way to make the native scrolling perform poorly. ;P