Microsoft has begun testing a cross-device continuity feature in Windows 11 that lets you pick up exactly where you left off in Spotify on your Android phone, right from your PC’s taskbar. The capability, rolling out to Windows Insiders in the Dev and Beta Channels as of August 22, 2025, introduces an Apple Handoff-style “Resume from your phone” notification. It’s the first public step toward a system-wide handoff experience between Windows and Android.
When the feature triggers, a toast appears on the Windows taskbar with the Spotify logo and a “Continue on this PC” button. Clicking it launches the Spotify desktop app—or offers a one-click Microsoft Store install if it’s missing—and resumes the exact track or podcast episode you were playing on your phone. The handoff requires the same Spotify account on both devices and an Android phone linked via the Link to Windows app.
How the resume magic works
The mechanism is built directly into the Windows 11 shell. After you pair your Android phone through Settings > Bluetooth & devices > Mobile devices and grant background access to Link to Windows, playing a song in Spotify on the phone sends a signal to your PC. Within seconds, the taskbar shows a “Resume” alert. Select it, and Windows deep-links into the Spotify client at the same playback position.
If the Spotify desktop app isn’t installed, Windows guides you through an automated Store installation before resuming. This one-click app-and-resume flow removes a common barrier to cross-device continuity. Behind the scenes, the feature relies on a new platform API that Microsoft is extending to developers, with Spotify as the inaugural partner.
Setup checklist for Insiders
To try the feature today, you need a few things in place:
- A PC on the Windows Insider Dev or Beta Channel with the latest preview update (build 26200.5761 for Dev, or 26120.5761 for Beta, delivered via KB5064093).
- An Android phone with the Link to Windows app signed in and allowed to run in the background—aggressive battery optimizations can block the handoff signal.
- The same Spotify account active on phone and PC.
You can nudge the feature to appear sooner by enabling “Get the latest updates as soon as they’re available” in Windows Update. Because it’s a controlled rollout, some Insiders on the correct build may still have to wait days or weeks before seeing the toast.
From WSA to cross-device bridging
The resume feature marks a strategic pivot for Microsoft on Android-Windows integration. In March 2024, the company announced it would deprecate the Windows Subsystem for Android (WSA), ending support on March 5, 2025. The Amazon Appstore on Windows shared that fate, closing new downloads a year earlier. Rather than running Android apps natively on the desktop, Microsoft now focuses on making the PC a seamless second screen for activities that start on your phone.
Cross-device resume picks up where Project Rome left off. That 2016 initiative promised “app portability” but never achieved mass developer adoption. Later, “Continue on PC” allowed sharing web pages via Edge, but Microsoft retired the dedicated iOS companion in 2021. The new approach embeds continuity directly into the taskbar—the most familiar Windows surface—and pairs it with the Store for frictionless app acquisition.
How it compares to Apple Handoff
Apple’s Handoff has long let users start an email, map route, or Safari tab on one device and instantly continue on another when signed into the same Apple ID. That experience is broad and mature, spanning multiple built-in apps and many third-party titles. Microsoft’s first version is narrower: one app (Spotify), one direction (Android to PC), and a single media scenario. But the intent mirrors Handoff’s core promise—pick up where you left off.
A key difference is platform control. Apple owns the hardware, OS, and app ecosystem, enabling tight, reliable proximity notifications. Microsoft must bridge Windows with a fragmented Android landscape where battery savers and vendor skins can interrupt background services. That’s why the setup guide stresses background permissions for Link to Windows and account parity within the target app.
Enterprise and privacy controls
For IT admins, the feature respects existing cross-device policies. Group Policy and MDM settings like “Continue experiences on this device” (EnableCDP) and “Phone-PC linking on this device” (EnableMmx) can already block these connections. A new “DisableCrossDeviceResume” CSP entry has appeared in Microsoft Learn for Insider builds, giving admins precise control over the toast notification.
Organizations that disable “Windows Consumer Features” may incidentally suppress the resume notification and other Phone Link experiences. For those who want the feature governed, the upcoming CSP provides a dedicated off switch. Privacy-conscious users should note that the handoff requires both devices to be linked and signed into the same Spotify account; the OS itself does not read or store playback data.
What developers need to know
Microsoft’s Insider blog explicitly invites developers to integrate with Resume. The API surface likely lets apps declare resumable states, validate user identity, and supply a deep link to restore context on Windows. For a music app, that could be a track URI and timestamp; for a document editor, a serialized state blob.
Essential considerations for builders:
- Identity parity: Confirm the signed-in user matches before restoring sensitive context.
- Deep linking: Accept protocol activations that reliably open to the correct screen without data corruption.
- Graceful failure: Handle cases where the desktop app is missing or outdated. Microsoft’s Store install flow helps, but your app should still manage version mismatches on launch.
- Opt-out options: Give users control over whether their app advertises resume signals, especially for sensitive content.
Project Rome’s muted uptake shows that platform continuity lives or dies by developer adoption. The new flow—taskbar toast to deep link—is simpler than any previous Windows cross-device API, which could attract more partners for media, messaging, and reading apps.
Early limitations and the road ahead
In this initial preview, cross-device resume is scoped exclusively to Spotify on Android handing off to the Spotify Windows client. There’s no iOS support yet, because the Link to Windows app is Android-only. The rollout is gradual even within Insider builds, so patience is required.
Hints of broader ambitions exist. Early Insider builds revealed settings toggles referencing WhatsApp and Spotify, suggesting messaging and communication apps could follow. Microsoft has also piloted a similar “resume” prompt for OneDrive-backed documents, nudging you to continue editing a file you had open on your phone. Neither is confirmed for public release, but they show the continuity vision extending well beyond media playback.
Real-world gotchas and pro tips
What works well:
- One-click entry: The taskbar toast is both a notification and an action button. No hunting through menus required.
- Automatic app install: If the desktop app is missing, Windows fetches it from the Store and then resumes playback—a surprisingly polished touch.
- Centralized pairing: Setup lives under Mobile Devices in Settings, avoiding confusion with the Phone Link app’s separate toggles.
Where you may stumble:
- Gradual flighting: Even with the right build, the feature may not appear for days. Enabling “Get the latest updates as soon as they’re available” improves your odds.
- Account mismatch: Resume breaks silently if different Spotify accounts are used on phone and PC—the toast may simply not appear.
- Battery optimization killers: Many Android OEMs aggressively throttle background apps. Exclude Link to Windows from battery restrictions to keep the handoff signal alive.
- Quiet hours: If Focus Assist is suppressing notifications, you’ll miss the resume toast entirely.
A small feature with big strategic weight
Cross-device resume may sound like a niche convenience, but it signals a major philosophical shift at Microsoft. Instead of trying to cram Android into Windows—a project that ended with WSA’s retirement—the company now treats the PC as a natural extension of the mobile experience. The phone is the first screen; Windows becomes the smart second screen where longer, more productive sessions happen.
Choosing Spotify as the debut partner is classic Microsoft pragmatism. It’s a widely used app with a clean session state and a huge user base, making the handoff demo instantly relatable. If the initial preview goes well, expect more apps to join—especially those where resuming context (a message thread, a draft, a reading list) adds obvious value. The fact that Microsoft teased this at Build 2025, then briefly pulled the demo video, suggests the company wanted to polish the experience before public testing.
The big open question is developer adoption. Windows has a history of introducing platform features that languish because app makers don’t invest. This time, the integration asks for very little: a lightweight API, a deep link, and a shared identity. If Microsoft pairs that with clear documentation and showcases real user delight, cross-device resume could finally deliver on the continuity promise that Project Rome never achieved.
For Insiders eager to try it: set up your phone link, open Spotify, and watch the taskbar. For admins: review your cross-device policies and prepare for questions. For the rest of us: keep an eye on future flight notes, because the Spotify handoff is likely just the beginning of a broader Android-to-Windows continuity story.