From Chrome 126, a new feature in Chrome Custom Tabs on Android enhances the web experience for users and developers alike. With App-specific history, Android users can see browsing history specific to an app and act upon it in both the custom tab as well as Chrome.
For users, this makes finding and returning to content simpler than ever. They can continue to act on the inspiration originating from an app whether it be unanswered questions, incomplete shopping journeys, and more complex tasks that keep users coming back to Chrome and your app.
In order for this to work, though, developers need to opt-in. Specifically, you'll need to share your app package name with Chrome. Read more to find out the benefits of opting in for both you and your app's users.
How it works
App-specific history provides an entry point for users to view links opened in an app's custom tab. It lets Chrome users resume their browsing session from inside the Chrome app. Links from the originating app are grouped in Chrome's history, making it easier for users to find and return to a previously visited page.
App-specific history is enabled by using setShareIdentityEnabled. When used on a CustomTabsIntent, the API grants Chrome access to the host app's package name. This lets Chrome identify the Chrome Custom Tabs session and tag history entries.
Benefits for users
On mobile, users often have trouble returning to the content they have previously viewed. Browsers like Chrome maintain history, but many apps have embedded web experiences as well, making the history harder to scan and find. Existing solutions, like bookmarks, only go so far.
With App-specific history, users can quickly find and return to web content. This lets them continue their journey if they have already associated that product detail page or news article seen in content from your app. They'll be able to better filter down and understand the origins of the links in their history and see links reflected in both Chrome and the host app. Over time, users begin to rely on the seamless journeys between app and Chrome that make the two a helpful destination for those multi-session complex tasks.
![An Android web browser showing Chrome history](https://developer.chrome.com/static/blog/android-app-specific-history/image/chrome-history.png?authuser=8)
![An Android Custom Tab showing Overflow Menu](https://developer.chrome.com/static/blog/android-app-specific-history/image/in-app-custom-tab-overflow-menu.png?authuser=8)
Good for developers, too
App-specific history is a win for you as an app developer helping you to grow traffic and engagement within your app. Adding history and seamless transitions to Chrome discourages app abandonment and cases where users attempt to open custom tab content outside the app in a standalone browser.
Within the app, you get a free surface and launchpad into previous intent, campaigns and other high-quality interactions from most engaged users that go deeper on the content. Within Chrome, apps get branding and visibility that helps users revisit dormant tasks that require them to revisit your app.
App-specific history provides robust experiences and increases users' investment and productivity within the apps. Those who choose to opt-in are certain to see a benefit from an enhanced user experience.
Get started with App-specific history today
To get started with App-specific history, additional documentation and code can be found in the Android Browser Helper library. The API is specific to devices running Chrome and Android 14+.