It’s always a terrible experience too. I’m never logged in, my password management app doesn’t work, and if I do want to login it’s a new browser so it trips all the security.
Let websites framebust out of native apps
81–90 of 158 posts
Re: Let websites framebust out of native apps
#82[deleted]
Re: Let websites framebust out of native apps
#83Earlier quoted context omitted.
Came here to say this. Custom webviews like Facebook likes to use are another matter but SFSafariViewController is for all intents and purposes real Safari with per-app cookies, storage, etc to bust tracking. And I have to say, I would be pretty irritated if every site demanded to open in my main browser. Many if not most links I tap are quick one and dones I’d prefer to not clutter up my tabs.
Perhaps it can be an option to check: "Always open websites in your default browser".
Many apps have this setting but some don't. When they do it is invariably buried in the most inconvenient and hard to find place, different in every app, named something non-obvious, moved every year or so when some PM decides that the settings screen needs rearranging, and it is never synced or saved so you have to set it separately on every device and again whenever you get a new device, in every app.
I wish there was an OS level setting.
Re: Let websites framebust out of native apps
#84I feel like I am in the extreme minority in that I pretty much never use an app for anything that already has a website. I just use the website on my phone. The experience might be slightly worse, but I much prefer just staying in the browser on my phone for everything. Reddit, Twitter, the few times I log into Facebook, are all just using a browser. I just find it simpler, and I like when the interface is the same o…
Tabs, extensions, bookmarks, and sharable URLs are so very nice, and so few apps implement them. Browsers are great.
Re: Let websites framebust out of native apps
#85Yes 10000x I hear insta engineers happily proclaim Instagram is one of the most popular web browsers :/
Re: Let websites framebust out of native apps
#86protip for gmail on android users: gmail -> settings -> general settings -> open web links in gmail -> uncheck
Re: Let websites framebust out of native apps
#87Earlier quoted context omitted.
Perhaps it can be an option to check: "Always open websites in your default browser".
Funny thing - the Gmail app has this prompt on the iPhone buy it never remembers my preference. It asks me every time even when I tell it not to.
If it’s like the one in Google Maps, it’s just an ad for Chrome. Chrome shows in the list whether or not it’s installed, with an option to get it from the App Store.
Re: Let websites framebust out of native apps
#88Some apps lack this setting, whereas many do. Funny thing is that the Gmail programme on the iPhone offers this prompt, but it never saves my preference. I'd be amazed if a native app couldn't strip the header if it had as much control over the webpage as it appears to have. Alternately, you might use a proxy that removes it and ignore the resulting HTTPS problems.
Re: Let websites framebust out of native apps
#89I feel like I am in the extreme minority in that I pretty much never use an app for anything that already has a website. I just use the website on my phone. The experience might be slightly worse, but I much prefer just staying in the browser on my phone for everything. Reddit, Twitter, the few times I log into Facebook, are all just using a browser. I just find it simpler, and I like when the interface is the same o…
I'm with you also. But it is getting harder and harder. I'm convinced that Facebook are actively downgrading their in-browser mobile experience for this reason. They want to force you to use their app. Reddit, at least, are more honest about it - but also very annoying.
Features that used to work just fine (tagging people, editing comments) are becoming worse.
Re: Let websites framebust out of native apps
#90I think the proposal of piggybacking on X-Frame-Options as expressed is just a smidgeon too coarse, and it needs a little more nuance.
My suggestion would be that web views that aren’t deliberately being an actual browser be classified as possessing some origin, preferably checked where possible by the OS to match an origin or custom scheme that’s associated with the app (thus generally tying into Android’s app links and iOS’s universal links). Of course, this is still technically fallible since browsers need to be able to disable it, so it’d become another thing for the app store reviewers to check.
Then, you apply your Content-Security-Policy’s frame-ancestors directive (the successor to X-Frame-Options, allowing more nuance than simple DENY/SAMEORIGIN: e.g. `Content-Security-Policy: frame-ancestors 'self' instagram:` would be same-origin or the Instagram app), and treat deny as “open in an external browser”, as proposed.