What Is Android’s Continue On Feature?
Continue On is Google’s new system-level tool for cross-device task switching, debuting with Android 17. It lets you start an activity on one Android device—such as drafting a document or reading an email on your phone—and continue that exact task on another compatible device without manual searching or re-opening files. When the feature is active, your second device shows a “handoff suggestion” in the taskbar or dock, highlighting the specific app instance you were using. Tapping this suggestion resumes the task in context, rather than just launching the app’s home screen. Similar to Apple’s Handoff, Continue On aims to reduce friction for multi-device productivity, especially for users who frequently move between phones and larger-screen tablets. Instead of juggling recent files, browser tabs, or email threads, Android will surface the right activity at the right moment, making the platform feel more like a unified ecosystem of screens.
How Continue On Works Across Phones and Tablets
In its first iteration, the Android Continue On feature is focused on phone-to-tablet workflows. Imagine you are editing a Google Doc on your Android phone. When you pick up your Android tablet running Android 17, you will see a Docs icon appear in the dock with a special handoff label. Tapping the regular app icon opens Docs as usual, but tapping the labeled suggestion jumps straight into the same document from your phone. The same logic applies to other supported apps, such as opening a Gmail thread you were reading on mobile directly on your tablet. Under the hood, developers can use activity deeplinks to restore the exact in-app state, or fall back to a web URL in Chrome when the native app is not installed. Google says bidirectional support is planned, but at launch you can only hand off tasks from phone to tablet, not the other way around.
Continue On vs. Apple’s Handoff: Similar Idea, Different Ecosystem
Apple’s Handoff is part of its broader Continuity framework, allowing activities to move fluidly between iPhone, iPad, and Mac. Android’s Continue On is clearly an Android Handoff alternative, adopting the same core concept of resuming a task in context, but within a more open and diverse hardware ecosystem. Where Apple tightly controls devices and operating systems, Android must support many manufacturers and form factors. Historically, that gap has been partially filled by proprietary features—Samsung, for example, offers its own continuity-style tools—but these are locked to specific brands. Continue On shifts cross-device continuity into the Android platform itself, promising a more standardized experience for any device running Android 17 or higher. While Apple already spans phones, tablets, and computers, Google’s early implementation focuses on Android-to-Android handoffs, with the longer-term ambition of extending continuity to platforms like ChromeOS and possibly even Windows-based experiences.
Why Continue On Matters for Multi‑Device Productivity
For multi-device productivity, the biggest friction on Android today is context switching. You might know a spreadsheet is in Google Sheets or an email is in Gmail, but jumping to it on another device typically means opening the app, navigating recent files, or searching. The Android Continue On feature removes this overhead by turning your second device into a natural extension of the first. Whether you are moving from a phone to a tablet while working on a document, reading a long article, or catching up on email, the system proactively surfaces the exact task you were doing. That makes Android feel less like a collection of separate devices and more like one continuous workspace spread across screens. As more apps adopt the APIs, cross-device task switching could become a standard expectation on Android, narrowing one of the ecosystem’s biggest usability gaps.
The Road Ahead: Developer Support and Future Platforms
Continue On is only as powerful as the apps that support it, which is why Google is exposing it at the platform level starting with API level 37 on Android 17. Developers have flexibility in how they implement the experience: they can open the same native app on the receiving device, fall back to a web version in the browser if the app is missing, or even design flows that go directly to the web by default. This modular approach should help more services participate without major rewrites. Although the current focus is Android-to-Android, Google’s continuity framework lays groundwork for broader ecosystem integration in the future. It is widely expected that Google will extend these capabilities to other platforms it touches, such as ChromeOS laptops, and potentially even deeper integrations with desktop environments, making Android’s cross-device story more compelling over time.