/
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

An Open Letter to Apple

Dear Apple: It's your friends from Readability.  Remember us?  You put our technology into your Safari browser last year.  We're writing this open letter because - well - we're a little upset right now.

Readability Blog Richard Ziade

Context & Ripple Effects

This letter lands less than a week after Apple introduced new subscription rules requiring digital-content sales inside iOS apps to run through its In-App Purchase system — the pickup list shows how fast the story travelled, from TechCrunch's warning that "all SaaS" was in trouble to a New York Times piece framing it as two platforms with two sets of problems. What stings extra for Readability is that Apple had put its reading technology into Safari just the year before, making this an open letter from an existing Apple partner rather than a stranger.

It also continues a recognizable genre from 2010: John Battelle's open letter to Apple about how it talks to its peers and hugo's letter to Steve Jobs both used the same public-letter format to press Apple on its closed posture. Marco.org's same-day analysis of the In-App Purchase requirement gave developers a technical read on exactly what the rules demand, which is why this round of pushback has more substance than complaint alone.

First-order effects

  • Readability's own iOS app now sits in limbo: under the new In-App Purchase requirement, selling subscriptions outside Apple's system risks rejection or removal, directly threatening the revenue model behind a product whose technology Apple already ships in Safari.
  • Every developer selling subscriptions through iOS — the group TechCrunch summarized as "all SaaS" — must decide immediately whether to hand sales to Apple's checkout or rework their apps before enforcement.

Second-order effects

  • Publishers and service developers start weighing web delivery as an escape hatch, shifting investment away from native iOS apps toward experiences Apple cannot tax at the point of purchase.
  • Rival platforms gain a talking point: any competitor that permits direct billing can court the developers Apple just alienated, turning Apple's strictness into a recruiting pitch.

Third-order effects

  • If enforced as written, app stores stop being mere distribution channels and become toll booths on recurring revenue — meaning every subscription business's margin becomes subject to a single company's terms, a structure likely to draw sustained scrutiny beyond this one letter.
  • Developer relations becomes a durable competitive axis: the pattern of public letters suggests that how a platform treats its own partners will increasingly shape where independent software chooses to build.

The trend: Mobile platforms are extending their take from one-time app sales into recurring subscriptions, forcing every content and SaaS business to negotiate with the storefront that controls access to its customers.