Apple's insistence on unnecessarily tying software releases to yearly hardware upgrades is a broken cycle for a services company; it needs to be more agile
This isn't the blog post intended to write. In fact, last night I drafted up one about my problems sending background push notifications with Amazon SNS (coming soon!).
Context & Ripple Effects
This piece lands in a decade-running argument about Apple's release cadence. Back in 2015, critics blamed marketing priorities for shipping software before it was ready, and The Next Web argued Apple should decouple apps like Apple Music from iOS updates so they could be patched through the App Store. In 2018, Learning By Shipping pushed back, framing the annual cycle as deliberate iterative evolution rather than negligence.
What changed by 2019 is the stakes: with Apple needing to transition into a services company earlier than planned, an annual big-bang release tuned to hardware launches looks increasingly mismatched to businesses that live on continuous iteration. Tyler.io's argument is essentially the 2015 critique re-weighted for a services era.
First-order effects
- Apple's own services — the apps critics have long wanted untied from iOS, like Apple Music — ship on the hardware calendar, so bugs reach hundreds of millions of users at once and wait up to a year for the next coordinated fix.
Second-order effects
- The App Store distribution channel Apple already operates makes the constraint self-imposed: first-party apps could iterate independently, which would put pressure on the internal process Learning By Shipping defended and force a choice between the two cadences.
Third-order effects
- If services keep growing as a share of Apple's business, the industry pattern points toward software decoupled from hardware cycles entirely — but the counterargument is real: the annual synchronized release is also what lets Apple ship at unprecedented scale, and abandoning it trades predictability for agility with no guarantee of better quality.
The trend: As Apple shifts from hardware company to services company, the decade-old tension between its annual synchronized release cycle and continuous software iteration is becoming a strategic question rather than a quality complaint.