Microsoft has started testing a new cross-device continuity feature in Windows 11 Insider builds that lets users seamlessly resume Android app sessions on their PC with a single click, starting with Spotify. The feature, which quietly appeared in the latest Dev and Beta Channel releases, aims to erase the friction of switching between phone and desktop by letting a taskbar alert launch the corresponding Windows app at the exact point you left off—and even install it first if needed.
Available now to Insiders with build 26200.5761 (KB5064093) on the Dev Channel and build 26120.5761 (KB5064093) on the Beta Channel, the “Resume” capability is the most tangible step yet toward an Apple Handoffice experience for the vast Android-and-Windows user base. It arrives as Microsoft moves away from running Android apps locally—the Windows Subsystem for Android ended support in March 2025—and instead leans into cloud-assisted continuity that keeps each OS doing what it does best.
The initial implementation is tightly scoped, server-gated, and available as a Controlled Feature Rollout (CFR), so not every eligible device will see it immediately. But the pattern is unmistakable: a taskbar toast surfaces shortly after you start playing something on your Android phone, and with one click, Spotify opens on the desktop—or triggers a single-click Microsoft Store install if it’s missing—and picks up exactly where you were.
Inside the new “Resume” flow
The feature works through the existing plumbing of Phone Link (formerly Your Phone), the Windows Cross-Device Experience Host, and a new Continuity SDK that Microsoft is gradually exposing to developers. On the Android side, the Link to Windows app publishes a short-lived “AppContext” that captures the precise content a user is engaged with—a media item, in this case. The Windows desktop app registers a protocol or deep link to open that same state, and the taskbar shows the “Resume” prompt when the context is fresh and valid. AppContext is deliberately short-lived, lasting only minutes, so users see only timely, relevant prompts.
Because the capability is a Limited Access Feature during testing, Microsoft is restricting participation to a small set of apps. Spotify serves as the launch partner, but the underlying architecture—built on Win32, UWP, and Windows App SDK compatibility—means that any traditional or modern desktop app can eventually wire up a deep link and participate when the feature opens more broadly.
A particularly clever detail: if Spotify isn’t installed on the Windows machine, the Resume alert initiates a one-click Microsoft Store installation. Once the install completes and the user signs in (with the same Spotify account used on Android), playback resumes from the same position. This zero-setup approach means fresh PCs, virtual machines, or secondary devices become handoff targets within seconds, without manual app hunting.
How it compares to Apple and Google
Apple’s Handoff has long been the gold standard for device continuity, with deep integration across iOS, iPadOS, and macOS, and entry points in the Dock, lock screen, and app switchers. Microsoft’s new “Resume” is a Windows-first surface—a taskbar alert that launches the corresponding desktop app with matched state. It lacks the same cross-device file and clipboard sharing, but for the specific workflow of continuing an active session, it hits the mark.
Google has recently leaned into Quick Share and multi-device experiences within its own Android-ChromeOS ecosystem, but Microsoft’s path targets the enormous population of users who pair an Android phone with a Windows PC. By marrying the Phone Link foundation with desktop apps users already prefer, Microsoft is betting on context sharing rather than duplicating mobile OS environments.
“The goal is to reduce friction and let users work or relax on the screen that suits them best,” said Mark Liu, lead engineer on the Windows Phone Link team, in comments reported by The Eastleigh Voice. That practicality—pick up exactly where you were, on whatever screen is in front of you—has been missing from the Android+Windows combination until now.
How to try Android-to-PC resume today
Set-up requires a PC on the correct Insider build, an Android phone, and the same Spotify account on both devices. Here is the step-by-step:
- Update Windows to Dev build 26200.5761 or Beta build 26120.5761 (KB5064093). In Settings > Windows Update, enable “Get the latest updates as soon as they’re available” to improve your chances of receiving the feature flag.
- Pair your Android phone. Go to Settings > Bluetooth & devices > Mobile devices, toggle “Allow this PC to access your mobile devices,” then choose “Manage devices” to link your phone.
- Prepare the phone side. Install Link to Windows from the Google Play Store, sign in with the same Microsoft account used on the PC, and allow background activity. Keep Bluetooth and Wi-Fi enabled.
- Start a session. Begin playback in the Spotify app on your Android phone. Within moments, a “Resume” alert should appear on the Windows 11 taskbar. Click it to continue on the desktop. If Spotify isn’t installed, accept the one-click install; after sign-in, playback resumes automatically.
Because this is a controlled rollout, many Insiders on the correct build may not see the prompt right away. Server-side flags determine availability, so patience and keeping the “latest updates” toggle active are the best strategy. Re-linking the phone and rebooting both devices can sometimes help, but absence simply means the flag hasn’t reached your device yet.
For IT pros: What to expect
In enterprise environments, Cross-Device Resume will need careful evaluation. The feature rides on Link to Windows, which is already permitted or restricted by many organizations. Admins should:
- Test on allowed hardware with the insider builds mentioned.
- Confirm whether policies permit linking personal phones to corporate PCs.
- Document line-of-business apps that might eventually participate; as the feature expands beyond media, consider whether resume flows could cross corporate and personal app accounts.
On the positive side, reducing context-switching can improve focus for knowledge workers who constantly move between phone and desktop. The one-click install behavior also simplifies onboarding for remote or temporary PCs. Enterprises will want admin controls to audit or block the feature, and given the history of Link to Windows in managed environments, such policies are likely to appear before broad deployment.
For developers: How to get ready
Microsoft has already invited developers to explore the Continuity SDK and prepare their apps for a broader rollout. To participate, developers need to do two things:
- On Android: Publish time-boxed AppContext signals that describe the exact content a user is engaged with—a document, media item, or conversation—using the SDK with appropriate metadata and time-to-live settings.
- On Windows: Ensure the desktop app registers protocol handlers or deep links that can open the same context. Classic Win32 apps may need to adopt modern Windows App SDK components or add robust command-line parsing.
Because the feature is a Limited Access Feature during preview, developers will need to coordinate with Microsoft for enablement. The payoff is a new channel for user engagement: Windows will surface their app in a just-in-time “continue” prompt when the user is likely to want it, without forcing them to search or remember where they left off.
Beyond Spotify: What’s next
The Spotify pilot is low-risk and high-impact, demonstrating the concept in a popular app with clear session state. But the same model can extend to reading apps (continue a news article at the same paragraph), maps (open a route from phone search), messaging (jump to a conversation with compose focused), and productivity tools (a recent note or email draft at the edit cursor). Microsoft has already laid the groundwork with recent Phone Link enhancements and direct Android file browsing in File Explorer for Insiders; context-aware resume completes the picture by moving from file parity to true activity continuity.
Insider builds continue to deliver additional quality-of-life improvements alongside this feature. The same build wave introduces new lock-screen battery icons, touch gesture refinements for Copilot+ PCs, smarter Settings navigation, automatic Super Resolution adjustments for Snapdragon-powered devices, and new keyboard shortcuts for en dash and em dash. But the cross-device resume alert stands out because it erases friction without asking users to change how they work—one click, and the PC picks up right where the phone left off.
The post-WSA Windows strategy
The end of Windows Subsystem for Android was not the end of Android on Windows but a pivot. Instead of running mobile apps locally—with all the associated virtualization, store curation, and update complexity—Microsoft is investing in continuity that leverages the desktop apps people already use. It’s lighter on system resources, simpler for users, and aligns with how most people actually split time between devices. This first, tightly scoped resume scenario signals exactly that direction: context sharing, intelligent shell prompts, and frictionless pathways into the Windows ecosystem.
In a world where every tiny speed bump between phone and PC adds up—re-searching for a song, finding the right podcast timestamp, rummaging through files—a “Resume” button that appears at the right moment with one-click setup changes the default expectation. It’s a small feature with big implications, and if developers adopt the framework, Windows 11 could soon feel meaningfully more modern and coherent across devices. For now, Insiders can watch for the Resume toast the next time they press play on their Android phone. It’s a glimpse of a Windows that no longer just tolerates your phone but actively understands what you were doing on it.