What Android 17’s Continue On Actually Does
Android 17 Continue On is Google’s new app continuity feature designed to let you start a task on one Android device and pick it up on another. Functionally, it is the closest Android Handoff equivalent we have seen, echoing Apple’s Handoff system that arrived with iOS 8. Continue On works when devices are signed into the same account and running Android 17, and it is currently available in beta and RC builds ahead of the stable release expected this summer. Once enabled, activities such as editing a document or browsing a website can surface as a “Handoff Suggestion” on your other device, ready to resume. While Google has not published a full list of supported apps, it has provided demos for Chrome and Google Docs and is inviting developers to integrate the feature into their own apps.
How Continue On Mirrors Apple’s Handoff
In day-to-day use, Continue On closely mirrors Apple Handoff’s approach to cross-device task switching. Start writing in Google Docs on your phone, unlock your tablet, and the same document appears in the dock with a “Handoff Suggestion” label so you can resume editing instantly. The app continuity feature supports both app-to-app and app-to-web transitions, giving developers flexibility in how they implement it. For example, a Gmail thread opened on your phone does not have to hand off to the Gmail app on your tablet; it can instead launch the Gmail web experience in Chrome if that is what the developer chooses. This mirrors Apple’s philosophy of continuity across platforms, but with Google’s spin: Android relies heavily on the web and gives developers freedom to decide whether the target is a native app, a browser tab, or another surface entirely.
Current Limitations: Phone-to-Tablet Only at Launch
Despite its bidirectional design, Continue On’s initial rollout is limited. At launch, Android 17 Continue On only supports handoffs from phone to tablet. In practice, that means you can start an activity on your Android phone and see it appear as a suggestion in your Android tablet’s dock, but not the other way around. Google has explicitly stated that bidirectional support is planned, though it has not provided a timeline for enabling tablet-to-phone or other device combinations. This staged introduction gives developers time to experiment with implementation details, such as deciding whether an activity should reopen in the same app or in a web view on the destination device. The limitation may feel restrictive for early adopters, but it also signals that Google is treating reliability and polish seriously before expanding to more complex device pairs and scenarios.
What Developers and Users Can Expect Next
Continue On’s long-term value depends heavily on developer adoption. Google is giving developers considerable control: they can choose how tasks are represented, whether to hand off to the same Android app, or to a browser-based version when the companion app is not installed. This flexibility should help popular services adopt the feature quickly, especially productivity and communication tools where cross-device use is common. For users, that means more seamless cross-device task switching as more apps integrate Continue On. The feature also launches alongside broader Android interoperability efforts, including new Android-powered laptops, hinting at a future where your phone, tablet, and other devices behave more like a single, cohesive workspace. As bidirectional support arrives and more device categories join in, Continue On could narrow the gap between Android and iOS continuity experiences in a meaningful way.