What Android 17’s Continue On Actually Does
Continue On in Android 17 is Google’s long-awaited answer to seamless app handoff between your devices. The feature lets you start a task on one Android device and resume it on another without digging through recent apps or manually syncing files. When you switch from your phone to a compatible tablet, Android surfaces a “Handoff Suggestion” in the tablet’s taskbar, prompting you to continue the same app session from the exact point you left off. Google has shown examples with Chrome and Google Docs, where a tab or document on your phone simply reappears on your tablet, already open and scrolled to the same position. Under the hood, Continue On treats your current app activity as a portable session that can be picked up elsewhere, making cross-device continuity feel like part of the operating system rather than a separate cloud feature.
How Continue On Compares to Apple’s Handoff
Functionally, Android 17 Continue On is very close to Apple’s Handoff: both systems let you move an in-progress activity from one device to another and pick up without losing context. The key similarity is that they treat tasks, not just files, as something that can travel between screens. Where Continue On starts to differentiate itself is in its flexibility. Google is explicitly supporting both app-to-app and app-to-web transitions. That means an activity from the Gmail app on your phone can resume in the Gmail web interface on your tablet, not just in another native app. Developers can also decide which experience is best per device, and there is a built-in fallback to the web if the receiving device does not have the app installed. In practice, this makes Continue On an ecosystem feature that leans heavily on the web as a safety net.
Current Limitations: Phone-to-Tablet Only, For Now
Despite being designed as a bidirectional system where any compatible device can send and receive activities, Continue On’s initial rollout is surprisingly narrow. At launch with Android 17, the app handoff feature is restricted to Android to tablet handoff scenarios, specifically phone-to-tablet transitions. That means you can start in an app on your phone and see a suggestion on your tablet’s taskbar to resume there, but the inverse is not yet available in practice. Google has not detailed a list of supported apps either, beyond its own demos with Google Chrome, Google Docs, and Gmail. Developers must integrate the new APIs before their apps show up in Continue On workflows. Until that adoption happens and support expands beyond tablets, the experience will feel more like a promising preview than a fully mature cross-device continuity system.
Why Continue On Matters for Android’s Cross-Device Future
Continue On is part of a larger strategic push toward robust cross-device continuity on Android. For years, Apple’s ecosystem has set expectations around picking up tasks seamlessly from phone to tablet to laptop. Android users, by contrast, have mostly relied on ad-hoc solutions such as cloud sync, shared clipboard tools, or browser-based workarounds. By baking an app handoff feature into Android 17, Google is signaling that consistent, stateful experiences across screens are now a core platform priority. The bidirectional design suggests that future updates could extend beyond phones and tablets to other form factors, letting users bounce between devices without constantly reopening apps or retracing their steps. This shift doesn’t just benefit end users; it also gives developers a clearer model for building multi-device experiences that feel coherent, predictable, and deeply integrated with the operating system.