Google is testing a new Android feature that lets users start an app on their phone and seamlessly resume exactly where they left off on a nearby tablet. Codenamed “Continue On,” the capability has surfaced in an early build of what appears to be Android 17, and it signals Google’s most aggressive push yet to tie its hardware ecosystem together with Apple-like handoff. For the millions of Windows users who carry an Android in their pocket, the news is a reminder of how disjointed cross-device life still is — and a hint that change might finally be on the way.

What ‘Continue On’ Actually Does

According to reports that first emerged from developer forums and were later corroborated by Android-focused outlets, Continue On is a system-level service that uses Bluetooth and Wi-Fi to detect when a compatible tablet is nearby and signed into the same Google account. Open a supported app — the leaks point to Chrome, YouTube, and Google Maps as initial candidates — and a small pill-shaped chip appears at the edge of the screen. Tap it, and the app’s current state is beamed to the tablet, where it opens to the same scroll position, input field, or video timestamp.

Critically, the handoff is stateful. It’s not just syncing tabs or pushing a notification; the app’s full activity stack moves across devices. That means if you’re halfway through composing an email in Gmail on your Pixel 9, you can pick up a Pixel Tablet and find the draft open and ready to finish, right down to the cursor position. The feature is currently limited to Android phones and Android tablets only, and it requires both devices to be running the same beta build where the underlying APIs are present. There is no official word on when, or if, it will graduate to a stable release.

What It Means for You: From Home Users to IT Admins

For everyday home users, Continue On is a quality-of-life upgrade that eliminates the friction of manually reopening apps and finding content. It turns a phone and tablet into a single, fluid workspace. Students, for example, could research a topic in Chrome on their phone during a commute and then have the article waiting on a tablet screen at home. The feature feels natural because it mirrors the behavior many already expect: their devices should just know what they’re doing.

But Windows users specifically need to read between the lines. Right now, the Android-to-Windows bridge is built on Microsoft’s Phone Link app, which allows text messages, notifications, and screen mirroring, but offers nothing close to true app handoff. You can’t start a task in the YouTube app on your Samsung Galaxy and have it pop up on your Windows laptop without a clunky workaround. If Continue On remains Android-only, it creates a two-tier experience: seamless when moving within Google’s own hardware family, and fragmented when crossing into Windows. That could pressure Google to expand the feature to Chrome on Windows — a move that would instantly make the browser a much more powerful hub for productivity.

For IT admins and business users, the implications are more cautious. Seamless handoff means sensitive data can move across devices with less friction, which is great for productivity but raises security questions. If an employee can transfer an open session from a phone to an unmanaged tablet, corporate data policies need to catch up. Admins will want granular controls over which apps participate, and Google would need to build in management hooks before enterprises trust it.

Developers, meanwhile, should pay attention to the new APIs. If Continue On is to succeed, it needs a critical mass of third-party apps. Google will likely provide a simple integration path — similar to the Activity Recognition API — but app makers will have to decide whether the added development cost is worth it for a feature that currently exists only on a subset of Android tablets.

How We Got Here: A Brief History of Cross-Device Fumbles

The idea of moving a task seamlessly between devices isn’t new. Apple debuted Handoff in 2014 with iOS 8 and OS X Yosemite, allowing users to start an email on an iPhone and finish it on a Mac. It worked across a tightly controlled hardware and software stack, and it set the bar for what cross-device continuity should feel like. Google has spent a decade chasing that same vision, but its attempts have been uneven.

In 2015, Google introduced Nearby Share for file transfers, and later added Chrome tab sharing across signed-in devices. Neither was a true handoff. Samsung, with its Flow app, offered a more ambitious take, mirroring phone screens to Galaxy Books and, later, allowing app streaming. But Flow remained a Samsung-exclusive feature that never gained widespread adoption.

Microsoft’s answer came with “Your Phone” in 2018, which evolved into Phone Link. It brought Android notifications and text messages to Windows, and with select Samsung devices, allowed users to run phone apps directly on the desktop. While this felt like handoff, it was actually screen mirroring — the app still ran on the phone. The experience was useful but often laggy and limited by the phone’s battery and processing power.

The missing piece has always been a native, OS-level protocol that doesn’t require streaming. Continue On appears to be that protocol for Android. By baking the logic into the system and relying on local proximity, Google avoids the latency and battery drain that plague mirroring solutions. The catch: it works only with Android tablets today, and extending it to Chrome OS or Windows requires Google to port the service or convince Microsoft to adopt it.

What to Do Now: Preparing Your Workflow for Cross-Device Handoff

If you’re a dedicated Android user who already owns a tablet, the only way to try Continue On is to enroll in the Android Beta Program and flash the appropriate preview build on both devices. This is not for the faint of heart; beta software can be unstable, and the feature itself is still under wraps with limited app support. For most people, the advice is simple: wait.

But there are practical steps you can take today to simulate a similar cross-device experience, especially if you work across Android and Windows:

  • Use Chrome’s tab syncing aggressively. While not stateful handoff, sending tabs between your phone and Windows PC is instant and works for most web-based tasks.
  • Leverage web apps. Services like Google Docs, Outlook Web, and Slack keep your session in the cloud, so moving from device to device is as easy as opening a browser.
  • Set up Phone Link for notifications and calls. It won’t hand off app states, but it reduces the need to check your phone constantly.
  • Keep an eye on Google’s developer announcements. If Continue On expands to Chrome, it could be delivered as a browser update, requiring no OS change on Windows.

For IT decision-makers, start thinking about how stateful handoff fits into your mobile device management strategy. Features like this tend to arrive first in consumer builds and then creep into the enterprise. Having a conversation with your Android OEM or MDM vendor about future policies isn’t premature.

Outlook: Will Windows Be Invited to the Party?

Right now, Continue On is an Android-to-Android story. But the technology behind it — likely built on Bluetooth Low Energy and Google’s Fast Pair service — isn’t inherently limited to mobile devices. Google has a track record of bringing its best Android features to Chrome: think of how Nearby Share now works with Windows via a desktop client, or how Chrome OS integrated phone unlocking. A logical next step would be to bake Continue On into Chrome for Windows, turning every PC into a handoff target for tasks that live in the browser.

If Google goes that route, it would be a game-changer for Windows users. Suddenly, any web app could be handed from phone to desktop seamlessly. That would pressure Microsoft to respond, potentially by opening Phone Link to deeper integration or by building its own stateful handoff into the Microsoft Graph. The competitive pressure might finally deliver the seamless cross-device experience that Windows and Android users have long deserved.

Until then, Continue On remains a promising feature trapped inside a beta, inside a single ecosystem. But it’s the clearest signal yet that Google understands the value of device fluidity — and that the days of manually hunting for your place in every app may be numbered.