Build 707 -- mucho awesomness, but lots of questions

Moving to requiring 4.3 is a big problem for me - I’m building an app targeting kids who are likely to have older iPods handed down etc. It might only be 5% or whatever of the market, but if you’re targeting that 5% then you could really lose out.

I know I can maybe use an older version of the SDK for older devices, but that’s going to mean two different development paths and become quite difficult. :frowning: [import]uid: 93610 topic_id: 19216 reply_id: 75688[/import]

@harry

Yeah, that threw me for a loop as well at first. Looking at the analytics from my other non-Corona apps I have around 15-20% of users that are on iOS 3.1 - 4.2. Up to 5% are 3.1 users.
But as Ansca have pointed out in other threads, Apple is phasing out support for armv6, and will eventually drop it all-together. Starting with xCode 4.2, the default app-template doesn’t include armv6.

Unfortunately there’s no other way to prevent apps from being installed on armv6 devices other than to set the minimum iOS version. That happens to be iOS 4.3 which is the lowest version that doesn’t support armv6.
I’m also assuming from my analytics that a majority of the devices that are reported as 4.0-4.2 can be updated to 4.3 and later. It’s just that some users tend not to upgrade until absolutely necessary.

I’m going to keep build 2011.706 around for a while to support my older apps (gradually phasing them out), however I’m going to use the latest builds for all my new projects.

After all, this is a fast paced environment we’re working in. Next year iOS5 will be old news as iOS6 will take its place…

[import]uid: 70847 topic_id: 19216 reply_id: 75695[/import]