Microsoft has begun rolling out a Windows 11 feature that lets you pick up exactly where you left off on an Android phone—starting with Spotify. In a limited Insider preview released on August 22, 2025, the company is testing a “Resume from your phone” experience that surfaces on the taskbar and, with a single click, opens the Spotify desktop app to the same track or podcast you were playing on your mobile device.

The capability arrived in Dev Channel build 26200.5761 and Beta Channel build 26120.5761 (KB5064093), and it leans on the existing Phone Link infrastructure that already connects Windows PCs and Android handsets for notifications, calls, and file access. For now, the handoff is exclusive to Spotify, but Microsoft has signaled that the same mechanism—code-named Cross Device Resume—will eventually support productivity, messaging, and reading apps, finally delivering on the continuity promise that Windows users have watched Apple owners enjoy for years.

A Long Road to Cross‑Device Continuity

Microsoft’s pursuit of seamless device switching is over a decade old. During the Windows 10 era, projects like “Rome” and “Shared Experiences” let developers sync apps across devices, but adoption never matched the ambition. The company’s most visible attempt to bridge Windows and Android came in 2021, when Windows Subsystem for Android (WSA) allowed Amazon Appstore titles to run natively. That experiment is now winding down: WSA and the Amazon Appstore integration are set to reach end of support on March 5, 2025. The sunsetting marks a strategic pivot away from local Android virtualization and toward cloud‑assisted continuity flows.

Meanwhile, Phone Link has evolved from a basic notification and SMS relay into a richer conduit. Features like recent websites, on‑PC phone storage browsing, and now cross‑device resume reflect a deliberate shift: rather than forcing Android apps to run inside Windows, the PC becomes a hub that resumes your tasks using the best available Windows surface—a native app, a web endpoint, or even a progressive web app.

What the Insider Preview Delivers

The preview is deliberately narrow. If your PC and Android phone meet the requirements, starting a song or podcast in Spotify on the phone triggers a “Resume from your phone” pill‑shaped alert on the Windows taskbar. Clicking it launches Spotify on the PC—installing the app from the Microsoft Store in one click if you don’t already have it—and immediately continues playback at the same position, provided you’re signed into the same Spotify account on both devices.

The key specs:
- Builds: Dev Channel 26200.5761 and Beta Channel 26120.5761 (KB5064093), rolling out gradually.
- Setup: Settings > Bluetooth & devices > Mobile devices, where you enable “Allow this PC to access your mobile devices,” then link your Android phone via Link to Windows.
- Phone requirement: Android device with Link to Windows allowed to run in the background.
- App support: Spotify is the sole partner at launch; no official timetable for others yet.

Microsoft first teased the feature during its Build 2025 conference in a now‑deleted demo video. That demo showed an email draft resuming on a PC, suggesting the handoff is not meant to be limited to media. The eventual goal, according to developer documentation, is to cover “reading, messaging, documents, and more.”

How Cross Device Resume Works Under the Hood

The technical spine of the feature is the Continuity SDK and a Windows‑centric framework called Cross Device Resume (XDR). When an Android app wants to hand off an activity, it publishes a compact, time‑bound “AppContext” payload. That payload includes a unique contextId, a timestamp, a type flag indicating a resume activity, and a deep link (intentUri) or a web link that points to the corresponding content on Windows. Metadata such as a title or preview image can also be included for UI surfaces.

On the Windows side, the Cross‑Device Experience Host (CDEH) service—installed automatically when you enable mobile device access—listens for these signals. If the context is still valid (the default lifetime is five minutes, designed to reflect ongoing activities), Windows displays the Resume alert. When the user clicks it, the shell tries to launch the registered desktop app. If no app is installed, the Microsoft Store takes over with a one‑click install flow. Desktop apps can be Win32, UWP, or Windows App SDK; they register a protocol handler or activation mechanism to ingest the context and load the correct state.

The whole system is currently a Limited Access Feature, meaning third‑party developers must request Microsoft’s approval to integrate with the Link to Windows package on Android. That gatekeeping ensures the first wave of integrations will be curated, but it also means that expanding beyond Spotify will require the company to open up the program.

Handoff, Windows‑Style: How It Stacks Up

Apple’s Handoff has set the bar for continuity since 2014. Using a combination of Bluetooth, Wi‑Fi, and iCloud signaling, Handoff lets you resume email drafts, Safari tabs, Keynote presentations, and a host of third‑party apps across iPhone, iPad, Mac, and Apple Watch with minimal friction. Microsoft’s Resume feature is clearly its answer—but for the heterogeneous pairing of Android and Windows rather than a vertically integrated ecosystem.

Google’s Quick Share (formerly Nearby Share) is efficient for file transfers and link sharing, and it works on Windows PCs. However, it doesn’t aim to resume app state across platforms in the same way. Microsoft’s ambition is different: it wants to preserve the exact context—the same track, the same article scroll position, the same draft—rather than just push a file.

What’s unique about Microsoft’s approach:
- It operates across two different operating systems, which introduces complexity but also massive reach.
- It weaves the experience into core Windows shell surfaces (taskbar alerts, Store install flows) rather than requiring a separate overlay.
- It provides a structured SDK and a time‑boxed AppContext contract, so developers don’t need to invent their own syncing logic.

Why Now? The Strategic Context

The cross‑device resume preview arrives at a moment when Microsoft is redefining its Android integration. The impending end of WSA closes the chapter on running Android apps locally on Windows; that approach suffered from the absence of Google Play Services and limited app availability. Instead, Microsoft is doubling down on making Windows the best companion for the Android phone billions of people already carry.

