Support iOS 4.2 going forward (in 1.4?) since it offers the most features built-in to the UIWebView: http://www.mobilexweb.com/blog/safari-ios-accelerometer-websockets-html5
On the native Objective-C side, supporting iOS 4 will also allow us to use blocks http://pragmaticstudio.com/blog/2010/7/28/ios4-blocks-1 which is a fundamental technology used in all of their framework APIs since iOS 4
- Plugin problems - plugins using blocks in native code cannot be used on iOS 3. This can be mitigated with support for PhoneGap versions (as well as built in macros for iOS versions) in pre-processor macros, so this can be conditionally compiled. This can be solved with versioning in our future proposed plugin packaging
- Possibly maintaining a iOS 3.x branch at the last iOS 3.x supported PhoneGap version for bug fixes – for those that want to still use that version – don't really want to do this though
We stopped iOS 2.x support when iOS 4.x came out (thus, we usually only supported one version back from the current OS version).
The oldest iPhone to have iOS 4.2 support is the iPhone 3G (released July 2008 - 3+ yrs old, discontinued). Current iPhone is the 4S, 3 models ahead.
The oldest iPod Touch to have iOS 4.2 support is the iPod Touch 2nd Generation (released Sep 2008 - 3+ yrs old, discontinued). Current iPod Touch is the 4th Gen, 2 models ahead.
The oldest iPad to have iOS 4.2 support is the iPad 1 (released April 2010, 1+ yrs old, reportedly discontinued). Current iPad is the iPad 3rd Generation, 2 models ahead.
Essentially, we would drop device support for these models: original iPhone and iPod Touch 1st Generation