What Continue On Is and Why It Matters
Continue On is Google’s new Android 17 feature that lets you start a task on one Android device and pick it up on another without losing your place. Functionally, it is an Android Handoff alternative, mirroring the seamless continuity Apple users have enjoyed for years. Until now, Android’s ecosystem lacked a unified, platform-level way to move live activities—like editing a document or reading an email—between devices. Users had to reopen apps, find the right file or tab, and manually resume work. By bringing cross-device app continuity into the core OS, Google is directly targeting one of Android’s biggest productivity weaknesses. Continue On integrates at the system level and is available to any developer who implements the new APIs, meaning it can extend well beyond Google’s own apps. For users, that promises smoother workflows, fewer taps, and a more cohesive experience across phones and tablets.
How Android’s Cross-Device App Continuity Works
With the Android Continue On feature, tasks move via what Google calls a “Handoff Suggestion.” When you’re using a supported app—say Google Docs or Chrome—on your phone and unlock your Android tablet, the tablet’s taskbar shows a labeled app icon representing the current activity. Tapping the normal app icon opens the app as usual; tapping the Handoff Suggestion resumes the exact document, page, or thread you were working on. Developers can implement two continuity paths. App-to-app handoff opens the same app on the tablet, restoring state so you continue exactly where you left off. Web handoff instead launches the activity in the tablet’s default browser, ideal for services with strong web experiences like Gmail. There’s also a fallback: if the receiving device doesn’t have the app installed, the task can still open in a browser, ensuring continuity rather than failing silently.
Phone-to-Tablet First: The Strategic Limitation
At launch, Continue On supports only phone to tablet handoff, even though the underlying framework is designed to work bidirectionally and across multiple device types. Practically, that means users can move from a smaller phone screen to a larger tablet for more comfortable editing, reading, or browsing—but not yet the other way around. This limitation matters for productivity because it reveals Google’s priorities. Android 17 productivity features are clearly focused on making tablets credible work companions, turning them into natural extensions of the phone. Many users already treat tablets as secondary devices for deeper work, so optimizing phone to tablet handoff addresses the most common use case first. At the same time, Google has explicitly described Continue On as bidirectional, strongly hinting that future updates will unlock tablet-to-phone and potentially broader device support once the initial rollout stabilizes.
Closing the Gap with Apple’s Handoff and Beyond
Apple’s Continuity and Handoff have long set expectations for fluid multi-device workflows, letting users jump between iPhone, iPad, and Mac with minimal friction. Android users, by contrast, have relied on workarounds or vendor-specific solutions from manufacturers like Samsung. Continue On changes that equation by putting cross-device app continuity in the Android core, not as an add-on. This Android Handoff alternative is especially significant because it is open to all developers, not just Google’s own apps. Examples Google has shown—such as handing off Chrome browsing sessions or Google Docs documents—illustrate the potential, but the real value emerges when third-party productivity, messaging, and creative tools join in. While the first version is restricted to Android-to-Android phone to tablet handoff, the framework’s flexibility suggests future expansion to other form factors, and possibly even other platforms, as Google evolves its broader ecosystem strategy.