Windows 11 Insiders on the Dev and Beta channels can now move a listening session from their Android phone to a PC with a single click, no copy‑and‑paste, no manual app hunting. The feature, called Resume, rolled out on August 22, 2025, in Build 26200.5761 (Dev) and Build 26120.5761 (Beta). It surfaces a small taskbar alert when you have been playing something in Spotify for Android; clicking the alert launches Spotify for Windows—or installs it automatically from the Microsoft Store—and picks up playback exactly where your phone left off.

This is the first public step of what Microsoft calls Cross Device Resume, a Handoff‑like capability that transfers activity context between devices rather than mirroring an Android app on the desktop. The company had teased the concept earlier this year, but the August Insider push turns it into a tangible, though limited, experience.

Not a return of Android apps on Windows

The announcement comes just months after Microsoft ended support for the Windows Subsystem for Android (WSA) on March 5, 2025. WSA allowed Windows 11 to run Android apps natively from the Amazon Appstore, but its retirement signaled a strategic pivot. Resume does not bring back Android emulation; it instead leans on Phone Link and a new set of continuity APIs to hand off context from the mobile app to its native Windows counterpart.

This distinction is crucial. When you resume Spotify, you aren’t running the Android app on your PC. The desktop client takes over, synchronized in state through your account. The approach side‑steps the complexity and security burden of hosting a full Android runtime and, Microsoft hopes, will push developers to maintain first‑class Windows applications that can accept rich handoff intents.

How the handoff works

The visible mechanics are simple. After linking an Android phone to your PC through Phone Link (Link to Windows), starting a song or podcast on Spotify for Android triggers a “Resume” notification on the Windows 11 taskbar. Click it, and one of two things happens:

  • If Spotify is already installed, the desktop app opens and jumps directly to the track or episode, resuming playback at the precise position.
  • If Spotify isn’t installed, Windows prompts a one‑click Microsoft Store install, then launches the app after sign‑in to resume the session.

Behind the scenes, Microsoft has built on the Cross‑Device Experience Host and Phone Link infrastructure. Developers can tap into a Continuity SDK that provides “Cross Device Resume (XDR)” guidance. The feature is gated as a Limited Access Feature, requiring Microsoft’s approval; only vetted apps can participate initially. That gives the company tight control over what context crosses devices and how it is secured.

Why Spotify first?

Media is a natural proving ground for continuity. It is self‑contained, easy to demonstrate, and immediately satisfying. Microsoft showcased Spotify when it first previewed Cross Device Resume during a now‑deleted Build 2025 demo, so the Insider rollout aligns with that early look. The company hasn’t committed to a specific roadmap, but references to third‑party toggles—including WhatsApp—have surfaced in preview builds, hinting that messaging and other media apps are near‑term targets.

Step‑by‑step for Insiders

If you are on the right builds and have the feature staged to your device, setting up Resume is straightforward:

  1. On your Windows 11 PC, go to Settings > Bluetooth & devices > Mobile devices and turn on “Allow this PC to access your mobile devices.” Then click Manage devices and follow the prompts to link your Android phone.
  2. On your Android phone, open the Link to Windows app and allow it to run in the background (disable battery optimization for the app if needed).
  3. Start playing a song or podcast in Spotify for Android.
  4. Look for a “Resume” alert on your Windows 11 taskbar. Click it to continue listening on your PC. If Spotify isn’t installed, let Windows handle the Store install and sign into your Spotify account when prompted.
  5. Playback should begin exactly where you paused on your phone.

Because the feature is rolling out via Controlled Feature Rollout (CFR), not every Insider on the correct build will see it immediately. Keep the “Get the latest updates as soon as they’re available” toggle enabled in Windows Update and check after cumulative updates.

Requirements at a glance

  • Windows 11 Insider Preview Build 26200.5761 (Dev) or 26120.5761 (Beta).
  • An Android phone linked via Phone Link / Link to Windows, with background activity permitted.
  • The same Spotify account signed in on both devices.
  • Internet connectivity on both devices for context sync.
  • A Microsoft Store account if the desktop app needs to be installed.

Privacy and trust

Handoff features inevitably raise questions about data flow. Microsoft’s documentation for Phone Link’s task continuity states that mobile apps can share recent URLs and document links to a Windows PC, and that transfers are governed by the company’s privacy commitments—data is not retained beyond user control. The Resume‑level integration adds another layer: the Continuity SDK mandates that only trusted Microsoft packages broker interactions, and the limited‑access gate lets Microsoft review which apps can participate. Still, users should review app permissions on Android and decide whether they are comfortable with cross‑device data sharing before enabling the feature.

A broader cross‑device strategy

Resume is the latest piece in a multi‑year effort to make Windows a hub for phone activities. Earlier iterations like “Continue on PC” in Windows 10 could push a web link from phone to desktop, but they felt piecemeal. The current push integrates phone features more deeply into the shell: Start shows recent messages, calls, photos, and phone battery; the taskbar now surfaces continuity hints.

