/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

All Apple Watch Apps Must Be Native Apps Starting on June 1

Apple today informed developers that starting on June 1, 2016, all watchOS apps submitted to the App Store must be native apps built with the watchOS 2 SDK or later.  —  When the Apple Watch first launched …

MacRumors Juli Clover

Context & Ripple Effects

The Apple Watch launched with a compromise architecture: as developers described in early coverage, first-generation apps were built with no access to the device itself, running as extensions of iPhone code and limited to what WatchKit allowed. Apple previewed watchOS 2 at WWDC in its new Watch software announcement, giving developers a year's runway toward a fully native SDK.

This deadline closes that transition: from June 1, 2016, every new App Store submission must be compiled against the watchOS 2 SDK or later, ending the era of companion-app-only Watch software roughly a year after Apple opened third-party Watch app submissions in the first place.

First-order effects

  • Developers still shipping WatchKit extension apps face a hard cutoff on June 1: any non-native submission is rejected, forcing rewrites against the watchOS 2 SDK for anyone planning new releases or major updates.

Second-order effects

  • Apps whose Watch experiences were thin companions now have to justify their existence natively — a pressure that culminates two years later when Instagram abandons its Apple Watch app entirely rather than maintain it under Apple's tightening native-app requirements (Instagram dropping its Watch app).

Third-order effects

  • Deadline-driven SDK mandates become a repeatable Apple playbook for platform maturation: the same submit-or-comply structure resurfaces in 2021, when Apple requires all iPhone, iPad, and Watch submissions to meet App Tracking Transparency rules by April 26 — using the App Store gate itself as the enforcement mechanism for architectural and policy shifts.

The trend: Apple is converging wearable software on fully native, on-device architectures, using App Store submission deadlines rather than deprecation notices to force the migration.