What Android 17 Continue On Actually Delivers
Android 17’s Continue On feature is Google’s clearest attempt yet to close the cross-device productivity gap with Apple. Built on Android 17’s new Handoff API, it lets you start a task on your Android phone and pick it up on your tablet without hunting through recent files or browser history. In Google’s examples, you might be composing a Gmail message or editing a Google Docs file on your phone. When you pick up your tablet, a suggestion appears in the dock or taskbar with a small phone icon. Tapping it instantly opens the same email or document at the same point, effectively resuming your workflow. If the matching app is missing on the tablet, Continue On can fall back to a web version in Chrome, opening the same email thread or document there instead. Both devices must share the same Google account, and at launch the flow is limited to phone-to-tablet only.
How Apple Handoff Works Across Four Device Types
Apple Handoff has been quietly shaping cross-device task switching since its debut with iOS 8 and OS X Yosemite. The feature links iPhone, iPad, Mac, and Apple Watch, allowing you to start an activity on one device and continue it on another with minimal friction. When you are browsing in Safari, writing an email in Mail, or editing a note, nearby devices signed into the same Apple account show a contextual icon: in the Mac Dock, in the iOS App Switcher, or on the iPad Dock. Tapping that icon opens the corresponding app and restores the current state, such as a specific webpage, email draft, or Pages document. Handoff relies on Bluetooth for device discovery and Wi‑Fi for state transfer, so devices need to be physically close. The feature is fully bidirectional, supporting any combination of iPhone, iPad, Mac, and Apple Watch handoffs, with Apple’s core apps and many third‑party tools integrating the API over roughly twelve years.
Scope, Device Support, and Ecosystem Requirements
The most obvious difference in an Apple Handoff comparison is scope. Apple supports four device categories—phone, tablet, laptop/desktop, and watch—while Android’s Continue On currently focuses on cross-device task switching between phones and tablets only. Google has architected Continue On to be bidirectional and has signalled future expansion, but the initial Android 17 release is one‑directional (phone-to-tablet) and excludes laptops and wearables. Both systems insist on a unified account: Apple requires all devices to share the same Apple ID, and Android Continue On requires the same Google account on both devices. Connectivity also diverges. Apple leans on local Bluetooth and Wi‑Fi proximity with no explicit cloud relay step in normal use. Continue On is built on Android’s CompanionDeviceManager framework and Google’s own cloud‑backed services, prioritising account continuity and the ability to fall back to web apps when native apps are missing.
Feature Parity, Remaining Gaps, and Real-World Workflow Impact
On paper, Android 17 Continue On finally delivers the core promise Apple Handoff has offered for years: Android 17 productivity that lets you move an in‑progress task from phone to a larger screen without manual juggling. In daily use, that means fewer drafts lost in your email outbox and smoother transitions from quick phone edits to focused tablet sessions. However, practical gaps remain. Handoff is mature, bidirectional, and spans four device types, while Continue On is still limited to phone-to-tablet flows with no announced date for reverse direction or laptop support. Apple also benefits from roughly twelve years of developer adoption; many popular iOS and macOS apps already implement Handoff. By contrast, the Android Continue On feature depends entirely on developers choosing to integrate Google’s new API. For now, users can expect polished experiences in Google’s own apps first, with broader app coverage arriving more slowly.