we now are allowed to compile with the 3.0 sdk, but unfortunately it goes only down to 2.2.1. I have two questions:
a) any idea on the current penetration of 2.2.1?
b) any idea on the anti-piracy situation on 2.2.1 vs. the older OS's? How about 3.0?
A few month ago I got quite an uptick in sales when I submitted an update that was compiled on 2.2 instead of 2.2.1. That might look different in the meantime but I wonder if the old rule still applies, like, go down as far as you can.
Also, as visible in the other threads, piracy is starting to be more than annoying. I thought I read repeatedly that it is harder to jailbreak 2.2.1, which leads me to: if the penetration is strong enough and it makes it harder for pirates, that could be a good target to compile for. Plus, I could continue with just one sdk and xcode install...
we now are allowed to compile with the 3.0 sdk, but unfortunately it goes only down to 2.2.1. I have two questions:
a) any idea on the current penetration of 2.2.1?
b) any idea on the anti-piracy situation on 2.2.1 vs. the older OS's? How about 3.0?
A few month ago I got quite an uptick in sales when I submitted an update that was compiled on 2.2 instead of 2.2.1. That might look different in the meantime but I wonder if the old rule still applies, like, go down as far as you can.
Also, as visible in the other threads, piracy is starting to be more than annoying. I thought I read repeatedly that it is harder to jailbreak 2.2.1, which leads me to: if the penetration is strong enough and it makes it harder for pirates, that could be a good target to compile for. Plus, I could continue with just one sdk and xcode install...
Opinions?
Thx,
Markus
Well... Apple says - if your app is not compiled with 3.0 sdk after 3.0 is released they reserve the right to remove your app from the appstore and since you can't submit without compiling with 3.0 sdk I guess that answers the question... 2.2.1 is the lowest you can go at this point if you're doing an update or submitting a new app... Any thoughts about lower versions would then be irrelevant?
I'm not sure about this myself (if it's the case that 2.2.1 is the lowest you can go since I haven't had time to look into it...) - but if you say that's the lowest you can go in 3.0 sdk then I guess that's the lowest you can go...
last time I checked 2.2.1 was the lowest on 3.0sdk you were able to go.
Are you sure about the statement that all new submissions NEED to be compiled with 3.0 sdk? If that's true, that would indeed answer my question.
I understood they reserve the right to pull apps that don't RUN under 3.0 from the store (which I think would be great, that would eliminate a lot of fire-and-forget apps), but that is a different story. So far we compiled with sdk 2.2.1 for target 2.2 and made sure it also runs under 3.0, which was the condition for new submissions since middle of may, right?
last time I checked 2.2.1 was the lowest on 3.0sdk you were able to go.
Are you sure about the statement that all new submissions NEED to be compiled with 3.0 sdk? If that's true, that would indeed answer my question.
I understood they reserve the right to pull apps that don't RUN under 3.0 from the store (which I think would be great, that would eliminate a lot of fire-and-forget apps), but that is a different story. So far we compiled with sdk 2.2.1 for target 2.2 and made sure it also runs under 3.0, which was the condition for new submissions since middle of may, right?
Any clarification highly welcome
Thx,
Markus
I'm not 100% sure - because I'm a bit stressed out with other stuff (duh, not making money on iphone apps!) so I can't go back and check right now, but we all got that email about downloading the 3.0 GM and somewhere (this thing about 2.2.1 and 3.0 that they keept talking about was a bit disturbing to me - since my app is 2.1 - so I might have been clicking on links and stuff) I found some text about apps not being built with the 3.0 sdk can be removed at anytime... If I remember correctly this was stated in the... hm... hang on I will check...
What got me jumping was that - ok, my apps are all 2.1 so do I need to update them all now?
And I see this as something that might be true - great way to do a spring cleaning before the summer... If you have a lot of apps just hanging around it would be easy for apple to just remove them because they're old and hard for the dev to update them all because they're many... Think they're just driving the users to update...
Hang on - I will check and see if I can find the statement about the need to build on 3.0 sdk....
If I remember correctly from Apple's statements, they were saying that if your apps which are currently on the store don't function on os 3.0 then they're on their way out. It makes sense that they'd want all current apps working on the new OS even if not everyone has it yet, but I don't think they'll start pulling perfectly working apps out for no reason.
If I remember correctly from Apple's statements, they were saying that if your apps which are currently on the store don't function on os 3.0 then they're on their way out. It makes sense that they'd want all current apps working on the new OS even if not everyone has it yet, but I don't think they'll start pulling perfectly working apps out for no reason.
But then again, you never know with apple...
Tried to find it but didn't - I might be wrong, but I do remember (yes a couple of days ago but I live in the "now" and my memory of the "then" is not the best) reading something about apps needed to be compiled on 3.0sdk and if not were liable for removement from the store - might be that I missinterpeted and what you're saying is correct... Just that I remember seeing this togheter with 2.2.1 and 3.0 and thinking "does that mean I have to update my apps to 2.2.1 at least to still exist on the appstore?!"
I think I wiped it away as to - if customers starts complaining about your app not running on 3.0 and it's not a tested and validated version you will be removed... I guess that's what they were trying to say which makes sense, if your app goes haywire on 3.0 of course they will remove it... Think they're just reserving the right to do so...
If your app submission is not compatible with iPhone OS 3.0, it will not be approved.
Note the 'compatible' bit. As long as it is 'compatible' with OS 3.0 you will be ok. I guess being compatible with the OS and compiling on the SDK are two different things.
I am still compiling in 2.2.1 and an app was recently approved - after their statement. I will move to 3.0 when I complete my current project.
Which Target OS are you compiling for right now?
Linear Mode
