Windows Insiders in the Dev and Beta channels can now test a new feature that continues Spotify playback from an Android phone to a Windows 11 PC with a single click. Called Cross Device Resume, the capability appears as a taskbar alert and represents Microsoft’s pragmatic pivot away from running Android apps locally via the Windows Subsystem for Android (WSA), which was deprecated on March 5, 2025.

GitHub-based analyst and Windows Insider MVP Tero Alhonen first surfaced the rollout on social media after the feature skipped Microsoft’s own blog post for Build 26120.5761. “A staged preview of Resume (a.k.a. Cross Device Resume) has landed—Spotify is the first integration, and it works exactly as the demo hinted at CES,” Alhonen wrote. Microsoft later confirmed the availability in an updated announcement.

What is Cross Device Resume?

Cross Device Resume is a continuity feature that bridges Android apps and Windows 11. When you play a song or podcast in Spotify on your linked Android phone, the PC shows a “Resume” prompt on the taskbar. Clicking it opens Spotify on Windows and picks up exactly where you left off. If the desktop app isn’t installed, the system initiates a one-click Microsoft Store install, then resumes the session after sign-in.

The feature is deliberately conservative—starting with a single app—and relies on the existing Link to Windows (Phone Link) connection. It does not stream the phone’s screen or run Android code locally. Instead, it transfers a lightweight activity hint, or AppContext, from the phone to the PC. Windows maps that context to the correct desktop destination: a native app, a Store install flow, or even a web app if supported.

Builds and availability

Microsoft is rolling out Cross Device Resume as a controlled feature rollout to Insiders. The following builds carry the capability:

  • Dev Channel: Build 26200.5761
  • Beta Channel: Build 26120.5761 (KB5064093)

Because the rollout is server-gated, not every tester on these builds will see the Resume prompt immediately. Enabling “Get the latest updates as they’re available” in Settings > Windows Update can accelerate exposure, but patience is required. Microsoft has not yet provided a timeline for general availability.

How the plumbing works

Under the hood, Cross Device Resume uses three components:

  1. Link to Windows (Android app): Collects and publishes a compact, time-bounded AppContext—typically a URI, content metadata, and a timestamp—whenever a supported activity is detected. The app must run in the background and be exempt from battery optimizations on the phone.
  2. Windows 11 shell: Surfaces the Resume notification on the taskbar and orchestrates the one-click flow. It queries the Microsoft Store if the desktop app is missing and handles account sign-in prompts.
  3. Continuity/Developer SDK: Allows app developers to register deep-link protocols or desktop handlers so Windows knows exactly how to resume the session. Microsoft is adapting the existing Windows App SDK and URI activation model to support Win32, UWP, and packaged apps.

This architecture is a direct consequence of the WSA deprecation. WSA ran Android apps in a local Hyper-V virtual machine, but Microsoft ended support for that subsystem after March 5, 2025. With no native Android runtime, Cross Device Resume gives users a continuity experience without the overhead of emulating Android on the desktop.

Setting up the preview

To test the feature, follow these prerequisites:

  1. Join the Windows Insider Program and switch to the Dev or Beta channel. Install the latest preview build that includes the Resume capability.
  2. On the PC: Navigate to Settings > Bluetooth & devices > Mobile devices. Enable “Allow this PC to access your mobile devices” and pair your Android phone via “Manage devices.”
  3. On the phone: Download or open the Link to Windows app, sign in with the same Microsoft account used on the PC, and allow the app to run in the background. Exclude it from battery optimization to ensure reliable activity detection.
  4. Use Spotify: Sign in to the same Spotify account on both devices. Play a track or podcast on the phone, then watch for the Resume alert on the PC taskbar.

If Spotify is not installed on the PC, clicking the prompt will open the Microsoft Store to download it. After installation and sign-in, the session should continue automatically.

Real-world scenarios beyond Spotify

While the initial preview is limited to Spotify, Microsoft envisions broader use cases. The feature’s design supports:

  • Media continuity: Start a playlist on your phone during a commute, then resume on PC speakers when you sit at your desk.
  • Productivity micro-moments: Open a rideshare tracker or delivery status on the phone, then push it to a larger screen without fumbling for the app.
  • Messaging and approvals: Pick up a two-factor authentication prompt or conversation thread mid-flow on the phone and continue on the PC (pending developer integration).

