What Android Continue On Actually Does in Android 17
Android 17’s new Continue On feature is Google’s most serious attempt at cross-device continuity so far. Built on top of the Android 17 Handoff API, it lets you start a task on your Android phone and continue it seamlessly on your tablet signed into the same Google account. In practice, you might be editing a Google Docs file or drafting an email in Gmail on your phone. When you pick up your tablet, a suggestion appears in the dock or taskbar, marked with a small phone indicator. Tapping it opens the same app and restores the exact state—scroll position, text cursor, and ongoing edits—so you can keep working without hunting through recent files or browser history. If the receiving device does not have the app installed, Continue On can fall back to a web version in Chrome instead of failing silently, which makes it more resilient for less commonly installed apps and diverse device setups.
How Apple Handoff Sets the Benchmark for Cross-Device Continuity
Apple Handoff has quietly defined cross-device continuity since its launch with iOS 8 and OS X Yosemite in 2014. It lets you start a task on one Apple device and resume it on another, working bidirectionally across iPhone, iPad, Mac, and Apple Watch. If you begin writing an email on your iPhone, a small icon appears in the Mac Dock, iPad Dock, or iOS App Switcher, allowing you to pick up that exact draft instantly. The system relies on devices being signed in to the same Apple account and uses Bluetooth for proximity detection with Wi‑Fi to pass state directly, avoiding a cloud relay in the standard flow. Apple’s own apps—Safari, Mail, Maps, Notes, Pages, Numbers, and others—support Handoff, and a public API has been available to third-party developers since 2014. Twelve years of consistent support have turned Handoff from a marquee feature into an invisible, everyday workflow tool.
Device Support: Phone-to-Tablet vs a Full Ecosystem
The biggest structural difference in an Apple Handoff comparison is device coverage. Android 17 Continue On currently focuses on phone-to-tablet transitions. Google confirms the underlying design is bidirectional, but the initial release only supports handing off from phone to tablet, not the reverse, and it requires both devices to share the same Google account. That means no official support yet for moving sessions from tablet back to phone, and no clear timeline for when that will change. In contrast, Apple Handoff has been bidirectional from the beginning and spans four device types: iPhone, iPad, Mac, and Apple Watch. Tasks can move in almost any direction among them, with the watch primarily handing off to larger screens. While Android’s implementation hints at future expansion—potentially to ChromeOS or more Android form factors—the reality today is that Apple offers a mature, whole-ecosystem experience, while Google is just starting with a narrower, two-device scenario.
Feature Parity, Fallbacks, and Developer Adoption Gaps
On a feature level, Android Continue On is closer to Handoff than any previous Android 17 new features, but important gaps remain. Both systems try to preserve context rather than simply re-open the same app: they restore the active document, email thread, or browser tab. Android goes a step further with a built-in app-to-web fallback, handing content to Chrome when the receiving device lacks the native app. Apple Handoff expects the same app family to exist across devices and does not provide a generic web fallback. However, Apple’s advantage lies in maturity. Its Handoff APIs have been available for twelve years, so a large share of iOS, iPadOS, and macOS apps already implement them. Continue On, by contrast, is brand new and entirely dependent on Android developers choosing to integrate Google’s APIs. Until major third-party apps adopt it widely, Android’s cross-device continuity will feel more inconsistent than Apple’s.
What Still Needs Work for Android to Truly Match Handoff
Continue On finally gives Android users a native, system-level answer to Apple’s cross-device continuity, but it is only a first step. For Android to truly match Handoff, Google needs to deliver bidirectional support between phones and tablets, extend the feature to more device types, and ensure the experience feels as automatic and predictable as Apple’s. Deep developer adoption is crucial; without broad support from productivity, communication, and creative apps, the feature risks becoming a niche perk limited to Google’s own services. Google’s decision to design around “continuing the user journey” and to add web fallbacks shows clear intent to reduce friction when switching screens. Now the challenge is turning that promising foundation into an ecosystem-wide norm. Until then, Android Continue On narrows the gap in cross-device continuity, but Apple Handoff still represents the more complete, truly everywhere implementation.