Microsoft just took a page from Apple’s playbook, and then tried to erase it. During its Build 2025 developer conference, the company demoed a new Cross-Device Resume feature that mirrors Apple’s Handoff: start listening to a podcast on your Android phone, and a click on your Windows 11 PC’s taskbar picks up exactly where you left off. Then it edited the demo out of the official video. The feature, however, didn’t disappear—it’s already rolling out to select Windows Insiders in the Dev and Beta channels as a staged, telemetry-gated preview in build 26120.5761 (KB5064093). The initial test case is Spotify, but Microsoft’s own documentation and developer outreach suggest far broader ambitions.
A Cross-Device Resume, Years in the Making
The concept isn’t new. Apple’s Handoff has been baked into macOS and iOS for nearly a decade, letting users seamlessly transition between Mail, Safari, Messages, and dozens of third-party apps. Microsoft’s previous attempts at device continuity—like the doomed Windows Subsystem for Android (WSA) and the Amazon Appstore partnership—fizzled out, with WSA’s deprecation announced earlier. That context makes this new effort both surprising and strategically important. The company isn’t resurrecting WSA; instead, it’s leveraging the existing Link to Windows (Phone Link) ecosystem to create a lightweight, cloud-aware bridge between Android and Windows 11.
At Build, senior product manager Aakash Varshney showcased the flow: open Spotify on an Android phone, and a subtle badge appears on the Spotify icon pinned to the Windows 11 taskbar. Hovering over it reveals a “Resume, recently opened on your mobile device” prompt. One click launches the desktop Spotify client and continues playback from the same timestamp. No manual searching, no re-authentication. The experience is so close to Handoff that it drew immediate comparisons—and likely prompted Microsoft to pull the demo, perhaps to avoid being labeled a copycat before the full vision was ready.
What’s in the Insider Build (and What’s Not)
The Insider preview notes for build 26120.5761 (and the parallel Dev channel build 26200.5761) are explicit about what’s live now:
- A “Resume” alert on the Windows 11 taskbar, triggered when an eligible Android app (currently only Spotify) is active on a paired phone.
- If the corresponding desktop app isn’t installed, clicking the alert initiates a one-click Microsoft Store install, followed by an automatic sign-in and session restoration.
- A new Resume API that third-party developers can adopt to define their own resume semantics—what state to capture and how to restore it.
- No support for complex app states (unsaved documents, in-progress edits) or apps without a native Windows counterpart. The initial scope is deliberately narrow: media playback state is easy to synchronize, poses minimal privacy risk, and validates the technical plumbing.
The feature is not enabled for every Insider. Microsoft is using its typical A/B gating, meaning two identical PCs on the same build may not show the same behavior. That controlled rollout is a direct response to the WSA debacle—the company wants telemetry and feedback before committing to a broader launch.
Setup: A Three-Step Ritual
There’s no magic here, but the prerequisites are non-negotiable:
- On the Windows 11 PC: Settings > Bluetooth & devices > Mobile devices → turn on “Allow this PC to access your mobile devices,” then pair the Android phone via Manage devices.
- On the Android phone: Install or update Link to Windows (the companion to Phone Link), sign in with the same Microsoft account, and grant background permission so the app can report active sessions to the PC.
- Using the same Spotify account on both devices, start playback on the phone. Wait for the taskbar alert, click it, and resume on the desktop.
If the alert never appears, the feature likely hasn’t been white-listed for that Microsoft account or device. The recommended next step: file Feedback Hub reports and wait. Patience is the price of bleeding-edge Windows.
Why Spotify? The Smart, Low-Risk Proving Ground
Choosing a single, widely-used media app as the launch vehicle is an engineering masterstroke. Playback state is unambiguous—a track ID and a timestamp—and the privacy surface is minimal. No personal messages, no financial data, no unsaved creative work. For Microsoft, it’s a way to stress-test the cross-device sync protocol, the Microsoft Store install path, and the user experience of account matching, all with near-zero chance of catastrophic data exposure.
Spotify also brings a massive existing user base. The overlap between daily Spotify listeners and Windows 11 Insiders is likely huge, meaning the feature will get heavy real-world usage quickly. If it holds up under that load, Microsoft can expand to other apps with confidence.
The Developer Play: A Resume API, Not a System Hack
Microsoft isn’t hardcoding Spotify’s resume behavior. The Insider blog explicitly invites developers to “integrate with Resume,” signaling a platform-level capability. That’s critical: it means any Android app with a Windows counterpart (or even a PWA) can eventually join the party if they implement the API.
For developers, the incentives are clear:
- A new engagement channel: users who switch devices mid-task are more likely to continue if the transition is seamless.
- A powerful conversion funnel: the one-click Microsoft Store install turns a taskbar alert into a desktop install event, potentially driving significant new Windows users for mobile-first apps.
- Differentiation: early adopters of the API could stand out in a Windows ecosystem hungry for deeper mobile integration.
But the API brings responsibilities. Developers must define clear resume semantics, avoid transmitting sensitive metadata (the last thing anyone wants is a half-composed email text synced over Bluetooth), and handle edge cases like authentication mismatches gracefully. Microsoft’s documentation for the API will be the make-or-break factor for developer adoption.
Privacy, Security, and the Ghost of WSA
The feature’s reliance on background reporting from Android raises immediate questions. Link to Windows must run persistently and communicate active app states to the PC. Microsoft has not yet detailed exactly what metadata is transmitted, how long it’s retained, or what end-to-end encryption is applied. That opacity will worry privacy-conscious users and enterprise administrators alike.
Enterprises face additional hurdles. Many organizations block Phone Link or restrict device pairing for security reasons. For Cross-Device Resume to be viable in regulated environments, Microsoft will need to provide Group Policy or MDM controls to disable it wholesale, limit it to specific apps, or enforce audit logging. Without those controls, IT departments will simply block the feature.
The legacy of WSA also looms large. Microsoft’s on-again, off-again relationship with Android on Windows makes developers cautious. Until there’s a clear, long-term distribution strategy for Android apps on Windows—whether through native Win32 bridges, PWAs, or a revived runtime—many developers may hesitate to invest in deep Resume integration.
The Competitive Landscape: Catching Up to Apple, Differently
Apple’s Handoff is deeply integrated into the OS and Apple’s own apps, but it works only within the Apple ecosystem. Microsoft’s approach is more open-ended: it uses a cloud-relay through Microsoft accounts to bridge Android and Windows, two platforms that collectively dwarf macOS and iOS in installed base. That could be a genuine advantage if executed well. Instead of locking users into a single vendor’s hardware, Microsoft is offering continuity across the devices most people already own.
The quiet removal of the Build 2025 demo suggests internal skepticism or, more likely, a recognition that the feature wasn’t ready for primetime. But the fact that it’s already shipping—even to a tiny Insider cohort—shows Microsoft is serious. The staged rollout allows the company to gather data, fix issues, and refine the messaging before a public launch.
What Comes Next: Speculation and Hard Limits
Microsoft hasn’t committed to a timeline for broader availability, nor has it revealed which apps will follow Spotify. The Insider build notes mention only Spotify. Industry observers expect media and productivity apps (YouTube Music, Audible, maybe Microsoft’s own Office suite) to be the next logical candidates. Navigation apps like Google Maps, messaging apps like WhatsApp, and e-readers like Kindle could also benefit, but each introduces unique privacy and state-restore challenges.
A wildcard: the feature’s name in some Insider references hints at OneDrive document resumption, consistent with earlier builds that resurrected Word or Excel docs across devices. That parallel effort may indicate Microsoft is developing two separate resumes: one for cloud documents (already partially live) and one for third-party app states, with the latter being the more experimental, Build-demoed version.
The Bottom Line: A Preview Worth Watching, Not Yet a Promise
Cross-Device Resume is the most tangible evidence yet that Microsoft understands the value of frictionless device hopping. The Spotify test case is smart, the developer API shows platform ambition, and the cautious rollout reflects hard-learned lessons from past failures. But it’s still early. The feature is experimental, incomplete, and gated behind a combination of Insider builds, telemetry-decided sampling, and manual device pairing. It’s not a shipping product—it’s a preview of what could be.
For Windows enthusiasts willing to jump through the hoops, it offers a genuine taste of a Handoff-style future. For everyone else, Cross-Device Resume is a signal: Microsoft is finally bridging the Android-Windows divide without resurrecting WSA. Whether it becomes a cornerstone of the Windows experience or another abandoned experiment depends on the next few months of Insider feedback, developer buy-in, and Microsoft’s willingness to commit fully to the vision.