Microsoft has begun public testing of a native Android-to-PC handoff feature that lets users resume activities from their phone directly on Windows 11 with a single click — starting with Spotify. The move arrives nearly a year after the company announced it would discontinue the Windows Subsystem for Android, marking a strategic pivot from running Android apps locally to a lightweight, intent-based continuity model.

The Windows Subsystem for Android (WSA) met its end-of-support date on March 5, 2025, leaving behind a gap for users who relied on Amazon Appstore apps. WSA allowed Android applications to run natively on Windows, but it was an expensive maintenance commitment and never achieved broad adoption, partly due to the absence of official Google Play Store support. Microsoft’s new Cross-Device Resume feature — first spotted in Insider builds in August 2025 — answers a different question: not “how can we run Android on Windows?” but “how can we pick up where you left off on your phone?”

From WSA to Cross-Device Continuity

Project Rome, “Continue on PC,” and the Phone Link app all represent earlier attempts at bridging mobile and PC workflows. WSA was a more ambitious bet: full-blown Android runtime on the desktop. When Microsoft ended WSA support, many wondered how the company would maintain relevance in a world where users increasingly expect seamless device switching. The answer now taking shape is a contextual handoff system that transfers session state — not pixels or runtimes — between an Android phone and a Windows 11 PC.

Rather than stream the phone’s screen or run Android in a VM, Cross-Device Resume uses a lightweight “AppContext” published by the phone. Windows consumes this signal and, through deep link handlers and the Microsoft Store, opens the corresponding native desktop app or web fallback to restore the user’s place. The first public integration is with Spotify: start playback on your Android handset, and a taskbar notification offers to resume on your PC exactly where you were.

How the Handoff Works Technically

The system builds on the existing Phone Link / Link to Windows bridge. On the phone, the app publishes a short-lived AppContext containing the current playback position, track, and other identifiers. Windows picks up this intent and checks whether the Spotify desktop client is installed. If it is, the app launches and restores session state via a deep link. If not, Windows triggers a one-click Microsoft Store install, signage into the same account, and then resumes playback — all without manual searching or re-authentication. This “install and resume” flow is central to the user experience, lowering friction for new or secondary PCs.

The Continuity SDK — still in limited-access testing — is what app developers will use to publish AppContexts and register desktop handlers. Microsoft’s documentation describes a model where Android apps define a compact intent, and Windows maps that intent to a registered UWP, Win32, or web endpoint. Unlike WSA, no Android emulation occurs; the desktop app is a first-class Windows application. This approach leverages the strengths of the Windows ecosystem while honoring the reality that the phone remains the authoritative runtime.

The Insider Preview Experience

The feature is rolling out as a server-gated cumulative update (documented as KB5064093) to Dev and Beta Channel Insiders on builds 26120 and 26200 series. Testers need to:

  • Enable “Allow this PC to access your mobile devices” in Settings > Bluetooth & devices > Mobile devices.
  • Pair their Android phone via Link to Windows, signed into the same Microsoft account.
  • Exempt Link to Windows from battery optimizations on the phone.
  • Sign into the same Spotify account on both devices.

When playback starts on the phone, a “Resume from your phone” alert may appear on the taskbar. Clicking it launches Spotify on the PC at the same timestamp. Because the rollout is staged, not all eligible Insiders will see it immediately. Microsoft often gates features to manage load and gather incremental feedback.

Comparing Apple Handoff and Google’s Multi-Device Efforts

Apple’s Handoff has long set the standard for intra-ecosystem continuity, relying on iCloud and OS-level hooks across iOS, iPadOS, and macOS. Microsoft’s challenge is different: it must orchestrate handoff between a third-party mobile OS (Android) and an expansive, historically heterogeneous Windows app model. Google has its own continuity features between Android and ChromeOS, but Microsoft’s play targets the massive installed base of Windows PCs paired with Android phones — a far more common combination than Android tablets or Chromebooks.

