What Android 17 Continue On Actually Does
Continue On is Android 17’s new app handoff feature designed to let you start a task on one device and continue it on another with almost no friction. It mirrors Apple’s Handoff concept: activities you initiate on your Android phone can surface as suggestions on a second device signed into the same Google account. In Google’s demos, opening a Google Doc or browsing in Chrome on a phone causes a “Handoff Suggestion” to appear on an Android tablet’s dock or taskbar. Tapping that suggestion opens the same document, tab, or activity in context, so you can pick up editing or browsing exactly where you left off. Under the hood, Android exposes a continuity framework that apps can hook into, allowing developers to describe what you were doing and how it should reopen on the second device, whether in the native app or on the web.
How Continue On Works Under the Hood
From a user perspective, Continue On looks simple: interact with an app on your phone, then tap the suggestion that appears on your tablet. Technically, it is powered by an activity deeplink and a flexible handoff model. Developers can register a deeplink that reconstructs the exact screen state in their tablet app, or they can rely on a web fallback. If the target app is not installed, Android can open the relevant content in the browser instead, such as loading a specific Gmail thread in the Gmail web interface via Chrome. There is also a direct-to-web option, where developers intentionally route handoffs to the browser even when a tablet app exists. Android 17’s APIs support both app-to-app and app-to-web scenarios, and Google leaves task management choices to each app, which should make it easier to add handoff support without rewriting existing experiences.
Current Limitations: Phone-to-Tablet Only and Beta State
In its first iteration, Android 17 Continue On is powerful but constrained. The most important limitation is direction: at launch it only supports mobile-to-tablet handoffs. That means you can start a task on your Android phone and continue it on an Android tablet, but not the other way around yet. Google says the framework is designed for bidirectional support, and tablet-to-phone continuity is on the roadmap, but there is no announced timing for when broader device pairings will ship. The feature is available in Android 17 beta builds and will roll out more widely once the stable release lands, with early testing in the RC1 build. Since Google has not published a definitive list of compatible apps, early usefulness will depend heavily on which developers move fast to implement the new continuity APIs and expose clear handoff suggestions.
What It Means for Cross-Device Productivity on Android
For years, cross-device productivity on Android has depended on manufacturer-specific features or manual workarounds like saving to the cloud and reopening on another screen. Continue On changes that by baking app continuity directly into the platform. Any developer targeting Android 17’s API level 37 can opt in, which should help standardize behavior across phones and tablets from different brands. In practice, this could make Android tablets far more viable as secondary work devices: you might triage email on your phone, then jump to your tablet for longer replies, or move a research session from your phone’s Chrome to a larger canvas with a single tap. Looking ahead, Google has hinted that the same framework could extend to other form factors, including ChromeOS devices, Windows integrations, and future Android-powered laptops, setting the stage for a more cohesive multi-screen Android ecosystem.
How It Compares to Apple’s Handoff and Where It Might Go Next
Apple’s Continuity and Handoff have long been a benchmark for seamless device switching, tightly integrated across iPhone, iPad, and Mac. Continue On is Google’s clearest response so far, offering conceptually similar behavior but with some key differences. First, it is Android-to-Android only for now, and limited to phone-to-tablet flows, whereas Apple’s system already spans multiple device categories. Second, Continue On leans heavily on developer choice: apps can direct users to native experiences or to the web, which adds flexibility but may create inconsistent behavior until best practices emerge. On the flip side, a platform-level solution promises broader access than proprietary manufacturer features and may evolve faster once adoption grows. As Android tablets mature and Google experiments with Android-based laptops, the success of Continue On will hinge on developer uptake and how quickly Google delivers full bidirectional and multi-platform support.