Tap a link in Instagram and it doesn't open in Chrome or Safari. It opens in a browser inside Instagram, with Instagram's toolbar on top and a small × to get back to the feed. The same happens in Facebook, TikTok, LinkedIn, Threads, Snapchat and plenty of other apps.
That browser looks like the real one, but it isn't. For anything that needs a login, a saved password or a card on file, the difference matters. This post explains what in-app browsers are, why they hurt sign-ups and sales, and what a link can and can't do about it.
What an in-app browser is
An in-app browser (or in-app webview) is a web page shown inside another app instead of handing the link to the phone's browser. Apps do it to keep people in the app: close the page and you're back where you were scrolling.
There are a few kinds, and they behave differently:
| Kind | Platform | Shares the person's browser logins? |
|---|---|---|
| WebView | Android | No: its own cookies and storage |
| Chrome Custom Tabs | Android | Yes: it's the real browser, framed |
| WKWebView | iPhone | No: its own cookies and storage |
| SFSafariViewController | iPhone | No: kept apart from Safari since iOS 11 |
The big social apps mostly use the first and third kind: a browser the app runs itself. That's the one that causes the trouble below.
What it costs you
Everything people have set up in their own browser is missing:
- They're logged out. Your shop, your app's web version, your community: the session lives in their real browser, not in Instagram's.
- No saved passwords or autofill. Password managers and saved addresses usually don't reach inside another app's webview, so people type, or give up.
- "Sign in with Google" can fail. Google blocks its sign-in in embedded webviews, so that button shows an error instead of an account picker.
- Carts don't follow. Add something to the cart in the in-app browser, open the shop later in Chrome, and the cart is empty, because it was a different browser.
- Analytics split. The same person shows up as two visitors with two sessions, one per browser.
None of this shows up as an error. It shows up as a sign-up page with a lower conversion rate from social traffic than from everywhere else.
How people get out by hand
Most in-app browsers have a way out, in the ••• or ⋮ menu: an item called Open in browser, Open in Chrome or Open in external browser, depending on the app and the phone. It works, but few people know it's there, and you can't count on someone doing it before they decide your checkout is broken.
So the question becomes whether the link can do it for them.
What a link can do about it
On Android, yes. A page can hand an address back to Android with an intent, and an intent that names no app leaves the choice to the phone. For an ordinary web page, the phone's choice is the person's default browser: Chrome, Samsung Internet, Firefox, Brave, whichever they picked. That's where their logins are.
acme.tnb.li/shop inside InstagramSees an in-app WebView and answers with an intent that names no app
On iPhone, no. iOS gives a web page no way to open the person's default browser. There are tricks that force Safari open (an x-safari-https:// address, for one), but Safari is only the right answer for people who use Safari. Someone on Chrome or Firefox would land in a browser where they aren't logged in either, and have to move again. We'd rather not send people somewhere arbitrary, so on iPhone the link behaves as usual.
How it works on tinbo
The switch is Open in external browser on Android, in the link's Redirect card under Change, on the Basic plan and up. With it on:
- Taps inside an Android in-app WebView get the hand-off to the default browser. tinbo spots them by the
; wv)marker these browsers put in their user agent. - Everyone else gets the normal redirect: real browsers, Chrome Custom Tabs (already the real browser), iPhones and computers.
- The click is counted as usual, with its referrer, country and device. Geo and device rules, A/B tests and expiry all apply first, and the hand-off carries whichever destination they picked.
We've tried it from Instagram on Android, where it works. Other apps' webviews may still keep the link inside, so it's worth a test from the app your audience uses before a campaign.
If the destination is itself an app, a YouTube video or an Instagram profile, you don't need this switch. Open in app sends people to that app instead of any browser, on iPhone too. How to make YouTube, Instagram and TikTok links open in the app covers that one.
When to turn it on
Turn it on for links where being logged in, or having saved details, decides whether people finish:
- a shop or checkout,
- a sign-up or log-in page, especially one with "Sign in with Google",
- a web app or dashboard,
- anything paid that relies on saved cards.
Leave it off for content meant to be read in passing: an article, a menu, an event page. There the in-app browser does the job, and staying in the app is what people expect.
The features page lists what's on each plan.