Android 17 Continue On: Seamlessly Move Tasks Between Android Devices

For example, someone browsing a website on a phone could pick up a tablet and immediately see a suggestion to continue that session. Selecting it launches the same experience on the larger screen.

The underlying architecture: sender and receiver

Technically, Continue On uses a sender/receiver model built into Android.

• Sender device: the device where the activity originally started.
• Receiver device: the nearby device that requests and resumes the activity.

Apps must explicitly declare that an activity can be transferred. Developers enable support by marking activities as handoff‑ready using the Android 17 APIs (for example, calling setHandoffEnabled(true) when an activity is ready to be transferred).

Once enabled, the app supplies continuation data describing how the task should resume on the receiving device. The Android system handles the rest of the coordination between devices.

Nearby device detection and account linking

Continue On works only when Android determines that another device is eligible for the handoff. Several conditions typically apply:

• The devices must be near each other.
• They must belong to the same user ecosystem, usually linked by the same account.
• Both must support Android 17 and the Continue On feature.

When these conditions are met, the system can advertise the transferable activity to nearby devices and display a suggestion in system UI such as a tablet taskbar or launcher.

Secure local communication between devices

Instead of forcing each app to implement its own networking or pairing system, Continue On relies on system‑managed device communication.

Android coordinates the transfer using secure local communication between the devices while associating the session with the user’s account and app context. This system approach ensures that developers do not need to build custom cross‑device transport layers themselves.

Public documentation confirms the existence of this secure communication layer but does not provide a full technical specification of the underlying protocol or cryptographic details.

What happens if the app isn’t installed on the receiving device

Continue On supports a fallback path when the receiving device lacks the native app.

Developers can provide web continuation data, allowing the receiving device to open the equivalent experience in a browser instead.

If the continuation uses a standard web intent, Android resolves it according to normal app‑link rules: if the app is approved for that domain it can open in the app, otherwise it launches in the user’s default browser.

This fallback ensures the user can still continue the task even if the native app isn’t present on the second device.

Current limitations and developer requirements

Continue On is powerful but comes with several constraints today:

• Android 17 only: The feature is part of Android 17 (API level 37).
• Developer opt‑in: Apps must explicitly implement the APIs and enable handoff for each activity. It does not work automatically.
• Device scope: Early demonstrations focus primarily on transitions between phones and tablets.

Documentation and early reports do not yet specify every supported device type, distance requirement, or all system surfaces where handoff suggestions will appear, indicating the feature is still evolving.

Android 17 availability and timeline

Continue On is included in the Android 17 platform and its developer APIs. Android’s release cadence now targets a major SDK release in Q2 2026, with additional updates later in the year.

Developers can already begin experimenting with the APIs in Android 17 builds, integrating cross‑device handoff into their apps before broader device rollout.

Why Continue On matters

Continue On represents a shift toward a device‑agnostic Android experience. Instead of treating phones, tablets, and other devices as separate contexts, the platform is gradually enabling workflows that move fluidly between screens.

For users with multiple Android devices, this means tasks can follow them across devices rather than restarting each time they switch screens—a step toward a more unified Android ecosystem.