By retiring WSA, Microsoft consolidated its mobile strategy around Phone Link and the Continuity SDK. Instead of trying to run Android apps directly, Windows is now a context router—receiving signals from the phone and directing them to the best PC target (a native app, a web app, or a deep link). It’s a lighter, more scalable approach that respects platform boundaries, and it creates a strong incentive for developers to offer robust Windows clients.

Strengths and early positives

Even in its infancy, the feature shows several promising attributes:

  • Frictionless onboarding: The automatic Store install removes the “I don’t have that app” dead‑end and makes handoff feel native, not bolted on.
  • Shell‑level integration: The taskbar alert mimics where users already look for app controls, much like Apple places Handoff cues near Dock icons.
  • Security posture: Limited Access Feature approval and trusted‑broker model give Microsoft tighter control than generic clipboard sync or full device mirroring.
  • Developer clarity: The Continuity SDK outlines specific prerequisites for Android and Windows projects, reducing trial‑and‑error.

Limitations to watch

The current implementation is intentionally narrow, and several gaps remain:

  • Single‑app scope: Today, only Spotify works. Broader categories—messaging (WhatsApp is expected), note‑taking, reading apps, browsers—are needed to make Resume a daily habit. Timelines are unconfirmed.
  • Windows app dependency: Handoff is only magical when there’s a first‑class Windows target. Services without a solid desktop client or progressive web app may see a degraded experience (e.g., opening a generic page without deep context).
  • Insider‑only and throttled: The feature is gated behind Insider builds and a staged rollout; mainstream users won’t get it until it reaches the Release Preview Channel.
  • iOS constraints: Apple’s platform restrictions make deep app‑to‑app handoff from iPhone to Windows much harder. Microsoft’s continuity APIs focus on Android, and there’s no equivalent iOS Continuity SDK today. Phone Link for iPhone supports calls, messages, and limited file sharing, but not rich activity resume.

How it compares to the competition

Apple’s Handoff remains the gold standard, seamlessly moving activities between iPhone, iPad, Mac, and Apple Watch. Microsoft’s approach is converging on the same user benefit but with Android as the mobile partner and Windows as the desktop hub. The difference is architectural: Apple controls the entire stack, while Microsoft must bridge two ecosystems through services and APIs.

Intel’s Unison, once a promising cross‑device layer, has been sunset, putting more pressure on Microsoft’s first‑party stack to deliver. Windows’ advantage is its massive install base and tight shell integration; the challenge will be rallying third‑party developers to support the Continuity SDK with the same urgency seen in Apple’s ecosystem.

For developers: What’s required to participate

Microsoft’s “Cross Device Resume (XDR)” guidance gives Android developers the hooks they need:

  • Limited Access request: Provide your app’s package ID, store URL, and screenshots of the native UX to get approval.
  • Android prerequisites: Minimum SDK level 24, Kotlin 1.9.x, and explicit metadata in AndroidManifest that declares your app as a resume context provider.
  • Windows prerequisites: The desktop target must accept resume intents or deep links that land users at the exact activity—a document ID, thread ID, playback position, or URL with scroll anchor. Even if your Windows presence is a PWA or classic Win32 app, you need a way to receive and process that context.

The payoff: fewer drop‑offs when users switch devices and a more “native to Windows” feel for your service without building an emulator‑friendly Android experience.

What’s next?

Based on demos and documentation cadence, the most logical expansions include:

  • Messaging handoff: Jumping into a WhatsApp or Teams conversation on the desktop exactly where you left off on your phone.
  • Document continuity beyond OneDrive: The task continuity API already covers URLs and cloud files; third‑party editors could plug in to hand off open documents.
  • Media and reading apps: Podcasts, audiobooks, and long‑form reading apps are low‑friction expansions—any context with a clear “position” maps well to Resume.

As with any Insider feature, timelines can shift. If Microsoft can demonstrate low latency and high reliability, and if developers embrace the SDK, Resume could graduate from a nifty demo to a daily habit for millions of Windows users.

The bottom line

Android app handoff in Windows 11 won’t run your phone’s apps on your desktop. Instead, it brings the same activity to your PC’s native app, instantly. After years of dabbling with cross‑device ideas, Microsoft has found a focused, shell‑native approach that feels modern: context‑first, privacy‑aware, and developer‑extensible via a formal SDK. With WSA in the rearview, this is the path forward for Windows and Android together—lighter, faster, and, if partners deliver, finally seamless.

For Insiders, it is a glimpse of a future where the gap between phone and PC narrows not through virtualization, but through intelligent context transfer. For everyone else, it is a signal that Microsoft is serious about making Windows the hub of your digital life, one click at a time.