1

In many (mostly iOS/Android) native apps, when you press a link, it opens within an embedded browser within the app. However, some apps don't do this and instead open directly within the operating system's default browser.

Almost always, desktop native apps seem to open links in the OS browser.

When should you choose to use one method over the other?

Example of Instagram's in-app browser:

An add in the Instagram feed The in-app browser that opens when following the ad link

2 Answers 2

1

Meta's decision to open links in an embedded browser is because of their global feature link feature that allows you to save links you click on, as well as view your overall link history. They likely do that as Instagram is also seen as a commerce platform. They want you to stay in the app.

My initial thought is to say that it depends on the experience you want to provide and the type of content that would link out to (or in).

Do you want to "control" the user's experience within the app? An in-app browser gives you the control to ensure that you're preventing users from navigating to websites outside of your app. (However, the case for Instagram, it also gives you the option to view the page with the native browser).

Are you collecting personal data? I would suggest opening up in a native browser as there's more security built in.

And, in terms of preference, would having to load the native browser hinder the experience, or do you want to create one that is more fluid?

1
  • 1
    Interesting thoughts. This app in particular is not collecting any data. It's focused on emergency communications and sometimes those messages will link out to external (web) resources. My personal opinion is that we should open in the native browser to give the user the best browsing experience, and they can return to the app through their OS to continue browsing in the app. Commented Feb 4 at 16:05
0

In app browsers generally provide worse UX than the user's system browser. This is for many reasons, including:

  • Limitting user choice
  • Limits of functionality
  • Secuirty risks
  • Privacy errosion

In many cases, companies utilize in-app browsers to track users and keep them from leaving their app/platform. Those reasons give to a bad UX, but are influences on why one would chosoe to implement an in-app browser.

Some UX driven reasons for implementing an in app browser:

  • Users of your app will frequently be clicking on links to view some content and return back to the app
    • Examples: email client, browsing social media
  • Your need to have the user jump out of the app into a web-bassed application for some actions
    • Examples: web-based forms that cannot be integrated natively

In any case, you should how users will be using your app, and if adding an additional step to accessing within their native browser will cause friction for the regular usage of your application.

Source: Digital Markets Act - Interventions - In-App Browsers (Open Web Advocacy, 2024)

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.