What Android 17’s Continue On Feature Actually Does
Continue On is one of the headline Android 17 features, built to reduce the friction of switching between an Android phone and tablet. At a high level, it enables cross-device task switching: you start an activity on your phone and see a contextual suggestion on your tablet’s dock or taskbar. Tap that suggestion, and the app resumes on the larger screen, preserving state such as scroll position, document cursor, or an email draft. Technically, Continue On sits on top of Android 17’s new Handoff API. When an app implements this API, it can publish a representation of the current task that another Android device can consume. If the same app exists on both devices, Continue On performs an app-to-app transition. If the receiving device lacks the app, the system falls back to a web implementation (for example, a Gmail thread opening in Chrome), so phone to tablet handoff does not silently fail when installations differ.
How Apple Handoff Works Across Four Device Types
Apple Handoff has been part of iOS and macOS since 2014, long enough that many users treat it as invisible infrastructure. It supports cross-device task handoff across four device types: iPhone, iPad, Mac, and Apple Watch. The architecture is proximity-based. Devices signed into the same Apple account broadcast their current task over Bluetooth and then exchange state using Wi-Fi, without a cloud relay step in the standard path. Handoff is fully bidirectional. You can move a Safari page from iPhone to Mac, a Pages document from Mac to iPad, or an activity from Apple Watch to a larger device. A context-specific icon appears in the Mac Dock, the iOS App Switcher, or the right side of the iPad Dock. Apple’s own apps such as Safari, Mail, Maps, Calendar, Notes, and the iWork suite support Handoff, and a public API has encouraged third-party adoption over more than a decade.
Supported Tasks and Apps: State Transfer vs Web Fallback
Both systems aim to preserve the user’s place, but they approach supported tasks differently. In Android 17, Continue On focuses on “continuing the user journey” within and between Android apps. When you hand off Google Docs, Gmail, or Chrome, the receiving tablet opens the same content in the equivalent context. The standout capability here is app-to-web fallback: if the tablet does not have Gmail installed, a phone-initiated email thread can reappear as a specific webpage in Chrome, maintaining continuity even with asymmetric app setups. Apple Handoff, by contrast, prioritizes deep app-to-app state transfer within a tightly controlled ecosystem. Core Apple apps such as Safari, Mail, Notes, and Pages expose rich state so that documents, web pages, and other activities resume exactly where you left them. There is no generic “open in browser instead” behavior; instead, continuity depends on both devices having compatible apps that explicitly implement Handoff support.
Device Compatibility and Ecosystem Reach
The clearest gap in any Apple Handoff comparison is device coverage. Handoff works across iPhone, iPad, Mac, and Apple Watch with true bidirectional support. Any combination of these devices can initiate or receive a handoff, and the experience is consistent: a contextual icon appears in a predictable place on the receiving screen, and tapping it resumes the current task. Android 17’s Continue On is narrower at launch. It is specifically framed as phone to tablet handoff, even though the underlying Handoff API is designed to support more directions. Google has confirmed that tablet-to-phone transitions are planned but not yet available, and there is early speculation that other form factors like ChromeOS devices could eventually participate. For now, the feature requires both Android devices to be signed into the same Google account, and the experience is centered on that two-device relationship rather than a broader, multi-screen ecosystem.
Where Continue On Still Falls Short—and What It Gets Right
From a technical perspective, Continue On is the closest Android has come to native phone to tablet handoff, yet gaps remain. The most obvious limitations are directionality and platform breadth: only phone-to-tablet flows are supported at launch, and there is no equivalent of Handoff’s Mac or watch integration. Feature parity also lags on the app side. Apple’s Handoff API has been available since 2014, giving developers years to integrate; Android’s Handoff API is brand new, so real-world coverage will depend heavily on how quickly developers adopt it. However, Continue On’s design shows meaningful strengths. The app-to-web fallback is pragmatic and user-friendly in a fragmented Android landscape. The explicit focus on “continuing the user journey” encourages developers to think about stateful experiences instead of simple deep links. If Google can expand device support and drive broad app integration, Continue On could evolve from a promising start into a truly ecosystem-wide continuity layer.