1

I am developing iPhone application which involves the frameworks available from iOS 3.2 (Core Text, etc..) for rapid development, but the client requires deployment target to be iOS 3.0

The dilemma is either drop the comparability requirement together with development cost but narrow the potential user range or to take an significant extra effort to develop application compatible with older iOS. The dilemma comes from the opinion that the users who do not update their iPhones are the ones who do not use AppStore, do not buy apps, etc... so keeping developing for them does not have marketing sense.

Is this true? Do you know any reliable resource/research regarding the subject?

Lukasz
  • 19,816
  • 17
  • 83
  • 139
  • Unless you require support for devices that *cannot* upgrade to 3.2 (like 1st-gen iPhones), absolutely don't bother with anything below 3.2. Almost certainly don't bother with anything below 4.0. And you could probably get away with 5.0+ only if you're willing to stay on the vanguard, especially after a couple more months. – Ben Zotto Nov 06 '11 at 16:44
  • I believe such questions are always puts dilemma kind of situations to developer. But i believe that its Developer's responsibility to explain the limitations of older functionality and advantages of using new functionality. This is always a challenge for a developers. Of course newer is going to give you something NEW.... :) – DShah Nov 06 '11 at 16:44
  • I am mainly concerned about the users who do not update their iPhones to the newer iOS because of the performance drop. This could be the true for iPhone 3G. – Lukasz Nov 06 '11 at 16:51

3 Answers3

4

As i see it - Apple is one of the companies with the highest upgrading percentages, most users upgrade to a steady release no longer than 3-4 months after its out (the more savvy ones will upgrade almost immediately usually),

Honestly i think the number of users who are actively downloading apps that DON'T have iOS > 3 is low enough to "ignore" it when needed.

If the decision was left to me i would go for > 3.2 as you need Core Text as you said and the downside isn't that high .

Thats my personal opinion about it :)

Cheers.

Shai Mishali
  • 9,224
  • 4
  • 56
  • 83
4

Definitely don't waste your time. Virtually EVERYONE is on iOS 4+ now, and virtually everyone will be on iOS 5 by early next year.

Also, please use the search function next time, this question has been asked many times before.

fishman
  • 955
  • 1
  • 7
  • 13
  • I have not found the question which would touch this dilemma from the project management / planning point of view. Please point to to duplicate if I a wrong. – Lukasz Nov 06 '11 at 16:46
  • http://stackoverflow.com/questions/4502839/percentage-users-still-on-ios-3-x-should-i-bother – fishman Nov 06 '11 at 16:55
2

If you are selling such a massive huge number of apps that even a tiny percentage increase in sales can pay the salary of full time programmers and QA testers, and your app is usable without the newer APIs, then maybe it's worth supporting ancient OS versions.

If not, it's most likely not worth it, as

1) the smaller feature set allowed by not using the newest APIs, and

2) the longer development and testing time as well, might cost you more new sales than you would get from customers with ancient devices; and

3) people who don't upgrade their OS or their devices don't buy nearly as many apps as people running more up-to-date OS versions.

hotpaw2
  • 70,107
  • 14
  • 90
  • 153