What Android 17’s Continue On Actually Does
With Android 17, Google is introducing Continue On, a new system-level feature that finally brings real cross-device continuity to the Android ecosystem. In Google’s own description, Continue On lets users start an Android app on one device and transition to another, picking up the same task without manual setup or digging through menus. In practice, this looks like editing a document in Google Docs on your phone, then opening your tablet and seeing a prompt in the taskbar inviting you to resume that exact document with a single tap. Continue On is essentially an Android Handoff feature, focusing on app handoff on Android so tasks feel continuous rather than fragmented. It arrives as part of the Android 17 release candidate and is built as a platform capability that app developers can integrate, rather than a one-off trick for Google’s own apps.
How Continue On Works: App-to-App and Web Handoffs
Under the hood, Continue On treats the device you start on as the sender and the device you move to as the receiver, with the handoff happening in the background. There are two main modes. App-to-app handoff resumes your activity inside the same Android app on the second device, deep-linking directly to the screen you were on, such as the exact tab in a Google Docs document. Web handoff instead opens your ongoing task in the tablet’s default browser, useful when a richer web experience exists, as with Gmail shifting from the phone app to the full web interface while keeping the same email thread open. A fallback system ensures continuity even when the receiver does not have the app installed, automatically routing your task to a web view so you still continue from where you left off rather than starting over.
How It Compares to Apple’s Handoff and Continuity
Functionally, Android 17 Continue On is Google’s clearest answer yet to Apple’s Handoff and broader Continuity suite. Like Handoff, it surfaces a context-aware suggestion on your second device—in this case, in the Android tablet taskbar—so you can tap once and instantly resume an app session. Both systems aim to make app handoff across devices feel invisible, removing the friction of reopening apps, hunting for the right document, or reloading the correct email thread. Where Apple’s Continuity is already tightly integrated across phones, tablets, and laptops, Continue On is starting primarily with phones and tablets, but Google explicitly designed it to be bidirectional and extendable to more form factors. That makes this first implementation less comprehensive than Apple’s ecosystem today, yet strategically important: it turns Android app handoff from a scattered, app-by-app feature into a core part of the platform.
Limitations at Launch: Phone-to-Tablet Only (For Now)
At launch, Continue On is limited to phone-to-tablet transitions, even though the underlying system is built to work bidirectionally. In other words, any supported Android device will eventually be able to both send and receive activities, but the first public rollout focuses on the scenario where you start something on your phone and then move to a larger screen. That means you will not yet be bouncing sessions between multiple phones or from tablets back to phones in a polished way. Another constraint is developer support: while Google has demoed Continue On with Google Docs and Gmail, third-party developers still need to integrate the new APIs and decide whether to prioritize native app-to-app handoff, web handoff, or a mix of both. Until that adoption grows, the experience will vary widely between apps and workflows.
Why Continue On Matters for Android’s Ecosystem Future
Despite its early limitations, Continue On is a pivotal step for Android’s cross-device continuity and overall ecosystem competitiveness. For years, many users have cited Apple’s seamless device integration as a reason to stay put, while Android and traditional PCs lacked an equivalent. By introducing a system-level Android Handoff feature that any developer can tap into, Google is laying the groundwork for a more cohesive experience spanning phones, tablets, and likely future devices such as laptops. The combination of app-to-app and web-based handoffs gives developers flexibility to design the best experience for larger screens, while the fallback system ensures users are rarely blocked by missing apps. If Google follows through by extending Continue On beyond tablets and getting major productivity and communication apps on board, Android 17 could mark the beginning of truly fluid, cross-device productivity in the Android world.