What Android Continue On Actually Delivers
Android 17 introduces Continue On, a user-facing layer on top of Google’s new Handoff API designed for cross-device task switching. When you’re working in an app like Chrome or Google Docs on your phone and pick up an Android tablet, the tablet’s taskbar can surface a contextual suggestion with the app’s icon and a small phone badge. Tapping that suggestion resumes the exact activity—same webpage, same document position—without digging through history or recent files. Continue On supports two flows: app-to-app, when the same app is installed on both devices, and app-to-web, where it falls back to a web view if the receiving device lacks the app. Both devices must run Android 17, be signed into the same Google account, and be online. At launch, it is officially limited to phone-to-tablet, with the reverse direction planned but not yet available.
How Apple Handoff Set the Template for Cross-Device Continuity
Apple Handoff has been the reference point for seamless task continuity since its debut with iOS 8 and OS X Yosemite. It lets you start an activity on an iPhone and continue it on an iPad, Mac, or Apple Watch with a single tap, provided all devices are signed into the same Apple account and have Bluetooth and Wi‑Fi enabled. Handoff uses Bluetooth for device discovery and Wi‑Fi for direct state transfer, prioritizing local communication rather than routing through the cloud. The feature is fully bidirectional: you can move tasks between phone, tablet, laptop, desktop, and watch in nearly any combination. Apple’s own apps—Safari, Mail, Notes, Calendar, and more—have supported Handoff for years, and a well-established public API has enabled widespread third‑party adoption, even if coverage is still not universal. After more than a decade of refinement, Handoff’s behavior is predictable, tightly integrated, and deeply embedded across the Apple ecosystem.
Feature Parity, Device Support, and One UI 9.0’s Role
On paper, Android 17’s Continue On finally mirrors the core idea of Apple Handoff: cross-device task switching without manual saves or searches. In practice, the scope is narrower. Handoff spans four device types—phone, tablet, laptop/desktop, and watch—while Continue On launches strictly from phone to tablet. Google has indicated broader device coverage, including ChromeOS and forthcoming Googlebook laptops, is likely, but it is not part of the initial rollout. Samsung’s Galaxy devices with One UI 9.0 sit at the forefront of this push. Samsung already offered “Continue On Other Devices” for first‑party apps like Samsung Internet and Samsung Notes, supporting clipboard sharing and cross-device paste. Android 17’s Continue On elevates this from a vendor‑specific perk to a platform capability that Galaxy One UI 9.0 can expose more consistently across Google apps, bringing Android closer to the ecosystem coherence Apple users have enjoyed for years.
Reliability, UX Consistency, and the Fragmentation Problem
The biggest remaining gap between Android Continue On and Apple Handoff is not ambition but execution across diverse hardware and software. Handoff benefits from a tightly controlled ecosystem: similar hardware capabilities, synchronized OS releases, and unified design patterns. As a result, the handoff prompt tends to appear in predictable locations—the Mac Dock, iOS App Switcher, or iPad Dock—and behaves consistently. Android, by contrast, must span multiple manufacturers, skins, and update cadences. Continue On depends on Android 17, the CompanionDeviceManager framework, and per‑app adoption of the Handoff API. That means the experience can vary: suggestions might surface in different UI elements, or not at all, depending on OEM customizations and whether developers have implemented support. While the app‑to‑web fallback is a clever mitigation, fragmentation still makes reliability and UX consistency more fragile than in Apple’s unified Handoff environment.
Where Each Platform Still Falls Short
Despite its new muscle, Android Continue On is starting behind in three areas: device breadth, directionality, and app coverage. It currently excludes laptops, desktops, and wearables, launches only phone‑to‑tablet, and relies on developers embracing a brand‑new API. Yet it also introduces meaningful advantages, especially the app‑to‑web fallback that keeps suggestions useful even when native apps are missing—an important design choice for a fragmented ecosystem. Apple Handoff, on the other hand, suffers from its own constraints. Proximity and local‑network requirements can make continuity fail silently when Bluetooth or Wi‑Fi conditions are not ideal, and support still varies across less popular apps. Neither solution fully solves cross‑platform workflows, either: both are confined to their respective ecosystems. For users deeply invested in Android, Continue On in Android 17 and Galaxy One UI 9.0 is a genuine leap forward, but Apple’s decade‑mature Handoff remains the more complete benchmark.