These scenarios mirror the type of handoff experiences macOS and iOS have offered for years, but they are tailored to the heterogeneous Android-Windows ecosystem.

Comparison with Apple’s Handoff

Apple’s Handoff transfers live document states between devices using native system APIs, benefiting from tight hardware and OS integration. Microsoft’s Resume is less ambitious technically; it does not transfer a running session—only a context hint that launches an equivalent desktop destination. This is a pragmatic choice given the diversity of Android hardware and the absence of a shared runtime.

Where Apple’s model is seamless but locked to its ecosystem, Microsoft’s approach depends on developer adoption and consistent account sign-in. Spotify is an ideal first partner because it already maintains cross-platform session synchronization. For apps without a natural desktop counterpart, fallback options like web links could still provide value.

Developer path: How apps will join

Microsoft is actively soliciting developer interest for the Continuity/Resume SDK. Early documentation suggests developers will need to:

  • Publish a compact AppContext from the Android app (intent URI, content ID, timestamp).
  • Register a handler on Windows that can parse and act on that context, such as a protocol scheme or app execution alias.

The model is designed to work with Win32, UWP, and Windows App SDK apps, broadening the surface beyond Microsoft Store-only packages. Developers should also consider edge cases: what if the user is signed into different accounts on each device, or what if the desktop app is already running with a different session?

Privacy, security, and enterprise considerations

Cross Device Resume introduces new governance questions. The AppContext signals are small and ephemeral, but they still convey metadata about user activity. Microsoft has not yet published a dedicated enterprise policy for the preview, so IT administrators should treat it as experimental. Key concerns include:

  • Account alignment: Session continuation requires matching accounts across devices. Mismatched work and personal identities may trigger sign-in prompts or failed resumes.
  • Data exposure: Even limited metadata could reveal sensitive patterns. Admins will want clarity on retention, telemetry, and cross-tenant implications.
  • Device management: Existing MDM controls for Phone Link / Link to Windows can block the connection, but granular toggle for Resume is absent. Testers should file feedback requesting per-feature policy options.

For enterprise environments, Microsoft recommends validating the feature against internal security policies and monitoring the Feedback Hub for updates on administrative controls.

Limitations and known caveats

  • Staged rollout: Not all eligible Insiders will see the Resume prompt immediately. Server-side flags control exposure.
  • Single-app launch: Spotify is the only supported app today. Other apps require developer integration before they can offer similar behavior.
  • Android-only (for now): The preview works only with Android phones via Link to Windows. iPhone users are excluded due to platform restrictions.
  • No local Android runtime: This is a continuity feature, not a replacement for WSA. Users hoping to run Android apps natively on the PC will be disappointed.
  • Battery and background constraints: Aggressive OEM battery optimizations on Android can prevent Link to Windows from reliably publishing context hints.

What this means for the Windows-Android story

Microsoft’s shift toward continuity signals a pragmatic reassessment. Instead of recreating Android on the PC, the company is betting on context transfer and identity to make phone and PC behave as parts of a single workspace. This approach is lower maintenance and potentially higher impact for common tasks—provided developers and OEMs buy in.

The demise of WSA on March 5, 2025, forced this pivot. While WSA never achieved broad adoption, its deprecation left a gap. Cross Device Resume fills that gap with a more focused, OS-integrated alternative that feels native rather than bolted-on.

Looking ahead

Cross Device Resume is an incremental but meaningful step toward frictionless multi-device workflows on Windows. Starting with Spotify gives Microsoft a clear, low-risk test bed to validate the plumbing, identity model, and user interface. If the feature proves reliable and gains developer traction, it could become one of those quiet, everyday conveniences that make Windows feel more cohesive across the devices people actually own.

For now, Insiders can kick the tires, developers can explore the Continuity SDK, and IT admins should begin assessing policy implications. Microsoft has a long road to match the polish of Apple’s Handoff, but the foundation is now in place.