Enhance your users' browsing experience with App-specific history

With App-specific history, Android developers and their users can gain more control over their web browsing experience using Chrome Custom Tabs. Opt in, then enable a history for in-app custom tabs that's specific to the browsing activity performed in your app, as opposed to the more-encompassing history seen on the Chrome app on the user's device.

App-specific history provides an entry point for users to view links opened in the app's custom tab. It lets Chrome users resume their browsing session. Links from the originating app are displayed in Chrome's history along with the app's name, making it easier for users to find a previously visited page and resume their experience. Enabling App-specific history has no impact on cookies or sign-in state.

App-specific history is available from Chrome 126, and requires an app package name to be shared so Chrome can distinguish the custom tab's session origin. This is done using setShareIdentityEnabled, that is available from Android 14.

An Android web browser showing Chrome history
Figure 1. Chrome History.
An Android Custom Tab showing Overflow Menu
Figure 2. In-App Custom Tab Overflow Menu.

Enable App-specific history

Developers can opt in to App-specific history by using the setter provided in CustomTabsIntent:

// In your activity

String url = "https://developers.android.com";
CustomTabsIntent customTabsIntent = newCustomTabsIntent.Builder()
    .setShareIdentityEnabled(true)
    .build();

customTabsIntent.launchUrl(MainActivity.this, Uri.parse(url));

When App-specific history is enabled, users can tap on "Chrome history" from the custom tab's three-dot menu to view a previously visited page.

Why choose App-specific history?

With App-specific history, users can quickly locate web content they've browsed before and resume their journey. They'll be able to see these links reflected in both Chrome as well the host app, reducing user friction and creating an overall better experience.

For developers, App-specific history further enhances Chrome Custom Tabs, which can improve user engagement and app traffic.

Limitations

  • Devices must be running Android 14+ for history entries to be tagged using the setter method.
  • The user's selected browser must be Chrome running version 126 or greater.

Additional resources