Seeing as Native Packaging is described as "providing a way to seamlessly 'wrap' your web app in a native shell" I'm hoping I'd only have to deal with App Store based app updates when Sencha's "native shell" is updated, i.e. not that often. This would be great because App Store updates take a week to get approved and require user intervention. If the Micro-loader Delta-update Mechanism coupled with HTML 5 Application Cache described in http://www.sencha.com/blog/behind-se...build-process/ were to work with Native Packaging it seems it would be the best of both worlds as the vast majority of updates would be seamless to the user just like a web app but you'd also have the device access advantages of a native app, a true "hybrid" approach.
I'm very new to Sencha Touch 2 but it doesn't seem to work that way, at least "out of the box". Benefit of "out of the box" way seems to be that you don't need a server, as everything is on device, which is great for some use cases, and certainly simpler. But, it seems like I'd have to do an App Store update every time I made one little change.
I'm sure there is is way for me to Micro-loader Delta-update Native "hybrid" route I'm just trying to understand the best way to get there now and if it's not currently quite "built in" whether it's on the road map.
Would be great if someone could shed some light on this topic.
In the meantime I'll be familiarizing myself with Sencha Touch 2 and coding my app, lucky I can put this concern off for a while, but figured I try and collect some advise in the meantime
Thanks a lot,