What Android 17’s Continue On Actually Does
Continue On in Android 17 is Google’s clearest answer yet to Apple’s Handoff, and it works on a similarly simple premise: start a task on one Android device and resume it on another without friction. When you’re using an app on your phone and pick up a tablet, Android can surface a suggestion in the tablet’s taskbar to open that same app. Tap it, and you’re dropped back into the exact state you left off on the first device, rather than the app’s home screen. Google says this app handoff feature is fully bidirectional, so any compatible Android device can act as sender or receiver. In other words, there is no single “primary” device; your phone and tablet share a continuous workspace, enabling seamless app switching as you move between screens throughout the day.
How Continue On Closes the Ecosystem Gap
For years, Android’s biggest weakness for power users has been cross-device continuity, not core phone features. Apple’s Handoff made it trivial to jump between phone, tablet, and laptop, while Android users resorted to manual syncing, cloud documents, or awkward copy‑and‑paste workarounds. Android 17 Continue On is a direct attempt to close that ecosystem gap. By letting app sessions move fluidly between devices, Google is turning separate gadgets into a loosely unified environment. The feature goes beyond simple recent‑apps syncing: the receiving device restores your in‑app context, such as the specific Google Doc tab or email thread you were viewing. That brings Android much closer to a coherent multi‑device story, where workflows travel with you instead of being siloed per device, and positions Android as a more credible option for users already accustomed to polished app handoff feature sets elsewhere.
From Native Apps to the Web: Flexible Handoffs for Real Workflows
Continue On is built to handle the messy reality of modern app usage, where sessions often span native apps and web experiences. Google’s demos show a Google Docs file opened on a phone jumping to the same document and tab on a tablet, preserving document state. With Gmail, the handoff can move from the Android app on a phone to the Gmail website on a larger‑screen device, landing directly on the same email conversation. Developers can choose whether their apps resume in a native tablet app or fall back to the web. There is also a safety net: if the receiving device doesn’t have the relevant app installed, Continue On can open the task in a browser instead. This flexible approach ensures cross-device continuity works in more scenarios, not just in a fully curated, all‑apps‑installed ideal setup.
What Multi-Device Users Can Expect at Launch and Beyond
At launch, Android 17 Continue On will focus on phone‑to‑tablet transitions, with suggested apps appearing right in the tablet’s taskbar for quick access. That’s a logical starting point, given how often people escalate tasks from a small phone screen to a larger tablet display for reading, editing, or multitasking. However, Google has already confirmed the feature is designed to be bidirectional, and its broader cross-device services strategy points toward support for more form factors over time. For multi-device users, the immediate payoff is reduced friction: no more hunting for the right document, tab, or message after you switch screens. Instead, you can rely on seamless app switching to keep your work in sync as you move. It’s a tangible sign that Google is serious about turning Android into a cohesive, device‑spanning platform rather than a collection of isolated gadgets.