The Android 17 Handoff API
Short answer: Handoff is a new Android 17 feature and API for cross-device continuity: a user starts an activity on one Android device and picks it up on another nearby device they own, from entry points such as the launcher and taskbar. You enable it per activity with setHandoffEnabled() and return a HandoffActivityData from onHandoffActivityDataRequested() describing how to recreate the activity. If your app isn’t installed on the other device, a web fallback URL can open instead.
Handoff building blocks
From Android 17 Features and APIs and the HandoffActivityData API reference, read 1 October 2026.
| Piece | What it does |
|---|---|
| Activity.setHandoffEnabled() | Turns Handoff on for that activity |
| Activity.onHandoffActivityDataRequested() | Callback where you return the data to recreate the activity |
| HandoffActivityData component name | The activity launched on the receiving device |
| HandoffActivityData extras | A PersistableBundle passed to the launch intent, for restoring state |
| Fallback URI | Opened in the browser if the component can’t be launched |
| HandoffActivityData.createWebHandoff(Uri) | A web-only handoff, with no app component |
App-to-app and app-to-web
In the app-to-app flow, the receiving device launches the same native app, if it is installed, and deep-links the user to the designated activity. The receiving device builds a launch intent for the component you name and passes along your extras, so put what’s needed to restore state, such as a document position or open tab, in the extras. As a fallback, or instead, you can offer app-to-web Handoff: if the component can’t be launched, the fallback URI opens in the device’s web browser; with no fallback the user sees an error. When the system hands off a whole task and the component can’t be resolved, only the top activity is handed off.
Where users see it
Handoff runs in the background and surfaces activities available from the user’s other nearby devices through entry points like the launcher and taskbar on the receiving device. Google’s September 2026 Googlebook post calls the experience Continue On, with handoff in both directions between phones, tablets and Googlebooks. See Googlebook for Android developers and the Android 17 behavior changes checklist.
Where Censuus fits
Continuity keeps users in your app across devices; being found brings them there first. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.
Frequently asked questions
What is Handoff in Android 17?
A feature and API that lets a user start an app activity on one Android device and continue it on another of their devices, surfaced through entry points like the launcher and taskbar.
How do I enable Handoff for an activity?
Call setHandoffEnabled() on the activity and implement onHandoffActivityDataRequested() to return a HandoffActivityData object.
What happens if my app isn’t installed on the other device?
If you set a fallback URI, it opens in the device’s web browser. Without one, the user sees an error.
Which API level adds HandoffActivityData?
API level 37, Android 17.
Guides for app developers
- Android AppFunctions: your app as on-device tools for AI agents
- Android 17 behavior changes: a checklist for target SDK 37
- Getting your Android app ready for Googlebook
- Android Contact Picker and the new READ_CONTACTS rules
- How to transfer an app to another developer account
- The Play Integrity API: what it checks and how to use it
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.