The entire task transfers instantly: the document, your scroll position, everything.
For years, the Android ecosystem has carried a quiet gap — the inability to move fluidly between devices the way Apple users have long taken for granted. Google is now closing that gap with Task Continuity, a native cross-device feature that will allow users to transfer active tasks, with full state preserved, between Android phones, tablets, and PCs. Discovered in early Android 16 code and slated for Android 17, the feature reflects something deeper than a software update: it is Google finally asserting the kind of unified platform control that coherent ecosystems require.
- Android users have long envied Apple's Handoff, watching a seamless cross-device experience remain out of reach due to the fragmented nature of Android's multi-manufacturer, multi-platform world.
- Microsoft's Phone Link attempted to bridge phones and PCs but produced a clunky, one-directional workaround that few developers bothered to support — leaving the gap largely unfilled.
- Google is now consolidating its leverage by merging Chrome OS and Android into a single OS framework, giving it the platform authority needed to embed Task Continuity at the system level.
- The feature enables true two-way task transfer — scroll position, session state, and all — triggered by a simple tap on a taskbar icon when a nearby device is detected.
- Already visible in Android 16 development code, Task Continuity is targeting a full launch with Android 17, positioning Google to finally offer users a compelling reason to invest in the broader Android device ecosystem.
For years, Android users have watched Apple customers move effortlessly between devices — starting an email on an iPhone and resuming it mid-sentence on a MacBook. Apple's Handoff works because Apple controls both ends of the experience. Google never could quite replicate it, largely because Android phones live alongside Windows PCs made by entirely different companies with different priorities. That fragmentation is now being addressed.
Code embedded in early Android 16 builds, uncovered by Android Authority, reveals a feature called Task Continuity. Previous attempts to bridge the gap — like Microsoft's Phone Link — were clunky and one-directional, requiring developers to build support using proprietary code. Few did. The barrier was simply too high.
Google's approach cuts through the problem by consolidating control. By merging Chrome OS and Android into a single operating system for PCs, Google gains the same kind of platform leverage Apple has always held. Task Continuity will be embedded directly into Android's core framework, with standardized APIs available to every developer and device maker — making implementation consistent and the experience reliable.
In practice, the feature is straightforward: you're reading a document on your phone, the screen feels too small, and you set it down. A small icon appears on your nearby tablet suggesting the session is available. You tap it, and everything transfers instantly — the document, your scroll position, the full session state. It works in both directions, with no third-party apps or manufacturer customizations required.
The rollout will take time. Google is targeting Android 17, expected next year, for the full release. When it arrives, it will give Android users something they've long been missing: a genuinely seamless reason to stay within the ecosystem.
For years, Android users have watched from the sidelines as Apple customers enjoyed something that seemed almost magical: the ability to start reading an email on an iPhone, set it down, and pick up that exact message mid-sentence on a MacBook. Apple calls this Handoff. It works because Apple controls both the phone and the computer. Google, by contrast, has never managed to build anything quite like it—partly because Android phones talk to Windows PCs, and those are made by different companies with different priorities. That fragmentation ends soon. Google is building a feature called Task Continuity, and it will bring that seamless cross-device experience to Android for the first time.
The discovery comes from code already embedded in early versions of Android 16, uncovered by Android Authority. The feature represents a fundamental shift in how Google approaches the Android ecosystem. For years, the company tried to bridge the gap between phones and PCs through partnerships—Microsoft's Phone Link, for instance, allows you to see your Android phone on a Windows desktop, but the experience is clunky and one-directional. You can resume tasks from phone to PC, but only if developers build support for it using Microsoft's proprietary code. Few do. The barrier to entry is simply too high.
Google's solution sidesteps the whole problem by consolidating power. The company is merging Chrome OS and Android into a single operating system for PCs. This gives Google the leverage it needs to embed Task Continuity directly into Android's core framework—the same way Apple embeds Handoff into iOS and macOS. Every developer, every device maker, will have access to the same standardized API. Implementation becomes consistent. The experience becomes reliable.
Here's what it will feel like in practice. You're reading a dense document in Chrome on your phone, but the screen is too small. You set the phone down. On your nearby tablet, a small icon appears in the taskbar—a suggestion that your Chrome session is running on the other device. You tap it. The entire task transfers instantly: the document, your scroll position, the full session state, everything. It's two-way. You can push tasks from phone to tablet or tablet to phone. The system handles all the discovery and state management behind the scenes. No third-party apps. No manufacturer tweaks. Just seamless continuity built into the operating system itself.
The code is already there, but the rollout will take time. Google is still in the early stages of Android 16 development, and a system-wide feature this complex requires careful engineering. The company is targeting Android 17, expected next year, for the full release. When it arrives, it will finally give Android users something they've been missing: a reason to stay within the ecosystem, to buy a tablet or a Google PC, knowing that their workflow will flow as naturally across devices as it does for anyone with an Apple logo on their devices.
The Hearth Conversation Another angle on the story
Why has this taken so long? Android's been around for nearly two decades.
Because Android is open. Google doesn't control every device or every operating system it touches. Apple controls the whole stack—hardware, software, everything. That unity is what makes Handoff possible. Google had to wait until it had enough control of its own ecosystem to build something comparable.
So merging Chrome OS and Android is the key?
Exactly. It gives Google the same kind of vertical integration Apple has. One operating system, one framework, one set of rules for how devices talk to each other. Developers don't have to negotiate with Microsoft or anyone else.
Will this actually work, though? Or will it be another half-baked attempt?
The fact that it's baked into the core framework changes everything. Phone Link failed because it was bolted on top, optional, proprietary. Task Continuity will be fundamental. Every Android device will have it.
What about people who use Android phones with Windows PCs?
That's the trade-off. This works best if you stay within Google's ecosystem—Android phone, Android tablet, Google PC. If you're mixing and matching, you're back to the fragmentation problem.
So Google is essentially saying: stay with us?
Not explicitly. But yes, the incentive structure is clear. Seamless workflow is a powerful reason to choose devices from the same company.