What Android 17 Continue On Actually Does
Android 17’s Continue On feature is Google’s first real attempt at seamless cross-device task switching between phones and tablets. Built on the new Handoff API in Android 17, it lets you move active app states instead of simply reopening files from history. If you are reading a page in Chrome or editing a document in Google Docs on your phone, a suggestion appears on your tablet’s taskbar or dock with a small phone icon. Tap it, and the same webpage or document opens at the exact point you left off. Continue On supports two flows: app-to-app when the same app exists on both devices, and app-to-web when the receiving device lacks the app, falling back to a browser version such as Gmail in Chrome. For now, it works only from phone to tablet, with reverse direction promised but not yet available.
How Apple Handoff Sets the Benchmark
Apple Handoff has been shaping cross-device workflows since its debut alongside iOS 8 and OS X Yosemite. It spans four device categories: iPhone, iPad, Mac, and Apple Watch. Handoff detects nearby devices using Bluetooth and transfers activity state over Wi‑Fi, without requiring a cloud relay step in the standard flow. You can move tasks in any direction—phone to laptop, laptop to tablet, tablet to phone, or from Apple Watch to a larger device. A contextual icon appears in the Mac Dock, iOS App Switcher, or at the end of the iPad Dock depending on where you are resuming. Apple’s own apps, including Safari, Mail, Notes, Maps, Calendar, Pages, Numbers, and more, support Handoff, and a public API has encouraged third‑party adoption over twelve years. While support is not universal, many mainstream productivity and communication apps integrate Handoff, making it a mature pillar of the Apple ecosystem.
Structural Differences: Scope, Connectivity, and Direction
Despite similar goals, Android Continue On and Apple Handoff differ in important ways. The biggest gap is scope. Handoff reaches across phone, tablet, laptop, desktop, and watch, while Continue On launches strictly as a phone‑to‑tablet feature. Google has designed its system to be bidirectional and has hinted at laptop support, but neither is available at launch. Connectivity also diverges. Handoff focuses on local proximity, pairing Bluetooth discovery with Wi‑Fi for state transfer, so activities usually hand off only when devices are physically nearby. Continue On instead leans on Android’s CompanionDeviceManager and an internet connection, synchronizing continuity state via your Google account. This may allow more distance between devices but introduces a cloud step Apple’s approach avoids. Finally, directionality matters in daily use: Handoff has always been fully bidirectional, while Continue On currently moves tasks in just one direction, limiting flexibility for now.
Where Android 17 Is Catching Up—and Even Pulling Ahead
Android 17 Continue On finally gives Android users a native answer to cross-device task continuity. The feature deeply integrates with core Google apps like Chrome, Docs, and Gmail and cleverly uses an app‑to‑web fallback so that a handoff suggestion still appears when the tablet lacks the relevant app. That design choice is particularly important in the fragmented Android ecosystem, where app parity between phone and tablet is far from guaranteed. If developers provide appropriate URLs, users can reliably resume activities in a browser instead of seeing the feature silently fail. Continue On will also power Samsung’s One UI 9.0 improvements, evolving the older Continue On Other Devices feature that previously worked mainly with Samsung’s own apps. As One UI 9.0 lands on Galaxy phones and tablets, Android’s cross-device productivity story will feel more coherent, especially for users already embedded in Google’s app suite.
Where Apple Still Leads in Cross-Device Task Switching
Even with Android 17’s advances, Apple Handoff keeps a clear lead in several areas. First is ecosystem breadth: Handoff spans phones, tablets, laptops, desktops, and watches, enabling workflows like starting an email on a Mac, checking details on an iPad, and glancing at updates on Apple Watch. Second is maturity. Twelve years of availability mean Handoff has been refined through multiple platform releases, and a wide range of first‑party apps ship with support out of the box. Third‑party developers have had over a decade to adopt the Handoff API, so real-world coverage is significantly broader than what Continue On will have at launch. Finally, Handoff’s always‑on bidirectional design makes cross-device transitions feel predictable—regardless of which device you pick up next, your current task is likely waiting. Android 17 closes much of the conceptual gap, but bridging this practical, ecosystem‑driven distance will take time.