Does it make any sense to develop for iPhone OS 3.0 instead of 3.2?

When it comes to backwards-compatibility, I want to stick to iPhone OS 3.0 so also some of the poor iPod Touch users who aren't rich enough for iPhones use my apps. But iPhone OS 3.2 has some pretty cool features that would be nice to have.

Problematic thing: Since it's just a minor upgrade, I can imagine most iPod Touch users who decided to upgrade to 3.0 pro开发者_如何转开发bably never upgraded to 3.2. I'm not sure if Apple actually asked them to pay like 10 bucks for going from 3.0 to 3.2. However, if Apple did ask them for money, I'm sure like 90% of all iPod Touch users didn't upgrade.

So the big question is: IF you decide to go with iPhone OS 3.0, is it a stupid idea to stick to 3.2 just because of a few more features? Will this effectively kill half of your iPod Touch userbase?

---

you can provide backwards compatibility by setting the "iPhone OS Deployment Target" property in the build settings to the minimal version that you like to support

keep in mind that you have to check the version at places in the source code where you like to use the new features and provide alternatives for older os versions

---

3.2 isn't out yet (for people without the SDK) but the 3.1 upgrade for iPod Touch owners who paid for 3.0 is free, so it seems reasonable 3.2 will be free for them as well.

3.2 is what runs on the iPad currently.

---

3.2 is only for iPad. iPod Touches and iPhones will jump strait to 4.0.

It's more a question of whether you need the features in 3.2 or want to target the iPad. If not then target 3.0/3.1.

You'd be surprised how many are still on the 2.x OS