# in-app-browsers

In-app browsers display web content within a mobile app, commonly using operating-system components such as Custom Tabs and WebView.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How to Add Payments to an Expo / React Native App

DevFeed: [How to Add Payments to an Expo / React Native App](<https://devfeed.tech/articles/how-to-add-payments-to-an-expo-react-native-app-9594.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/add-payments-react-native-expo/>)

Author: Aarthi Poonia

Published: 2026-03-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [Expo](<https://devfeed.tech/topics/expo.md>), [React Native](<https://devfeed.tech/topics/react-native.md>), [in-app-browsers](<https://devfeed.tech/topics/in-app-browsers.md>), [React](<https://devfeed.tech/topics/react.md>), [appstores](<https://devfeed.tech/topics/appstores.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [dodo](<https://devfeed.tech/tags/dodo.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [payments](<https://devfeed.tech/tags/payments.md>), [react-native](<https://devfeed.tech/tags/react-native.md>)

### AI overview

The guide describes an Expo/React Native checkout flow using Dodo Payments: create checkout sessions on an authenticated backend so secret API keys stay off the device, open the returned URL with `expo-web-browser`, and use `expo-linking` for the return trip. Configure a custom URL scheme and request a fresh session URL for each attempt; the guide says these URLs expire after 24 hours. It recommends validating backend inputs and using HTTPS. A deep link can update the app's UI, but the backend webhook should be the source of truth for granting access. Browser checkout is presented as easier to maintain and potentially suitable for multi-platform SaaS, subject to store rules; the article cautions against directing users to external payment to save money and suggests account or subscription settings. A native SDK offers a more integrated payment sheet and may help conversion, but platform fees may still apply depending on region and product. Store policy applicability and payment methods depend on context.

### Source excerpt

Learn how to add payments to your Expo or React Native app using Dodo Payments and WebBrowser.openBrowserAsync() to avoid the 30% app store fee for SaaS products.

## SwiftUI Custom URL Schemes

DevFeed: [SwiftUI Custom URL Schemes](<https://devfeed.tech/articles/swiftui-custom-url-schemes-21088.md>)

Original publisher: [Read original article](<https://useyourloaf.com/blog/swiftui-custom-url-schemes/>)

Author: Keith Harrison

Published: 2025-10-27T11:26:47Z

Content type: tutorial

Language: en

Sources: [K. Harrison](<https://devfeed.tech/sources/k-harrison.md>)

Topics: [SwiftUI](<https://devfeed.tech/topics/swiftui.md>), [in-app-browsers](<https://devfeed.tech/topics/in-app-browsers.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [async](<https://devfeed.tech/tags/async.md>), [auto-layout](<https://devfeed.tech/tags/auto-layout.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [custom](<https://devfeed.tech/tags/custom.md>), [data](<https://devfeed.tech/tags/data.md>), [display](<https://devfeed.tech/tags/display.md>), [error](<https://devfeed.tech/tags/error.md>), [extension](<https://devfeed.tech/tags/extension.md>), [file](<https://devfeed.tech/tags/file.md>), [format](<https://devfeed.tech/tags/format.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [handler](<https://devfeed.tech/tags/handler.md>), [html](<https://devfeed.tech/tags/html.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-26](<https://devfeed.tech/tags/ios-26.md>), [load](<https://devfeed.tech/tags/load.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swiftui](<https://devfeed.tech/tags/swiftui.md>), [url](<https://devfeed.tech/tags/url.md>), [webview](<https://devfeed.tech/tags/webview.md>), [wwdc](<https://devfeed.tech/tags/wwdc.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

### AI overview

The excerpt describes loading local App bundle resources in SwiftUI WebViews with a custom URL scheme on iOS 26. Implement a URLSchemeHandler that validates the request URL and scheme, derives a filename from the URL hostname, finds the file in the main App bundle, determines its MIME type from the extension, and returns a URLResponse with the data through an async sequence. Errors are thrown through the sequence. Register the handler in a WebPage configuration, then load and display the page with WebView; WebPage's load method also returns an async sequence that can track progress. The excerpt does not include the complete implementation or the final display details.

### Source excerpt

Create a custom URL scheme handler for SwiftUI WebViews. Custom URL schemes Apple introduced both WebView and WebPage SwiftUI views in iOS 26. These provide similar WebKit functionality to the UIKit WKWebView APIs. This includes being able to register custom URL schemes to load local resources. Suppose I have an App that loads quotations from the local App bundle. My URL scheme uses the format: quotes://001.html There are a few steps to support a custom URL scheme: Create a custom URL scheme handler that knows how to load the local resources. Register the scheme handler in a WebPage configuration. Have the WebView load and display the web page. Let's look at each of those steps. URLSchemeHandler (iOS 26) The URLSchemeHandler is a protocol with a reply method to return an async sequence of results. The AsyncSequence expects us to either yield a URLResponse and some data or throw an error. struct QuoteSchemeHandler: URLSchemeHandler { static let scheme = "quotes" func reply(for request: URLRequest) -> some AsyncSequence< URLSchemeTaskResult, any Error > { AsyncThrowingStream { continuation in ... } } } The reply method provides us with the URLRequest. I start by extracting the URL and checking it matches our quotes scheme: guard let url = request.url else { continuation.finish(throwing: QuoteError.missingURL) return } guard url.scheme == QuoteSchemeHandler.scheme else { continuation.finish(throwing: QuoteError.invalidScheme) return } To construct the URL response I need the mime type and length of the data. I first extract the filename from the URL, determine the mime type from the file extension, and then load the data: do { let file = try filename(for: url) let mimeType = try mimeType(for: file) let data = try Data(contentsOf: file) I can then build the URLResponse: let response = URLResponse( url: url, mimeType: mimeType, expectedContentLength: data.count, textEncodingName: "utf-8" ) If nothing has gone wrong I then add the response and the data to the AsyncSequenc

## Multi-tasking with Minimized Custom Tabs

DevFeed: [Multi-tasking with Minimized Custom Tabs](<https://devfeed.tech/articles/multi-tasking-with-minimized-custom-tabs-4185.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2024/05/multi-tasking-with-minimized-custom-tabs.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2024-05-29T16:08:00Z

Content type: release

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [in-app-browsers](<https://devfeed.tech/topics/in-app-browsers.md>), [picture-in-picture](<https://devfeed.tech/topics/picture-in-picture.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [browsing](<https://devfeed.tech/tags/browsing.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [none](<https://devfeed.tech/tags/none.md>), [picture-in-picture](<https://devfeed.tech/tags/picture-in-picture.md>)

### AI overview

Chrome M124 adds Minimized Custom Tabs: users can tap the down button in the Chrome Custom Tab toolbar to shrink a tab into a floating picture-in-picture window, then tap the window to restore it. The browser-level change applies automatically to developers using Chrome Custom Tabs. The source says this is a Chrome change and expresses hope that other browsers adopt similar functionality.

### Source excerpt

In the latest release of Chrome, we're introducing Minimized Custom Tabs, a feature that allows users to effortlessly transition between native app and web content. With a simple tap on the down button in the Chrome Custom Tabs toolbar, users can minimize a Custom Tab into a compact, floating picture-in-picture window. This seamless integration enables multi-tasking across surfaces, enhancing the in-app web browsing experience. By tapping on the floating window, users can easily maximize the tab, restoring it to its original size. How to get started Because this change happens at the browser level, developers who use Chrome Custom Tabs will see this change automatically applied starting with Chrome version M124. End users will see the Minimize icon in the Chrome Custom Tab toolbar. Please note that this is a change in Chrome, and we hope other browsers will adopt similar functionality. Posted by Victor Gallet, Senior Product Manager

## Chrome Custom Tabs in Android

DevFeed: [Chrome Custom Tabs in Android](<https://devfeed.tech/articles/chrome-custom-tabs-in-android-25832.md>)

Original publisher: [Read original article](<https://segunfamisa.com/posts/chrome-custom-tabs>)

Author: Segun Famisa

Published: 2016-06-04T08:05:30Z

Content type: tutorial

Language: en

Sources: [Segun Famisa](<https://devfeed.tech/sources/segun-famisa.md>)

Topics: [in-app-browsers](<https://devfeed.tech/topics/in-app-browsers.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Android](<https://devfeed.tech/topics/android.md>), [WebView](<https://devfeed.tech/topics/webview.md>), [browser](<https://devfeed.tech/topics/browser.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [browsing](<https://devfeed.tech/tags/browsing.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [look-and-feel](<https://devfeed.tech/tags/look-and-feel.md>), [webview](<https://devfeed.tech/tags/webview.md>)

### AI overview

Chrome Custom Tabs offer a middle ground between opening links in an external browser, which creates a large app-to-web context switch, and using a WebView, which the excerpt says takes technical work and gives users a less familiar browsing experience. A Custom Tab loads Chrome within the app and can make the transition feel more seamless. The excerpt lists toolbar color, enter and exit animations, and custom actions in Chrome's toolbar, overflow menu, and bottom toolbar as configurable options. It begins setup instructions by mentioning an app-level dependency and opening a tab with a URL, but cuts off before giving the dependency details or complete steps.

### Source excerpt

Introduction I have been seeing a behaviour in some apps for a while, and I've always wanted to know how it was done. I noticed some apps that allow to view urls within the app, used something that is "Powered by Chrome". I first noticed this on the Twitter for Android app, then on Medium, then Feedly. I was interested in knowing how these worked, but I didn't know what to search for. Finally, a few weeks ago, I stumbled on "Chrome Custom Tabs". Alas, that was what I was looking for. In this post, I'm going to explain why, when and how to use "Chrome Custom Tabs" in your Android applications. Why use Chrome Custom tabs? When building apps, developers are usually faced with difficult tradeoffs to make when we have to show web content in our Android apps. Very common and easy solution is to open links externally. If you do this, then these lines of code will look familiar: Intent browserIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(url)); startActivity(browserIntent); This typically results in a heavy-weight transition between the app and web. Launching a browser from your app to view web content results in a huge context switch which isn't customizable, and hence could lead to a terrible experience. An improvement on this experience will be to use a WebView which is essentially an Android view that displays web pages. However, this options requires technical work to implement and delivers a browsing experience that the users aren't used to. To solve this problem, the Google Chrome team introduced a new feature last September, called custom tabs. This allows to load a chrome tab within your app, and also allows you customize the look and feel of Chrome thereby making the transition between your app and the web content fast & seamless for your users. This is Chrome Custom tab in action on Twitter for Android app: Chrome Custom tab allows you customize the experience of Chrome. It allows you customize: Toolbar color Enter and exit animations Add custom actions to th