Google’s Answer to Handoff Arrives in Android 17
With Android 17, Google is closing a long-standing gap in its ecosystem with a new app continuity feature called Continue On. Announced at Google I/O as part of the “What’s new in Android” updates, Continue On lets users start a task on one Android device and resume it on another signed into the same account. Functionally, it mirrors Apple’s Handoff, which has allowed similar cross-device transitions on iOS and macOS for years. In its initial beta and upcoming release candidate form, Continue On focuses on streamlining everyday workflows rather than showcasing flashy AI. It aims to cut down on re-opening apps, digging through recent tabs, or manually navigating back to the right screen whenever users switch devices. For Android, this marks a strategic move toward a tighter, more Apple-like ecosystem experience where devices feel less like isolated endpoints and more like parts of a single, continuous workspace.
How Continue On Works Across Phones, Tablets, and the Web
Continue On is built around cross-device app switching that feels as natural as picking up the nearest screen. When you move from your Android phone to a compatible tablet, Android 17 surfaces a contextual “Handoff Suggestion” in the tablet’s taskbar or dock. Tap it, and the app or task you were using on your phone opens on the tablet in the same state. Google has demonstrated this with Google Chrome and Google Docs: a web page or document opened on a phone reappears on a tablet at the exact same tab and cursor position. The app continuity feature supports both app-to-app and app-to-web transitions. That means a Gmail conversation started in the mobile app on your phone can resume in the Gmail web interface on your tablet via Chrome, even if the native app is not installed, thanks to a built-in browser fallback.
Early Limitations: Phone-to-Tablet Today, Bidirectional Tomorrow
Despite its promise, Android 17 Continue On launches with notable limitations. Initially, it only supports handoff from phone to tablet, leaving tablet-to-phone and other combinations for a later date. Google has been clear that the underlying system is designed to be bidirectional: in theory, any supported Android device will eventually be able to both send and receive live app sessions. However, the company has not provided a timeline for when those broader scenarios will be available. For now, the experience centers on picking up a larger screen and having your recent phone activity appear in the tablet dock or taskbar. That focus aligns with Google’s push to make Android tablets more useful for productivity and multitasking. The staged rollout also suggests Google is testing reliability and UX polish before expanding the feature to a wider range of device pairings and use cases.
Developer Adoption Will Decide How Seamless It Feels
The effectiveness of Continue On will hinge on how broadly app developers embrace it. Google is leaving many implementation details to developers, offering flexible options for handoff Android devices. Apps can resume directly into their native tablet counterparts or redirect to a web experience if the app is missing on the receiving device. For example, a Google Docs file can open in the Docs app on a tablet, while a Gmail thread can appear in the browser instead. This flexibility helps ensure there is almost always a way to continue a task, but it also means experiences may vary from app to app. To help, Google has published a developer blog describing APIs and best practices. If major productivity, communication, and entertainment apps integrate the feature, cross-device app switching could quickly become a default expectation rather than a niche perk.
Toward a More Cohesive Android Ecosystem
Android 17 Continue On is more than a single convenience feature; it signals a broader ecosystem strategy. Google has been steadily building cross-device services that make phones, tablets, and other form factors feel more integrated, from shared clipboard tools to casting and multi-device experiences. Continue On is a key missing piece, especially now that Google is also talking about Android-powered laptops and larger-screen devices that could participate in the same continuity framework. While critics point out that Google is effectively cloning a concept Apple shipped back in 2014, cross-platform feature borrowing has long gone both ways. What matters most to users is the end result: less friction when moving between screens. If Google can refine bidirectional support and win strong developer adoption, Android’s app continuity feature may finally deliver an ecosystem that feels genuinely cohesive across all your devices.