Microsoft details Project Westminster, one of four bridges for converting apps on other platforms into Universal Windows apps
Microsoft plugs Westminster as one of its four bridges to the future of Windows Universal Apps — Project Westminster is a way of converting web-based apps into Windows 10 apps.
Context & Ripple Effects
Project Westminster is the fourth piece of Microsoft's bridge strategy, following the two SDKs announced in April that let Android and iOS code be ported to Windows 10 and let web apps be packaged for the Store. With Westminster detailed, all four conversion paths — web, Android, iOS, and Win32 — are now on the table, each aimed at the same problem: filling the Windows Store's app gap without asking developers to rewrite anything.
The stakes become clear in how the strategy plays out afterward: Microsoft open-sources an early preview of the iOS bridge toolkit within a month, while the Android-side effort is abandoned entirely with Project Astoria's cancellation in February 2016, leaving web, iOS, and Win32 as the surviving paths.
First-order effects
- Web developers gain a direct route into the Windows Store — an existing web app can be packaged as a Universal Windows 10 app without a rewrite, making Microsoft's store the cheapest of the major platforms to list on.
- Microsoft's Store catalog problem now has four parallel solutions under active development, with Westminster covering the largest installed base of software: the open web.
Second-order effects
- The bridge bet raises the bar for Apple and Google's own store lock-in: if packaging a website counts as a store app, Microsoft is effectively importing the entire web as its catalog rather than courting native ports one at a time.
- Internally, the four-bridge structure forces triage — Astoria's later cancellation shows the Android path couldn't be sustained, concentrating Microsoft's porting effort on the iOS and web routes.
Third-order effects
- If the conversion-tooling pattern holds, Windows development consolidates around a single unified platform rather than parallel APIs — which is where the arc eventually lands with Project Reunion in 2020, Microsoft's attempt to reduce fragmentation between Win32 and UWP after the bridge era.
- A decade of bridge-and-unify cycles suggests the durable lesson: developer reach on Windows is pursued through lowering migration costs rather than through exclusive native incentives.
The trend: Microsoft's app-gap fix has moved through successive conversion tools toward platform reunification, with each bridge generation absorbing the failures of the last.