There’s also competitive pressure. Apple’s Handoff raises user expectations, and Google is strengthening cross‑device experiences through Phone Hub on ChromeOS and Quick Share on Windows. A compelling handoff story for the Android‑Windows pairing helps keep users inside the Microsoft ecosystem without forcing them to abandon the open nature of the PC platform.

The User Experience: What You See and Do

For Insiders who receive the feature, the flow is straightforward. After linking an Android phone and opening Spotify on the mobile side, a “Resume from your phone” alert appears on the Windows taskbar next to the Spotify icon. Clicking it:
1. If Spotify for Windows is installed, the app launches and starts playing the same track at the same position.
2. If not installed, a Microsoft Store prompt offers a one‑click install; once installed, playback continues automatically.

The handoff relies on account identity: you must be signed into the same Spotify account on both devices, which is how the service matches the user. Microsoft has indicated that future productivity scenarios (e.g., an email draft) will similarly require matching Microsoft accounts or app‑specific logins.

Developer Implications

For app makers, adopting Cross Device Resume means integrating the Continuity SDK on the Android side and implementing a handler on the Windows side. The AppContext schema is intentionally simple: a call to AppContext.publish() with the relevant intent URI or web link. Because Windows already supports deep linking and protocol activation, most modern Windows apps can participate with minimal additional code. If a desktop client doesn’t exist, a web fallback can at least open the corresponding URL, providing a continuity flow even for web‑only services.

The Limited Access nature of the feature means developers will need to engage with Microsoft to get early access, but the documentation suggests a deliberate path toward a broader public API. Given that Spotify is the first real‑world integration, other high‑profile partners in music, messaging, and productivity are likely to be courted next.

Security, Privacy, and Enterprise Controls

Phone Link’s infrastructure typically uses Microsoft’s cloud relay for many data types, and the same likely applies to Cross Device Resume’s signaling. The AppContext payloads are transient (time‑boxed to five minutes) and contain only the minimum metadata needed to launch the correct experience. While Microsoft has stated that relayed content is processed only in transit and not stored, enterprises in regulated industries will want to understand exactly which servers are involved and whether data traverses regional boundaries.

Organizations can manage cross‑device experiences through existing Group Policy and MDM settings. The “Continue experiences on this device” policy (EnableCDP) can disable all cross‑device features, and many hardening baselines recommend turning it off on sensitive workstations. Windows 11’s Settings > Bluetooth & devices > Mobile devices also provides per‑device toggles for phone access in File Explorer and, by extension, for Resume signaling. For IT, the best approach is to pilot the feature with approved apps, pair phones tied to managed identities, and audit endpoint logs for any resume events.

Strengths and Limitations

What Microsoft got right:
- A visible, one‑click taskbar prompt that does the right thing without hunting through menus.
- A developer‑friendly SDK with web fallback and automatic app install via the Store.
- A pragmatic ecosystem play: embrace Android where it is rather than try to replace it.

What could hold it back:
- The scope today is a single app. Success hinges on signing up WhatsApp, Teams, Outlook, Edge, and other high‑frequency services quickly.
- Cloud dependency and Android OEM power management can introduce latency or missed contexts. “Seamless” remains an aspiration until background restrictions are minimal.
- History: Project Rome and Shared Experiences generated excitement but never became ubiquitous. Microsoft must prove this will be different by shipping broadly and fast.

How to Try the Preview Right Now

  1. Update to an Insider build: Ensure you’re on Dev Channel build 26200.5761 or Beta Channel build 26120.5761 (install KB5064093 if not present automatically).
  2. Enable mobile device access: Go to Settings > Bluetooth & devices > Mobile devices, toggle on “Allow this PC to access your mobile devices,” and link your Android phone.
  3. Prepare your phone: Open the Link to Windows app on Android and allow it to run in the background. Make sure your PC and phone are connected on the same Microsoft account and that the phone’s Link to Windows service is up to date.
  4. Test with Spotify: Play a song or podcast on your phone. Look for the Resume alert on your PC’s taskbar. Click it. If Spotify isn’t installed, Windows will ask to install it from the Store; after installation, playback resumes.

Because the feature is rolling out gradually, even Insiders on the right builds may not see it immediately. Enabling the “Get the latest updates as soon as they’re available” toggle in Windows Update can help.

The Road Ahead: From Music to Everything

Microsoft’s documentation and Build 2025 tease paint a picture of a much broader handoff ecosystem. The same infrastructure that works for Spotify can be adapted for a WhatsApp chat thread, an Outlook draft, a Microsoft To Do task, or even a Kindle page number. The Windows IT blog already lists “Cross Device Resume” as a capability for OneDrive files, indicating that file‑level handoffs are also in the pipeline.

Once WSA is fully retired in March 2025, the rationale for running Android apps inside Windows evaporates entirely. In its place, resume‑style continuity positions Windows as the productivity surface that always knows what you were doing, regardless of the device you started on. This aligns with how people actually work: toggling between phone and PC dozens of times a day, often with the same accounts and services.

Competition will only intensify. Apple will continue to refine Handoff with tighter integration across its silicon. Google’s Quick Share already excels at file transfers and could expand toward app state syncing with Android’s “Continue Apps” initiative on ChromeOS. And third‑party bridges like Intel Unison, which offered similar clipboard and notification features, shut down in June 2025—a reminder that sustaining cross‑platform experiences without OS‑level support is brutally difficult.

The Verdict

For now, “Resume from your phone” is a tiny, Spotify‑only feature hidden inside Insider builds—easy to overlook. But seen strategically, it’s the most tangible sign yet that Windows 11 can deliver the continuity that Android users have long envied on iOS and macOS. If Microsoft can quickly add partners, keep the experience reliable, and give IT admins confidence in the data flow, the taskbar resume alert could become as iconic as the Start menu. The foundation is here; the next six months will show whether the company can build a real ecosystem on top of it.