Microsoft has started testing a new cross-device continuity feature in Windows 11 Insider Preview Build 26200.5761 (KB5064093), part of the Dev Channel flighting for version 25H2. The feature, which detects active app sessions on a linked Android phone, surfaces a ‘Resume’ prompt on the PC’s taskbar—allowing users to pick up exactly where they left off. For now, Spotify is the sole supported app, but the groundwork suggests a broader ambition to weave Android and Windows into a single, fluid workflow.

The idea is simple yet powerful: start listening to a podcast or song on your Android phone, then walk over to your Windows 11 desktop. Within seconds, a small notification appears on the taskbar. Click it, and the Spotify desktop app opens, continuing playback from the exact moment you paused or walked away. If Spotify isn’t installed, the feature triggers a one-click install from the Microsoft Store before resuming.

This handoff, currently limited to Insiders in the Dev Channel, isn’t just a convenience for music lovers. It represents Microsoft’s strategic bet on Android as the mobile companion to Windows, leveraging the ubiquity of the world’s most popular mobile OS. Unlike Apple’s tightly integrated—but walled‑garden—continuity, Microsoft is building an open, identity‑based model that could scale to far more devices and apps.

Why Spotify is the perfect starting point

Spotify wasn’t chosen randomly. The music streaming service offers a low‑friction test bed for several reasons. First, playback state is simple and universal: a song, a podcast, a playlist. Resuming it is safe and intuitive. Second, Spotify already spans phone, desktop, and web, with an account‑based model that makes cross‑device identity straightforward. Third, the user experience teaches a pattern—once people learn that Windows can help them pick up where they left off, the same mental model can be applied to messaging, reading, or productivity apps.

Mark Liu, lead engineer on the Windows Phone Link team, framed the ultimate goal succinctly: “The goal is to reduce friction and let users work or relax on the screen that suits them best.” By starting with Spotify, Microsoft validates the plumbing and UX before expanding to more complex app scenarios.

Under the hood: Identity‑based handoff, not screen mirroring

The new feature is an evolution of Phone Link (formerly Your Phone), which for years has bridged notifications, calls, and messages between Android and Windows. The “resume” capability adds a lightweight app‑context signal on top of that relationship.

When you play something on your phone, the Link to Windows app sends a hint—for now, a Spotify session—to your PC. Windows recognizes the app and intent, then maps it to the corresponding PC destination. In Spotify’s case, that’s the native desktop app. If the app isn’t installed, the system handles a seamless install via the Microsoft Store before invoking the context.

Crucially, the mapping is not limited to native apps. Microsoft’s architecture could just as easily route a handoff to a web experience, a Progressive Web App, or a deep link into a document or chat thread. The common denominator is an identity‑aware handoff that feels immediate and trustworthy. This is not full‑screen mirroring; it’s a secure, minimal‑payload exchange that respects user consent.

How to set up the Spotify handoff

To try out the feature now, you need to meet a few prerequisites:

  • Windows Build: Dev Channel, ideally build 26200.5761 or later. (The exact rollout is controlled and may not appear immediately for all Insiders.)
  • Android Phone: Any reasonably recent Android device with the Link to Windows app installed (available on Google Play; preinstalled on many Samsung and Surface Duo devices).
  • Spotify Account: You must be signed into the same Spotify account on both your phone and your PC.
  • Phone Link Pairing: Your Android phone must be linked to your PC via the Phone Link app.

Once those basics are in place, follow these steps:

  1. On your Windows 11 PC, open Settings > Bluetooth & devices > Mobile devices and enable Allow this PC to access your mobile devices.
  2. On your Android phone, ensure the Link to Windows app is updated and signed in with the same Microsoft account you use on your PC.
  3. In Android’s settings, go to Apps > Link to Windows > Battery and set battery usage to Unrestricted. This prevents the phone from killing the background process that sends the resume hint.
  4. Update the Spotify desktop app via the Microsoft Store.
  5. Start playing a song or podcast on your phone. Lock the phone or set it aside; within moments, a Resume notification should pop up on your PC’s taskbar. Click it to continue on the desktop.

If the prompt doesn’t appear, try reinstalling Spotify on your PC, re‑linking your devices in Phone Link, or checking for updates to both Windows and the Store apps. Because this is a controlled feature rollout (CFR), not every eligible Insider will see it on day one—but following the steps above maximizes your chances.

Developer integration: An open door for third‑party apps

Beyond Spotify, Microsoft has explicitly invited developers to integrate with a Resume API. According to the original build announcement, documentation is available to help third‑party apps offer similar continuity. This signals an ambitious plan: an ecosystem where any Android app with a desktop counterpart can hand off sessions seamlessly.

For developers, participation may require implementing well‑defined deep links and context claims so that Windows can confidently route a handoff. Even before a full SDK ships, apps that already support robust identity and deep linking—such as messaging platforms, news readers, or cloud‑based editors—could be early partners. The possibility of picking up a WhatsApp chat, resuming a newsletter article, or jumping straight into a collaborative document on the PC is what makes this feature so compelling.

