/
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

Workflow automation app has no ‘further updates planned’ following Apple acquisition

Benjamin Mayo / 9to5Mac :

9to5Mac Benjamin Mayo

Context & Ripple Effects

When Apple bought Workflow in March 2017 it kept the three-person team and made the app free, which read as an acqui-hire with the product left on life support (kept the three-person team and made the app free). A month later, Apple's own updates restored some Chrome and Pocket actions but other post-acquisition removals stayed missing (restored some Chrome and Pocket actions), already signaling selective maintenance rather than active development.

'No further updates planned' confirms the sunset: Workflow was talent-plus-technology, not a product Apple intends to grow. The destination is visible in the corpus — the automation idea survives inside Apple's own Shortcuts app, which by iOS 27 builds workflows from natural-language prompts (builds workflows from natural-language prompts).

First-order effects

  • Existing Workflow users are left with a frozen app whose removed actions stay gone, while the three founders work on Apple's internal automation efforts rather than the standalone product.

Second-order effects

  • Third-party services lose a neutral cross-app automation surface on iOS — the pruned non-Apple integrations show Apple folding connectivity into tools it controls, pushing developers to build for Shortcuts instead.

Third-order effects

  • If the pattern holds, iOS automation consolidates from independent utilities into OS-native features: Apple absorbs promising apps, sunsets them, and re-emerges the capability as a first-party feature — eventually one driven by natural language rather than manual action-chaining.

The trend: iOS automation is migrating from independent third-party apps into Apple-native tooling via acqui-hire-and-sunset, culminating in AI-generated workflows inside Shortcuts.