What Continue On Does and Why It Matters
Continue On in Android 17 is Google’s answer to the long‑requested app handoff feature that Apple users have enjoyed for years. The concept is simple: start an activity on one Android device, then resume the same task on another without losing your place. Google describes it as enabling users to “start an Android app on one Android device and then transition to another device in their Android ecosystem, continuing the user journey they started.” In practice, that means drafting a document on a phone and instantly reopening it on a tablet, or picking up the same email thread on a larger screen. By baking cross-device task switching into the OS itself, Google is moving beyond basic account syncing to a more fluid, session‑level continuity that makes multiple Android devices feel like parts of a single, unified experience.

How Android 17’s App and Web Handoff Works
Under the hood, Continue On treats the device you start on as the sender and the destination device as the receiver, with the actual transition handled quietly in the background. There are two main modes. App‑to‑app handoff deep‑links you straight into the exact activity on the receiving device’s app—like opening the same Google Docs tab on your tablet that you were editing on your phone. Web handoff instead routes you to the equivalent experience in the tablet’s default browser. This is how a Gmail thread started in the phone app can reopen in the full Gmail web interface. Developers can choose which mode fits their experience best and can also define a web fallback. If the receiving device does not have the app installed, the task still resumes in the browser, preserving continuity instead of leaving users at a dead end.

From Mobile-to-Tablet Today to a Wider Ecosystem Tomorrow
At launch, Google is narrowing Continue On’s focus to mobile‑to‑tablet transitions, a logical starting point given how often users pair phones with Android tablets. When you unlock an eligible tablet, the taskbar surfaces a suggestion for the most recently used app on your phone; one tap opens the same content right where you left off. Although the underlying system is bidirectional—any supported Android device can act as sender or receiver—Google’s first implementation concentrates on this phone‑to‑tablet flow. Even with that constraint, the feature significantly improves Android tablet integration by positioning tablets as natural extensions of your phone rather than isolated screens. Developers already have access to the tools needed to support Continue On in the Android 17 release candidate, and reports suggest Google could eventually extend the same continuity model to other form factors, including future laptop-style devices.
Closing the Gap with Apple’s Handoff and User Expectations
For years, Android users have asked for better cross‑device continuity, while Apple’s Handoff set the benchmark for seamless transitions between phones, tablets, and computers. Continue On is Google’s clearest attempt yet to close that gap. By enabling session‑level handoff instead of just syncing files or notifications, Android finally offers a more cohesive multi‑device workflow. The fact that any Android 17 device can send and receive activities, rather than deferring to a single “primary” device, aligns with how people actually mix phones, tablets, and potentially future laptops. It is still early: feature support depends on developers, and initial scope is limited to mobile‑to‑tablet. Yet the underlying framework—app‑to‑app, app‑to‑web, and robust fallbacks—positions Android to grow a true continuity ecosystem that feels less like a loose collection of gadgets and more like one interconnected platform.
