Re: Is iOS 7 required for submission of an app to the Apple App Store?

[Shazron <sh...@gmail.com>]

Perf gains for 64 bit:
http://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html

TLDR;
The 64-bit isa pointer for an Objective-C object only uses 31 bits, the
rest of the 33 bits are used for an inline reference count. Previously,
reference counting was in an external table. The old way was slower, thus
the new way results in performance gains for object alloc/dealloc.

Quoting:
"My casual benchmarking indicates that basic object creation and
destruction takes about 380ns on a 5S running in 32-bit mode, while it's
only about 200ns when running in 64-bit mode. If any instance of the class
has ever had a weak reference and an associated object set, the 32-bit time
rises to about 480ns, while the 64-bit time remains around 200ns for any
instances that were not themselves the target.

In short, the improvements to Apple's runtime make it so that *object
allocation in 64-bit mode costs only 40-50% of what it does in 32-bit mode*.
If your app creates and destroys a lot of objects, that's a big deal."




On Fri, Sep 27, 2013 at 2:09 AM, Shazron <sh...@gmail.com> wrote:

> Currently, no.
>
> See this page, section "Test for Compatibility":
> https://developer.apple.com/ios7/
>
> "New apps and app updates submitted to the App Store should support iOS 7
> and be optimized for iOS devices with Retina display. iPhone apps must also
> support the 4-inch display on iPhone 5, iPhone 5s, and iPhone 5c."
>
> The operative word is "should", and as Build has encountered already, they
> are still accepting iOS 6 built apps. Most likely the added time is for
> developer testing with the new devices. The operative word is "should", it
>  used to say "must": https://devforums.apple.com/message/884949#884949
>
> My guess for iOS 7 being required is when they support compiling a fat
> binary of 32-bit for iOS 6 and 32 and 64-bit for iOS 7:
> https://developer.apple.com/news/index.php?id=9162013a
>
> The ETA for that is "next month" (end of it, most like), when OS X
> Mavericks is released (note that Xcode 5.0 GM does not include Mavericks
> support) and the new iPads come out.
> There are no plans IMO for Cordova to care about 64-bit support until this
> fat binary format is supported. At this point, I'm not sure if there are
> any performance gains, there is no data for this until we can run
> benchmarks on 64-bit devices like the iPhone 5s and the new (future) iPads.
>
>
> =============
>
> LIMITATIONS ON iOS 6 BUILT APPS RUNNING ON iOS 7 DEVICES
>
> =============
>
> Microphone access requires user permission now on iOS 7. When an iOS 6
> built binary runs on iOS 7, any microphone access is by default *allowed*
> but the resulting audio file will be *silent*. The media and media-capture
> core plugins can use the microphone - and iOS 7 support for the microphone
> have just been tagged in the repos (thanks Steve Gill):
>
>
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;a=summary
>
> See tag r0.2.3
>
>
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;a=summary
>
> See tag r0.2.2
>
> The same goes for the splash screen plugin, it has a change for iOS 7
> support:
>
>
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;a=summary
>
> See tag r0.2.2
>
> These changes are in their master branches as well, and have been pushed
> to http://plugins.cordova.io
>
> If CLI and plugman users re-get the plugins (by id), the latest code
> should be downloaded.
>