[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-21 (世界標準時間)。"],[],[],null,["# In-app browsing using Embedded Web\n\nIn-app browsers can provide a full browser experience for your users, while\nletting them stay in the context of your app. This is most commonly used when\nyou have a link or ad in your app which links to a web page. The web page can\nbe opened in an in-app browser, as seen in **Figure 1.**\n**Figure 1.** Clicking on an in-app link (left) and opening an in-app browser using a Custom Tab (right).\n\nBoth [Custom Tabs](/develop/ui/views/layout/webapps/overview-of-android-custom-tabs)\nand [WebView](/reference/android/webkit/WebView) are APIs available to power\nyour in-app experience, but choosing which one is best for you depends on your\nuse case. The following table shows some advantages of each:\n\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|\n| [**Custom Tabs**](/develop/ui/views/layout/webapps/overview-of-android-custom-tabs) | | | [**WebViews**](/reference/android/webkit/WebView) | | |\n| Out-of-the-box ready browsing for 3rd party content handled by the user's default browser. Most common for the majority of use cases. | | | Custom developer controlled browsing experiences. Typically used for more advanced use cases. | | |\n| - Ease of integration: Integrating Custom Tabs is the simplest and easiest way to provide users an Embedded Web browsing experience - Shared state: Reduced user friction when logging into sites given shared cookies and permissions model with the browser | | | - More advanced UI control of the browser view - Be able to modify the contents of the web page itself - Deeper developer analytic insight into engagement / activity - WebView updates roll out to all devices and users consistently and globally | | |\n\n| **Note:** You can also choose to not use an in-app browser and use an [Android Intent](/guide/components/intents-filters) to link out of your app to the user's default browser. Doing so launches the browser and takes the user to the website in the user's default browser app.\n\nAlthough Custom Tabs are supported by a vast majority of browsers, some offer\nadditional customization options. To learn more, see this\n[Custom Tabs browser support comparison](https://developer.chrome.com/docs/android/custom-tabs/browser-support).\n\n### Additional resources\n\nTo develop web pages for Android-powered devices using WebViews or Custom Tabs\nAPIs, see the following documents:\n\n- [Embedding web content into your app as primary or supporting content](/develop/ui/views/layout/webapps)\n- [Custom Tabs Overview](/develop/ui/views/layout/webapps/overview-of-android-custom-tabs)\n- [Overview of Trusted Web Activities](/develop/ui/views/layout/webapps/trusted-web-activities)\n- [Browser support](https://developer.chrome.com/docs/android/custom-tabs/browser-support)"]]
