In-app browser
Opens outside links in a browser inside the app.
In one line
Can show web pages inside the app and, in some versions, watch what you do
Opens outside links in a browser inside the app.
The host app can see page loads and may inject script. Isolated tabs like SFSafariViewController block that; plain WebViews do not.
What it can and can't do
What the user does: You tap a link inside the app and it opens without leaving the app
It can
- Show a web page inside the app window with no prompt
- Watch which pages you open and when they finish loading
- Add its own script to the page when it uses a plain in-app web view
- Keep you inside the app instead of switching to your browser
It cannot
- Add script or watch taps in the isolated browser tabs (Android Custom Tabs, iPhone Safari view)
- See your saved passwords or open tabs from your own browser app
- Keep watching once you tap Open in Safari or Open in Chrome
How it differs between platforms: Both phones offer an isolated tab the app cannot change and a plain web view it can; which one you get depends on how the app was built.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 1.0 (API 1) | iOS 2.0 |
| Permission or entitlement | INTERNET | Not listed |
| Protection level | normal | none |
| How access is granted | install | none |
| What the user sees | No prompt | No prompt |
| How long it lasts | WebView storage per app | WKWebView storage per app |
| How to take it back | Clear app data | n/a |
| Store policy | None listed | App Review 5.1.2 |
| API | WebView vs Custom Tabs | WKWebView vs SFSafariViewController |
| Notes | Custom Tabs are isolated; WebView exposes JS injection to host | SFSafariViewController is isolated and does not allow script injection by the app |
Data you get
What comes back: Page navigation and injected script results
Shape: event
How often: per page
No individual data fields. The signal is the access itself.
Technical limits
- Cannot read passwords typed in an isolated tab
The story
What it is
Opens a web link inside the app instead of sending you to your normal browser.
For you
You tap a link in a post or chat and the page opens right there, with no app switch. You may not notice that the app can see what you tap and type on that page, unlike in Safari or Chrome. Your saved passwords may also be missing.
For makers
Keeping people inside the app means more time on screen and more ads seen. A plain web view lets the app measure clicks, scroll depth and form use on outside sites. The safer isolated tabs trade that visibility for trust.
Where you see it
| Type | Example | Apps |
|---|---|---|
| social | You tap a link in a friend's post and the page opens inside the feed app, so the app can log how long you read before you swipe back. | Instagram, Facebook, TikTok |
| messaging | A shared article in a chat app opens in a built in window with a Back to chat button, and the app shows its own share sheet over the page. | Snapchat, LinkedIn |
| ads | An ad click opens the advertiser site inside the app, letting the ad network confirm the visit and count it for billing. | None named |
| payments | A checkout page opens in a secure tab so a bank login or 3D Secure step works with saved cards and autofill. | None named |
| games | A mobile game opens its Terms or a support form in an in-app page, so you can return to the match without losing your place. | None named |
| news | A news reader app loads full stories in an embedded page, then injects its own reading mode or ad blocker script. | |
| security | Security researchers test whether big apps add hidden scripts to outside pages, which showed that some do. | None named |
Risks
- App can watch what you tap or type
- Outside pages may be altered
Android and iPhone in short
- Android: Plain WebView lets the host app inject scripts, while Custom Tabs are isolated and keep your normal browser sign ins.
- iPhone: WKWebView lets the host app inject scripts, while SFSafariViewController is isolated and the app cannot read it.
What the platform says
- Google: Chrome Custom Tabs. Developer pitch: show web content inside your app with the speed, saved logins and security of Chrome.
- Apple: SFSafariViewController. Developer pitch: show a full Safari experience inside your app, with the app unable to see what you do on the page.
Good uses and abuse
Legitimate uses
- Fast link viewing
Known abuse
- Keystroke and tap logging
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2017-09, iPhone iOS 11: SFSafariViewController no longer shares cookies with Safari
- 2022-08, iPhone iOS 15: InAppBrowser tool shows injected scripts of other apps, not LinkedIn
Related capabilities
Related
- Universal Links and Android App Links. Can open the app directly from a website link, with the full link and campaign tags
Same idea on the web
- Navigational tracking. Can pass an ID along when you move between sites by link or redirect
Sources
How well checked: Inferred from related behavior.