/
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

Microsoft plans to end support for SwiftKey on iOS and delist the app from the App Store on October 5; Microsoft will continue to support SwiftKey for Android

Questions about what's going on with Microsoft's support of the predictive SwifKey keyboard app for iOS have been bubbling up over the past few weeks.

ZDNet Mary Jo Foley

Context & Ripple Effects

Microsoft acquired SwiftKey with a commitment to maintain both mobile versions, and later steered iOS Word Flow users toward it when Word Flow was shut down. Ending the iOS version therefore removes the successor Microsoft itself had positioned for those users.

The move also fits Microsoft’s earlier withdrawal of its dedicated Cortana mobile apps. But SwiftKey’s subsequent return to the iOS App Store after customer feedback shows that the planned delisting encountered a meaningful user response.

First-order effects

  • SwiftKey’s iOS users face the app’s removal from the App Store and the end of Microsoft support, while Android users retain the product.
  • Microsoft narrows SwiftKey from the cross-platform mobile app it pledged to develop after its acquisition to an Android-only offering.

Second-order effects

  • The shutdown leaves former iOS Word Flow users without the SwiftKey replacement Microsoft previously recommended, increasing pressure to use another iOS keyboard.
  • Customer reaction became an operational constraint for Microsoft: the later App Store return reversed the planned removal rather than leaving the iOS exit in place.

Third-order effects

  • Taken alongside the Cortana mobile-app shutdown, the episode points to a more selective Microsoft approach to standalone consumer mobile apps, even where it owns established cross-platform products.
  • The reversal suggests that app-store withdrawal is not necessarily final when an installed user base makes a product’s removal costly in customer goodwill.

The trend: Microsoft is concentrating support around products and platforms it chooses to sustain, while user feedback can still alter planned exits from consumer mobile apps.

Discussion

  • @keleftheriou Kosta Eleftheriou on x
    The terrible 3rd-party keyboard APIs on iOS strike again: “if Apple doesn't grant access to certain interfaces, there's no easy or good way to make a product which needs integration to work.” https://twitter.com/...
  • @foxfortmobile @foxfortmobile on x
    Now with non removable ios 16 paste alert when any app/keyboard wants to access your clipboard, many products are going to die. Like swiftkey! Stupid apple does not want to allow a proper api for a clipboard manager tools. That's also why my own app pycopaste is paused.😒 https://…