Starting with a focused, low-risk scenario like media playback allows Microsoft to test UX, performance, and developer APIs before tackling more complex handoffs such as messaging, document editing, or navigation.

Developer Incentives and the Continuity SDK

For Cross-Device Resume to grow beyond Spotify, developers must integrate the Continuity SDK. The work involves:

  • Publishing an AppContext from the Android app.
  • Registering deep link handlers or providing a web fallback that can restore session state.
  • Ensuring identity interoperability (same user account across phone and PC).

The carrot is clear: apps that support resume deliver a smoother cross-device experience, potentially increasing engagement on desktop clients. However, developers face real hurdles — understanding Windows deep-linking mechanics, maintaining session hygiene across authorization boundaries, and prioritizing integration work for a feature that is still in limited preview. Microsoft’s early outreach to partners will determine how quickly the roster expands.

Privacy, Security, and Enterprise Concerns

Automatically resuming sessions across devices raises valid security questions. The feature hinges on a shared Microsoft account and background execution of Link to Windows. In enterprise or regulated environments, unexpected handoffs could violate data residency or compliance policies. Key concerns include:

  • Account linking: Shared or misconfigured accounts might surface content on the wrong PC.
  • Background permissions: Android battery optimizations often kill Link to Windows, breaking continuity. IT admins need clear controls to manage this.
  • Data transit: While AppContexts are lightweight session descriptors, enterprises must understand what metadata flows and whether encryption is applied.
  • Group Policy / MDM: As of the early preview, there are no documented administrative controls to disable or audit Cross-Device Resume. Until Microsoft provides enterprise tools, cautious IT teams may block the feature entirely on managed devices.

Microsoft’s preview is a consumer test bed; enterprise readiness will require robust documentation, transparent telemetry, and policy controls.

Limitations and Risks

  • Narrow app support: Only Spotify is confirmed; users will see limited benefit until more developers adopt the SDK.
  • Server-gated rollout: Even Insiders on the required build may not see the feature for weeks.
  • Account parity: Both devices must use the same service account; mismatches break handoffs or force re-authentication.
  • Not a WSA replacement: Users who need local Android runtime capabilities must turn to third-party emulators. Cross-Device Resume solves continuity, not general Android app execution.
  • Tentative timeline: The feature’s mechanics may change before a wider release. Microsoft edited out a Build demo previously, signaling that the experience is still under active development.

Why Microsoft’s Approach Matters

The new handoff model has practical strengths:

  • Low friction: One click to continue, with a seamless install path if the app is missing.
  • Leverages existing investments: By keeping the phone as the runtime engine and using lightweight context signals, Microsoft avoids maintaining an Android runtime on every PC.
  • Plays to Windows strengths: Windows has a rich desktop app ecosystem. Resuming to a native client often provides a better experience than a streamed phone screen.
  • Consumer-friendly: It mirrors the simplicity users expect from Apple’s Handoff but operates across a heterogeneous device mix.

What to Watch Next

  • Developer adoption: Will messaging, productivity, and navigation apps follow Spotify? The feature’s utility depends on ecosystem buy-in.
  • Performance across networks: Handoff must be reliable on mixed cellular-to-Wi-Fi transitions and across aggressive Android OEM power management.
  • Enterprise controls: Microsoft must deliver MDM policies and audit capabilities before IT departments will embrace the feature.
  • Product positioning: The company needs to articulate where continuity fits alongside web apps, traditional desktop software, and future cross-platform plans.

Microsoft’s Cross-Device Resume test is a pragmatic re‑imagining of device-to-device continuity. It replaces the heavy lift of WSA with a nimble context-transfer model that takes advantage of Windows’ native app strengths. For users, the immediate payoff is tangible: fewer context switches, faster productivity, and one less reason to pick up a phone when a PC is already at hand. The feature’s long‑term success, however, will be measured not by a single Spotify demo, but by whether Microsoft can attract developers, address enterprise concerns, and deliver the kind of seamless experience that Android and Windows users have long been promised.