Why do so many mobile apps open links in built-in browsers?
Asked by
beaker rack
A lot of mobile apps open web links inside their own built-in browser instead of handing them off to the browser or app already installed on the phone. As a user, I often have to log in again, deal with a smaller or less useful interface, lose the page if I close the view accidentally, and struggle to find the content later because it does not appear in my normal browser history. Deep links can also fail behind authentication, and some apps do not open their corresponding installed app at all. What benefits do companies get from using built-in browsers, and why is this pattern still so common despite the frustration it causes?
Answers
There is also a legitimate usability reason: without a built-in browser, tapping a link may launch a separate browser, interrupt the app, and make users switch back and forth. Many people find that disruptive, so companies use an embedded browser to keep the whole interaction in one place.
Reply to this answer
For some companies, the embedded page is not just a convenience featureโit is part of the product funnel. Keeping you inside the app makes it easier to guide you toward more content, ads, purchases, or other actions instead of sending you into a separate app where the original company has less visibility.
Reply to this answer
Built-in browsers let apps preserve the session and bring you back to the app when you finish. They can also apply their own navigation controls, authentication flow, and tracking without depending on whichever browser the user prefers. The downside is exactly what you described: separate logins, poor history support, lost state, and broken deep links.
Reply to this answer
The biggest reason is control and retention. Keeping the link inside the app means users are less likely to switch away, and the company can measure what pages they open, how long they stay, and what they click. It also keeps the experience visually tied to the app and can support more advertising or analytics.
signed.in.blue: That probably explains why the pattern survives even though it creates so much friction. The engagement numbers must look better than the user experience feels.
Reply to this answer
Add your answer
Answers are reviewed before publication.
dusk patrol: That makes sense for quick pages, but it would be much better if the embedded view also offered an easy โopen in browserโ or โopen in appโ option.