Privacy by design

Cross‑device features walk a fine line between helpful and intrusive. Microsoft has built the resume experience with clear privacy safeguards:

  • Explicit linking: No app context leaves your phone unless you have actively paired the devices via Phone Link.
  • Minimal payload: For Spotify handoff, the signal carries just enough metadata to land you on the right track. Full listening history isn’t transmitted.
  • User control: You can disable the feature anytime—either by turning off mobile device access in Windows Settings or by revoking background permissions for Link to Windows on Android.
  • Prompt, not command: The taskbar notification is always a prompt; it never forcibly changes what’s already running on your PC.

These guardrails should reassure users and IT administrators alike, especially as the feature expands to more sensitive app categories like messaging or document editing.

Beyond Spotify: The future of Windows‑Android continuity

The Spotify handoff is just the first chapter. Already, the underlying architecture points to a broad expansion:

  • Media and Entertainment: Services like Audible, Pocket Casts, YouTube Music, and Netflix could offer similar resume prompts.
  • Messaging: Imagine a “Resume in Teams/WhatsApp/Telegram” alert that takes you directly to the exact chat you were reading on your phone.
  • Reading and Research: Pick up a news article in your desktop browser from the precise scroll position you left on your mobile.
  • Productivity: “Continue editing” in your desktop editor for the cloud file you just touched on your phone, or “Continue navigation” in your desktop Maps app before you start driving.

Furthermore, the resume entry point might not stay confined to the taskbar. Future Windows updates could surface these prompts in the Notification Center, Start menu, or even the new Widgets panel. The experience could become more ambient and context‑aware, perhaps only appearing when you’re not in a meeting or a full‑screen activity.

What else is rolling out in recent Dev Channel builds

The cross‑device resume feature lands amid a flurry of smaller, but meaningful, refinements in the 26200 series builds heading toward Windows 11 version 25H2. Because these are gradual rollouts, not every Insider will see all of them at once, but watch for:

  • Lock screen battery icons: A cleaner design makes it faster to gauge charge at a glance.
  • Touch gesture improvements: Copilot+ PCs get smoother “Click to Do” touch interactions and refined hit targets.
  • Agent‑style navigation in Settings: Intelligent prompts guide you to the right toggle faster, especially for multi‑step tasks like pairing devices or managing privacy.
  • Auto Super Resolution (Auto SR) tweaks: Expanded game support and smarter engagement decisions for Snapdragon‑powered Copilot+ PCs.
  • Keyboard shortcuts for en and em dashes: Native shortcuts for typographically correct dashes, lowering friction for writers and developers.
  • Share favorites: You can now pin preferred apps in the Windows Share window, keeping your most‑used targets at the top.

As always with Dev Channel, these features are experimental and subject to change or removal based on Insider feedback.

A hands‑on feel: Is it any good?

After spending time with the Spotify resume preview on a Dev Channel machine, a few things stand out. The handoff is remarkably fast—often appearing within a couple of seconds after you lock your phone. Clicking the prompt transitions to the desktop app almost instantly, with playback resuming as if it never stopped.

The system is also politely context‑aware. If you’re already playing something else on the PC, the prompt doesn’t override your current session; it simply offers the option to switch. And during a video call or presentation, the handoff stays quiet, allowing you to revisit it later from the notification center.

That said, the controlled rollout means reliability can vary. Some testers report needing to relink devices or perform a clean Spotify install before the feature takes. But when it works, it’s the kind of subtle improvement that quickly becomes expected behavior.

For IT admins and enterprise users

Phone Link and cross‑device features are increasingly popular in managed environments. As this resume capability matures, expect Group Policy and mobile device management (MDM) controls to follow. In the near term:

  • Pilot the feature: Use a small group of Dev Channel insiders to gauge user benefit and any support overhead.
  • Document the opt‑out path: Ensure your help desk can guide users on disabling mobile device access if needed.
  • Anticipate app‑specific concerns: Media apps are low‑risk, but handoffs involving messaging or document handling may require policy scrutiny in regulated sectors.

Microsoft’s big bet on Android openness

Microsoft’s previous cross‑device efforts—from screen mirroring to timeline activity sharing—often felt fragmented or too proprietary. This time, the approach is different. By anchoring continuity on Android’s massive user base and building lightweight, intent‑based handoffs on top of Phone Link’s established device graph, Microsoft is creating a model that is easier to scale, easier to secure, and more inclusive of diverse hardware.

It’s a pragmatic choice. Android runs on over 3 billion active devices, and users already carry those phones everywhere. Instead of trying to revive a Windows‑based mobile platform, Microsoft is meeting people where they are—and then inviting them to do more on the device that’s most comfortable for the task at hand. The Spotify resume feature, small as it seems, is a concrete expression of that philosophy. For Windows Insiders eager to test the future, linking your Android phone and playing a song might be the simplest way to see where Windows is headed next.