This specification is designed to extend the [JSON Wire
a W3C working draft for web browser automation. The JSONWP has been greatly
successful for that purpose. The need for automation of native and hybrid
mobile applications can be met by the extension of the JSONWP, which already
has a proven basic automation framework (architecture, interaction model,
This feature is about to change app delivery and installation.
Before App thinning uses were given package of the apps including some resources and binaries that were not going to be used on their devices.
App thinning uses the three ways to improve app delivery and installation.
Using image assets in Xcode will allow App Store to create a specialized app bundle including only the assets that fit the users device.It will also only include architecture specific binary in that binary such as 32 or 64 bit.
Put artwork in the asset catalog and tag it for individual platforms..other than that everything is same appstore will take care of compiling and giving the device specific things while installing.
On Demand Resources:
Developers will now able to host additional content in the App-store and the app can fetch some resources only when needed.
We have to assign tags to different chunks of code and these things will be downloaded when needed….If OS wants to make free space these things will be purged and dowloaded when needed from app-store
Developer will have the permission to say which tagged thing should be deleted first if OS needs to purge and developer will be able to specify what code is needed for first time launch.
Apps now can be submitted as LLVM Bitcode(intermediate language) instead of native executables and AppStore will take care of comipiling to native binaries.
Its by default on in iOS and can be optional to iOS apps but Mandatory in iwatch apps
LLVM -> Low Level Virtual Machine...A compiler that has the ability to act as JIT(Just in Time)