Skip to main content

Developing a new app; is maintaining iOS 4 compatibility still worth it? [closed]



I am currently in the starting phase of developing a new iOS app (for both iPhone and iPad) for a client. I'm really indecisive if I should still support iOS 4 or not. I tried to find some statistics about the adoption of iOS 5, one of the only fairly recent articles that I could find was this one. This article shows that 59,16% of all users of Bump for iPhone were using iOS 5 or later as of December 30th of last year. The (free) app will not be out for another 1.5 to 2 months, my personal guess is that the iOS 5 adoption percentage will be pretty large by then.





I fully realize that there is no single answer to this question, but I would like to know what your experiences with backwards compatibility are and if you think it is worth the hassle. I would really like to use the new Storyboard functionality of Xcode and I would also really like to use ARC (although I understand that it is partially useable with iOS 4 too). The app will also use quite a bit of JSON and which is now natively supported in iOS 5 without the use of a third party framework.





Thanks for the help!


Comments

  1. The answer is yes. You have no idea how many ppl have no clue that 5.0 is out, or even what it is. My neighbor still has 3.1 and it is so old that iTunes fails to upgrade it.
    Target for 4.2.

    ReplyDelete
  2. It honestly depends. If your app wants to reach a large number of users (social networking, maybe a game), then supporting older OS's is the ONLY way. Your statistics imply that a full 41% (most likely a lot less) of iOS devices are on iOS 5, so 41% of a huge install base may not seem like a lot, but when it comes to marketing, it's huge.

    But if you want to reach a special audience (say a special synthesizer app, or a REALLY complicated application), requiring the latest OS becomes less of a burden.

    So, take your pick. It's really your personal choice. Either way; you can't go wrong.

    ReplyDelete
  3. Here is some real data - for my apps approx 75% of users are on iOS5.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex