Wednesday, 15 September 2010

app store - WatchKit apps/extensions and iOS backwards compatibility -


I have an iOS app with the deployment target for the iOS 6.1 version and the base SDK for the latest iOS. I've added the Watchchit app and the watchkit extension goal for the project, but I'll need to understand how it will affect the presentation in the app store in the future:

1) What two executable files generate? IOS app + second for watchkit extensions and for the watchchit app? Or are all packaged in a unique executable file?

2) Can it handle the iOS version of the device automatically, which is installing the app? I mean: The user must download and install the update from the App Store , and then he will be requested to install the iOS app only if his version is 8.1 - and it is requested that both iOS apps And the watchchit app if he has iOS 8.2+ and an amazing Apple Watch? Has Apple provided such information?

Apple has provided a lot of information about the Watchkit app and extension. Before going with the project, read them first. For example, you can find information about the Watchkit architecture and how WatchKit applications and extensions work together with the iOS app.

Also, keep in mind that these things can change completely later this year.

Advertising 1) Only one executable is generated, in which all these parts are included. The user will already download your app from the app store first.

Advertising 2) Your iOS app will run on the lowest iOS target set in your project, in your case 6.1, though the watchkit app was included. However, the Watchchit app will be available to users only for iOS 8.2 and above - and of course they will need applewatch.


No comments:

Post a Comment