BT

Apple Requires WatchOS 2 for All New Watch App Submissions

| by Sergio De Simone Follow 14 Followers on Apr 26, 2016. Estimated reading time: 1 minute |

Apple has announced that new watchOS apps submitted after June 1, 2016 must be native apps built with the watchOS 2 SDK or later. Furthermore, Apple has refreshed its review guidelines for the App Store.

Apple announced watchOS 2 at WWDC 2015 to enable more powerful and fast apps. Among watchOS 2 main features are support for so-called native apps, i.e. apps that do not require an iPhone to run, and better support for Apple Watch hardware, such as Wi-Fi, digital crown, microphone, etc.

Yet, developers have been slow in updating their apps to watchOS 2. Runkeeper cofounder and CEO Jason Jacobs explained that moving to a native app entails a large amount of work that involve a complete rewrite as well as figuring out how to handle the communication between the watch and the iPhone. Mac Stories’ Federico Viticci pointed to the lack of incentives to explain developer “muted” response to watchOS 2 and why they ignored it.

In the past, Apple has generally followed a two-step approach to make sure that developers adopt its latest technologies, by first requiring that all new apps comply with a minimum SDK requirement, then extending that rule to also include updates to existing apps. Albeit successful with apps that are regularly maintained, this approach fails to address the problem of older apps that are not updated, as Viticci also remarks.

On a related note, Apple has also provided new review guidelines for the App Store, coming six months after their last update. Most notably, the new guidelines introduce a requirement that will affect all apps using background location services – i.e., apps that track your location in the background – by requiring them to specify a reason when asking for user permission.

Additionally, all keyboard extensions are now required to actually support the typing of characters, whereas a few apps have been known to install keyboards to provide a cross-application UI to handle features such as clipboard management, etc.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT