Android 17 adds 'Continue On' handoff

- Google added Continue On to Android 17 in May 2026, giving developers a new way to hand off app activity between Android devices. - Android Developers says Continue On is available in Android 17, API level 37, and works per activity after developers call `setHandoffEnabled(true)`. - Android 17 Beta 3 reached platform stability on March 26, 2026, and Google’s Continue On documentation is live for developer testing.

Google has added a new cross-device feature called Continue On to Android 17, extending task handoff between Android devices tied to the same Google account. Google’s developer documentation says the feature lets users start an app activity on one Android device and continue that journey on another device in their Android ecosystem. The initial coverage around the feature has centered on phone-to-tablet resume, with compatible apps surfacing a handoff entry point on the tablet taskbar. The feature has been widely compared with Apple’s Handoff by outlets including The Verge and 9to5Google. ### Where did Continue On actually show up? Google published Continue On documentation on Android Developers last week, describing it as “a new feature available in Android 17 (API level 37).” The same documentation says the feature is part of Google’s “Better Together” effort and is designed to provide cross-device continuity for users moving between Android devices. (developer.android.com) Android 17 Beta 2, published on February 26, said Google was adding “cross-device handoff APIs,” and Beta 3, published on March 26, said the platform had reached stability with the API surface locked. That places the handoff framework inside the public Android 17 release cycle rather than as a separate Google app experiment. (developer.android.com) ### What does the feature do on a user’s devices? Google’s feature page says Continue On allows a user to begin an activity on one Android device and transition it to another device in the same Android ecosystem. Coverage from The Verge and Android Authority says the first visible use case is resuming work from a phone onto a tablet, with the tablet taskbar showing a suggestion to continue the task. (android-developers.googleblog.com) Tech Advisor reported that Google has described examples such as browsing in Chrome or editing Google Docs on one device and resuming on another. That report also said the system can fall back to a web interface when the same native app is not installed on both devices. Google’s developer pages describe sender and receiver devices and include setup and testing guidance for developers implementing the flow. (developer.android.com) ### What do developers have to build? Google says Continue On is off by default and must be enabled on a per-activity basis. The Android Developers documentation says developers need to call `setHandoffEnabled(true)` only when an activity is ready to be handed off, and can check state with `isHandoffEnabled`. Google’s setup documentation says developers must configure and test the feature against supported device requirements, and the receiving device should launch into the specific activity requested by the handoff flow. (techadvisor.com) That means Continue On is not automatic for every Android app; app makers have to opt in and define where a resumed session should land. (developer.android.com) ### Why is Apple’s Handoff part of every comparison? The Verge described Continue On as Android 17 getting “its own version of Apple’s Handoff,” while 9to5Google said Google was setting the stage for Android’s version of Apple Handoff. Those comparisons reflect the same core behavior: starting work on one device and resuming it on another without manually reopening context. (developer.android.com) Google’s own feature page uses the term “Handoff” in the Android 17 features list, even though the developer documentation brands the capability as Continue On. The pairing suggests Google is presenting the feature both as a user-facing continuity tool and as a developer API surface for cross-device session transfer. ### What changes next for app makers? (theverge.com) March 26 is the key date for developers because Android 17 Beta 3 marked platform stability, allowing final compatibility testing and Play Store targeting for Android 17 apps, Google said. With the documentation already published, developers can begin implementing activity-level support and testing how handoff appears across phones and tablets. (developer.android.com) Tech Advisor reported Android 17 is expected to launch in June or July 2026. Between now and that release window, the next concrete step is whether app developers add support for Continue On in enough apps for the feature to become visible beyond Google’s own ecosystem examples. (techadvisor.com) (android-developers.googleblog.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.