Windows 11 Preview Brings Apple Handoff-Style Spotify Resume from Android to PC

Microsoft is rolling out a new Android-to-PC handoff feature to Windows Insiders that lets you pick up a Spotify track exactly where you left off on your phone—with a single click on the desktop taskbar. The preview arrives in Dev build 26200.5761 and Beta build 26120.5761 via KB5064093, and marks the company’s most direct attempt yet to match the seamless continuity that Apple users have enjoyed for years.

The feature surfaces as a “Resume” toast above the taskbar system tray, nudging you to continue playback on the PC. If Spotify isn’t installed, Windows offers a one-click Microsoft Store install before launching the desktop app and resuming playback. It’s not mirroring, emulation, or streaming; instead, Windows 11 receives lightweight context from your Android session and opens the native desktop app to the right state.

The rollout, first spotted by Windows Insiders and confirmed in an official blog post, is limited to Spotify for now—but Microsoft has made it clear this is just the opening move in a broader cross-device strategy. The same approach could soon apply to messaging, reading, and productivity apps, creating a fluid web of activity across your phone and PC.

From Project Rome to practical handoff

Microsoft’s cross-device ambitions aren’t new. Almost a decade ago, the company introduced “Project Rome” with Windows 10, promising to let apps and services roam across devices. The vision was grand: start a task on one device, finish it on another. But developer adoption was tepid, and the feature set—largely buried in Graph APIs and an obscure “Timeline” view—never broke into mainstream consciousness.

In parallel, Apple rolled out Handoff in 2014 with iOS 8 and OS X Yosemite, allowing users to seamlessly transfer activities like email drafts, Safari browsing, and Maps directions between iPhone, iPad, and Mac. It worked because Apple controls the full stack—hardware, OS, and core apps. Microsoft faced a harder problem: bridging Windows to a fragmented Android ecosystem without owning either end outright.

The new Resume feature tries a different tact. Instead of asking developers to build against abstract APIs, Microsoft is starting with a concrete, high‑profile use case—Spotify playback—and delivering an OS‑level prompt that feels native. The implementation leans on three existing building blocks:

• Phone Link (formerly Your Phone): the bridge that pairs Android devices to Windows, handling notifications, calls, photos, and now cross‑device context.
• Cross‑Device Experience Host: a Store‑delivered component that manages cross‑device signals and UI surfaces like taskbar badges.
• Continuity SDK: a new developer framework that lets Android apps publish an “AppContext” (what you’re doing and where to resume) and Windows apps register how to open to that exact point.

Unlike the now‑deprecated Windows Subsystem for Android, which tried to run Android apps natively on Windows, Resume avoids emulation entirely. It hands off context to a native desktop counterpart. For Spotify, that means the PC client starts playing the same song at the same timestamp—no phone mirror, no VM overhead.

How the Spotify handoff works today

The experience is straightforward if you’re enrolled in the right Insider channel:

1. Pair your Android phone with Phone Link on the PC. Allow Link to Windows to run in the background on the phone.
2. Start playing a song or podcast in Spotify on the phone.
3. After a few seconds, a “Resume” badge appears on the PC taskbar showing the Spotify icon and the phrase “Continue on this PC.”
4. Click the alert. If the Spotify desktop app is installed, it opens directly to the track. If not, Windows initiates a one‑click Microsoft Store install. After signing in, playback resumes from the same spot.

Microsoft stages the rollout carefully. Even on the correct build, the alert may not appear immediately—the company uses controlled feature rollouts to gather telemetry before wider deployment. Enabling the “Get the latest updates as soon as they’re available” toggle in Windows Update can hasten delivery, but patience is sometimes part of the Insider experience.

Requirements beyond the Insider build include a functioning Phone Link setup, background permissions for Link to Windows, and a shared Spotify account across devices. The Cross‑Device Experience Host must also be present and up to date; if issues arise, installing it manually via winget install 9NTXGKQ8P7N0 can help.

Why Spotify? A safe proving ground

Spotify was a logical first partner. The service already has robust cross‑device awareness through Spotify Connect, which synchronizes playback state between phones, desktops, and speakers. By adding a native Windows shell prompt, Microsoft elevates an existing capability into an OS‑integrated feature. The one‑click Store install closes a common friction point—users needn’t have pre‑installed the desktop app to benefit from the handoff.

That said, Spotify’s own session management isn’t perfect. Some users report queue resets or inconsistent behavior when switching devices. Because Windows’ Resume triggers the desktop client directly, any quirks in Spotify’s cloud sync model—like a playlist that doesn’t carry over exactly—will be visible. Microsoft can’t fully control the app’s internal state, so the smoothness of the experience will depend partly on how well each service manages its own continuity.

How Microsoft’s approach compares to Apple’s Handoff

Both systems surface subtle affordances—a dock icon on macOS, a taskbar toast on Windows—that encourage users to complete a task on another device. But the underlying architectures differ sharply.

Microsoft is effectively playing catch‑up on convenience while working with a much more heterogeneous device landscape. The Limited Access gating for the Continuity SDK reflects a cautious approach: the company wants to validate privacy, reliability, and abuse protections before opening the doors wide. Early support will likely center on a handful of high‑impact partners while the platform hardens.

The strategic pivot after WSA’s demise

