Tuesday, November 4, 2014

applications - Prevent apps opening links in Chrome Custom Tabs (i.e. open in default browser directly)


Not long ago, Google added a new feature called Chrome Custom Tabs since Chrome 45 on Android JellyBean or later.




What are Chrome Custom Tabs?


App developers face a choice when a user taps a URL to either launch a browser, or build their own in-app browser using WebViews.


Both options present challenges — launching the browser is a heavy context switch that isn't customizable, while WebViews don't share state with the browser and add maintenance overhead.


Chrome Custom Tabs give apps more control over their web experience, and make transitions between native and web content more seamless without having to resort to a WebView.


When will this be available?


As of Chrome 45, Chrome Custom Tabs is now generally available to all users of Chrome, on all of Chrome's supported Android versions (Jellybean onwards).


custom tabs demonstration



Google has integrated this feature on some of their apps (e.g. Google+, Google Search) and now, 3rd-party apps can also use it (e.g. Twitter, Stack Exchange).


While some apps provide setting to enable/disable it (e.g. Google Search), others don't seem to be possible to disable this. I know I can still open the link in Chrome by tapping the overflow menu (3-dots on top-right) and select Open in Chrome. However, it'd be preferable if it can be disabled on specific apps.



So, my question is: is it possible to disable this feature, preferably on selective apps? (by disable, I mean to open the link directly in default browser, or prompt user to choose a browser)


Note: I'm open to all suggestions, including root solutions, or even uninstalling Chrome in the worst case scenario. However, more practical answers are preferred.




No comments:

Post a Comment

samsung galaxy s 2 - Cannot restore Kies backup after firmware upgrade

I backed up my Samsung Galaxy S2 on Kies before updating to Ice Cream Sandwich. After the upgrade I tried to restore, but the restore fails ...