A while back Facebook integrated a so-called internal or in-app browser into its mobile apps. The ideas is that when you click to see a website that somebody has shared on Facebook, instead of being taken out of the Facebook environment, the app would display the relevant page within its own browser.
The main reason they gave for doing this is that it’s faster. It’s true – they can even cache a page ahead of you clicking on it.
But I hated it.
First of all, the real reason for embedding your own browser into your app, is to increase dwell time. The app maker is worried that if someone shares, say, a Buzzfeed link, you’ll just end up reading more Buzzfeed stories, and not return to the social media app you’d started in.
This is true. But I’m an intelligent human being. Let me choose whether to return to the app I started in, or continue using the link ecology that makes the web so fascinating – and so open.
Other reasons for wanting not to use internal browsers include cookies (I have to log in again on sites like Amazon or the New York Times), and the inability to use bookmarks or other browser functionality. I regularly like to use Recent Tabs in Chrome to, say, read on a laptop, a long story that I opened in Chrome on my mobile.
It also denies other app users the ability to launch a page in their app – when I click on a Guardian story, I might prefer to see it in the Guardian app. Aside from anything else, the top banner on the story will end up being a promotional ad for said app.
Internal browsers also tend to eat screen real estate, something that’s important in mobile where every pixel counts.
This added “functionality” also tends to increase the overall size of apps. Not something you might worry about if you’re using a 32GB+ top of the range smartphone. But bear a thought for the vast majority of the world on inferior devices.
When Facebook introduced their internal browser, they did at least include a way to turn it off. It was just about the first thing I did when they installed it.
(Later I stopped using the Facebook app altogether when they started pulling it apart and insisting that I install their Messenger app. I don’t want another messaging app thanks. Your old app was fine for my purposes.)
This is all a roundabout way of noting that Twitter has recently added its own internal browser. Now I should note that I’m on an Android beta stream (Ver 5.48.0-beta.267), so it’s possible that you’ve not seen this. But the app version I’m using does not have the ability to switch off the internal browser (or if it does, it’s seriously well hidden, because believe me, I’ve looked).
Sure – I can launch the resulting internal browser page in my preferred Chrome browser. But that’s an extra couple of button presses – Menu > Open in Browser.
Look – I understand that social media companies like Twitter want to get me to spend more time in their ecosystem. But this is actively driving me away from their browser. If they don’t add a way to switch this “functionality” off, I’ll have to move to a third-party app altogether.
Please do the right thing Twitter, and let me switch off your internal browser.[Update – March 10 2015] The latest Twitter beta has a setting to let you switch off its internal browser. Hurrah!
(Sadly, actually writing a Tweet requires 1-2 more button presses which seems odd)