In early 2025, Microsoft ended support for the Windows Subsystem for Android, effectively killing the ability to run Android apps natively on Windows 11. The decision left a gap: what would replace the seamless smartphone‑PC crossover that WSA promised? The answer is this lighter, context‑driven handoff model.

Cross Device Resume doesn’t try to host a phone’s runtime on the PC. Instead, it acknowledges that most popular mobile apps already have desktop counterparts—Spotify, WhatsApp, Outlook, Edge—and simply passes a small metadata payload to pick up where you left off. That’s simpler to maintain, faster to launch, and more respectful of each platform’s strengths. It also avoids the licensing and performance headaches that plagued WSA.

In that light, Resume isn’t a consolation prize; it’s the practical evolution of Microsoft’s cross‑device strategy. Having learned from the over‑ambitious Project Rome and the resource‑heavy WSA, the company is now betting on a focused, partner‑driven platform that delivers immediate user value.

Developer opportunities and the Limited Access model

For developers, the Continuity SDK opens a clear path to add “pick up where you left off” without reinventing sync infrastructure. The workflow is straightforward:

• Android apps publish an AppContext—compact metadata describing the activity (track, document, conversation) and the URI or intent needed to resume it.
• Windows apps register protocol handlers or URI schemes to open directly into the corresponding view, document, episode, or thread.
• Because Resume is currently a Limited Access Feature, developers must submit scenario details and package information to Microsoft for approval.

This guarded onboarding makes sense during a preview. It lets Microsoft work closely with a select set of apps, iron out edge cases, and establish baseline privacy and reliability standards. Once the platform matures, expect a broader SDK release and a push for wider adoption.

Microsoft has already hinted at WhatsApp integration—a now‑deleted Build 2025 demo showed a phone badge inviting users to resume a conversation on the PC. Reading, document editing, and navigation are other obvious targets. If the company can land a few category‑defining partners, Resume could become a quiet but transformative quality‑of‑life feature for Windows 11.

Real‑world benefits—and lingering concerns

What works well:
- Native feel: The prompt is part of the Windows shell, governed by standard notification and privacy controls. No floating windows or remote streams.
- Frictionless app acquisition: The one‑click Store install eliminates the “I don’t have the desktop app” barrier, a subtle but powerful improvement.
- Performance and battery: By launching the native PC app, you avoid the latency and energy drain of mirroring your phone screen or running an Android VM.
- Clear developer model: The Continuity SDK gives partners a well‑defined contract for cross‑device handoff.

What needs attention:
- Narrow app support: Spotify alone won’t change daily habits. Until more apps ship integrations, Resume will feel like a demo.
- Background service dependency: Phone Link and Cross‑Device Experience Host must be healthy. Users who aggressively limit background processes may find handoff unreliable.
- Session‑state inconsistencies: The feature depends on the app’s own cloud sync. If Spotify’s queue doesn’t transfer perfectly, the experience suffers.
- Privacy transparency: Microsoft says only metadata is exchanged, not content, but clear user‑facing explanations about what moves between devices, for how long, and under what policies will be essential as more apps come online.

Step‑by‑step setup for early testers

If you’re running a compatible Insider build (Dev 26200.5761 or Beta 26120.5761), try the feature now:

1. Open Settings > Bluetooth & devices > Mobile devices. Enable “Allow this PC to access your mobile devices,” then click Manage devices to link your Android phone.
2. On your Android phone, launch the Link to Windows app and grant it background access.
3. Start playback in the Spotify mobile app.
4. When the taskbar Resume alert appears on your PC, click Continue on this PC to launch Spotify on the desktop. If not installed, approve the one‑click Store install.
5. If the alert doesn’t appear, ensure the “Get the latest updates as soon as they’re available” toggle is on in Windows Update, and keep checking after cumulative patches.

What comes next

The most obvious expansions align with how people actually switch between devices:

• Messaging and calls: Resume a specific WhatsApp conversation or Teams call in progress. The Build demo explicitly showed this path.
• Reading and writing: Continue an article from a mobile browser in Edge on desktop, or open the same draft you started on your phone in Outlook for Windows.
• Media and navigation: Jump from a podcast app to a Windows client at the exact timestamp, or pass a route from your phone to a maps experience on the PC.

If Microsoft can deliver these scenarios with the same one‑click simplicity as Spotify, the feature will shift from a curiosity to a daily driver. Enterprise IT will also want admin controls to scope which apps can publish and consume cross‑device context—a consideration Microsoft appears to be addressing through its guarded rollout.

A deliberate step toward seamless Windows

The Android‑to‑PC handoff in Windows 11 is modest in scope but ambitious in implication. It replaces clunky “share to PC” rituals with a taskbar‑native nudge that knows what you were just doing and helps you continue without breaking stride. Starting with Spotify gives Microsoft a safe, familiar sandbox to refine the plumbing before broadening to messaging, productivity, and beyond.

After years of chasing the dream of cross‑device continuity with uneven results, this preview feels different. The pieces are finally in place: mature Phone Link infrastructure, a cohesive shell UI, and a developer SDK that promises a clean integration path. The feature won’t rival Apple’s Handoff overnight—that will require a critical mass of partner apps and a track record of reliability. But if the rollout proceeds smoothly and partners sign on, Cross Device Resume could become one of the most useful upgrades to everyday Windows life, turning every PC into a natural extension of the phone in your pocket.