For example, the new partial custom tabs feature allows apps to open split-screen tabs when you tap on an article link. The developer can choose the size of the overlay, with the aim of allowing you to interact with the app and the in-app browser at the same time. Of course, you can expand the custom tab to full screen view by dragging the toolbar up. If you want to return to the original launch height, just drag the toolbar down. But if your favorite browser doesn’t support this feature, the links will still open in a custom full-screen tab.
Custom tabs were originally introduced as a feature of Google Chrome, but have since been extended to work with all supported browsers. This is powered by the androidx.browser library, which connects apps to the user’s default browser to view web pages without leaving the native app – handy for keeping logins, widgets plugins and other browser-specific settings when viewing web content in non-browser applications.
According to Google’s blog, some custom tabs are currently supported by some in-app browsers, such as Chrome. However, Google has promised support for some of the best web browsers.
Interestingly, this capability has been around since Chrome 107, released last October, and androidx.browser version 1.5.0-alpha01, as spotted by Mishaal Rahman. However, version 1.5.0 of androidx.browser was only recently released on the stable channel, so it’s no surprise that Google is now officially making this feature available.
Additionally, custom tabs will now indicate when a web page is “running in Chrome”, giving you the impression that Chrome’s nifty features, including autofill and saved passwords, easily accessible. Custom tabs have done a great job of helping developers keep users engaged with their apps without interruption, and the latest feature is an enhancement to in-app navigation.