Comments on: The Pitfalls of In-App Browsers https://frontendmasters.com/blog/the-pitfalls-of-in-app-browsers/ Helping Your Journey to Senior Developer Tue, 14 Jan 2025 23:15:30 +0000 hourly 1 https://wordpress.org/?v=6.8.3 By: Shalanah Dawson https://frontendmasters.com/blog/the-pitfalls-of-in-app-browsers/#comment-19460 Tue, 14 Jan 2025 23:15:30 +0000 https://frontendmasters.com/blog/?p=3008#comment-19460 In reply to Yzb.

The “getallmylinks” is fascinating. I think they make it work by having android + iOS apps so they can make deep links work with registered apps with a fallback url and they must parse the UA server side. It’s kind of ridiculous that a seamless exit from in-app would need all that work (if you don’t want a popup asking the user if they want to leave the app) — but that’s what it takes. I don’t think exiting in-app browsers to a default browser should involve creating 2 native apps and server side scripting!

]]> By: Yzb https://frontendmasters.com/blog/the-pitfalls-of-in-app-browsers/#comment-10316 Fri, 23 Aug 2024 20:21:51 +0000 https://frontendmasters.com/blog/?p=3008#comment-10316 Exists a couple of sites that has done a good job avoiding in-app browsers, the best that I found, is “getallmylinks”

Maybe this works as an example to understand how they did it. Anyways, thanks for the analysis and explanations.

]]> By: Olivier https://frontendmasters.com/blog/the-pitfalls-of-in-app-browsers/#comment-7877 Wed, 24 Jul 2024 16:49:47 +0000 https://frontendmasters.com/blog/?p=3008#comment-7877 Displaying external sites is not AFAIK the intended use of in-app browsers. Instead they exist to allow developers to author some or even all pages of their app as web pages seamlessly integrated with the rest of the application. That is a perfectly valid use that is not going away.

]]>