/
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

Updating our built-in apps for Windows 8

MSDN Blogs Steven Sinofsky

Context & Ripple Effects

This post lands near the end of a year-long drip of Building Windows 8 posts that walked through the redesign piece by piece — the Start menu's replacement, the reworked Task Manager, the touch keyboard, and May's user-experience deep dive. Updating the built-in apps is the last visible layer of that sequence before general availability: the shell and input stories were already told, and this closes the loop by showing the same design language applied to the software every Windows PC ships with.

The pickup was broad for a developer-blog post — PC World, Engadget, CNET, The Verge, TechCrunch, ZDNet, The Next Web and Neowin all ran it on or about October 4 — which reflects how much weight observers were putting on any signal about the finished product ahead of launch. It also sits next to Microsoft's July post on making money through the Windows Store, where third-party developers were being recruited into the same visual and commercial system these built-in apps now exemplify.

First-order effects

  • Microsoft ships refreshed first-party apps as reference implementations of its new design language, giving every Windows 8 buyer an immediate demonstration of the interface described in the earlier UX and Start-menu posts.
  • Developers building mail, calendar or media apps against the Windows Store now have Microsoft's own apps as both a design template and a direct competitor in the same storefront.

Second-order effects

  • Third-party developers must differentiate against bundled apps that ship free and pre-installed, pushing monetization toward the store-based models Microsoft laid out in its July developer-post guidance.
  • PC makers preparing Windows RT hardware get a defined out-of-box app set to build their own preloads around, shaping how OEMs position value beyond the base OS.

Third-order effects

  • If the pattern holds, bundled apps stop being static OS utilities and become annually redesigned products — making the OS vendor a recurring participant in app categories it once merely hosted.
  • A platform where the vendor's own apps model the design rules tightens Microsoft's control over what a 'proper' Windows 8 app looks like, raising the bar for store acceptance and third-party polish alike.

The trend: Operating-system vendors are turning bundled applications into flagship design statements and competitive products, using them to define the platform's look and pressure third-party developers toward the store economy.