What Android 17 Continue On Actually Delivers
Android 17 Continue On is Google’s most serious attempt yet at true cross-device task switching. Built on the new Handoff API introduced in Android 17, it lets you start an activity on your phone and pick up the same “user journey” on a tablet signed into the same Google account. In practice, that means editing a Google Docs file on your phone, then seeing a contextual suggestion appear in the tablet’s dock or taskbar. Tap it and the identical document opens, preserving scroll position and in-progress edits. Continue On also supports an app-to-web fallback: if the receiving tablet does not have the corresponding app installed, Android can resume the task in a browser tab instead. This keeps Android tablet continuity usable even on mismatched setups. At launch, however, Continue On focuses solely on phone-to-tablet transitions, with the reverse direction only confirmed as a future expansion.
How Apple Handoff Works After a Decade of Refinement
Apple Handoff has quietly defined cross-device task continuity since it arrived with iOS 8 and OS X Yosemite in 2014. The system connects iPhone, iPad, Mac, and Apple Watch, allowing tasks to flow in any direction as long as devices are nearby, signed into the same account, and have Bluetooth and Wi‑Fi enabled. When you start an email, webpage, or document on one device, a small Handoff icon appears in the Mac Dock, the iOS App Switcher, or at the edge of the iPad Dock, depending on where you move next. The handoff itself relies on local device detection over Bluetooth and transfers state via Wi‑Fi, avoiding a cloud relay step in standard use. Importantly, Handoff launched bidirectional from day one and ships deeply integrated into Apple’s own apps such as Safari, Mail, Maps, Notes, Pages, and more, with a mature API that many third-party developers have implemented over the last twelve years.
Android 17 Continue On vs Apple Handoff: Core Similarities and Key Gaps
On paper, Android 17 Continue On and Apple Handoff target the same goal: making cross-device task switching feel invisible. Both surface contextual suggestions on a second device and reopen the same content at the same state, whether that is an email thread, a document, or a browser tab. Yet the differences are still substantial. Apple Handoff connects four device types—iPhone, iPad, Mac, and Apple Watch—and supports fully bidirectional flows, like Mac-to-iPhone or iPad-to-Mac. Continue On, by contrast, debuts limited to phone-to-tablet, with tablet-to-phone still pending and no official support for laptops or wearables. Apple’s system also benefits from twelve years of developer adoption and a long list of first-party apps. Google’s implementation is new, depends entirely on developers embracing the Handoff API, and currently leans on web fallbacks to mask missing apps. Continue On is finally a genuine answer to Handoff, but not yet its equal.
Why Continue On Matters for the Android Ecosystem
Even in its early form, Android 17 Continue On is significant because it tackles a long-standing weakness: fragmented device-to-device experiences. While individual manufacturers like Samsung have offered their own continuity tools, there has been no universal Android mechanism equivalent to Handoff’s core behavior. Continue On changes that by defining a platform-level way for apps to transfer state between devices sharing a Google account. The app-to-web fallback is a pragmatic nod to Android’s diversity, ensuring cross-device flows can still work when app setups differ. For users who move regularly between phone and tablet, this promises far smoother Android tablet continuity—less hunting through recent apps or browser history, more tapping a single, context-aware suggestion. Looking ahead, the underlying framework is broad enough that tablets, phones, and potentially even ChromeOS or other form factors could join the experience, provided developers adopt the APIs and Google ships true bidirectional support.