3 ms·
Android solved that UX issue with Chrome custom tabs (https://developer.chrome.com/multidevice/android/customtabs https://developer.chrome.com/multidevice/andro
by giulianoxt 10y ago
Android solved that UX issue with Chrome custom tabs (https://developer.chrome.com/multidevice/android/customtabs https://developer.chrome.com/multidevice/android/customtabs). It uses a seamless UI exiting the app and everyone uses the up to date browser on the phone.
- geekrax 10y agoiOS also provides a way to have similar UX using Safari View Controller. https://developer.apple.com/videos/play/wwdc2015/504/ https://developer.apple.com/videos/play/wwdc2015/504/
- tehlike 10y agothere are problems with both, though. i like to click on something and then give a break, and read later. with CCT, I have to consciously go and click on "open in browser", which doesn't work well for me. Otherwise, CCT and SVC should be the way to go, still much better than FB. Aside from tracking and all, it doesn't get the niceties of a full blown browser.
- saagarjha 10y agoiOS has Reading List for this purpose, and SFSafariViewController has a button dedicated for this.
- untog 10y agoI only know detail about the iOS equivalent (https://developer.apple.com/reference/safariservices/sfsafariviewcontroller https://developer.apple.com/reference/safariservices/sfsafar...) but I'm not expecting Facebook to implement it any time soon as it makes it a lot harder to track where a user goes (you can't access that) and/or inject content into the webview. On the current Android and iOS implementations a user is far less likely to share on, say, Twitter, because they won't have their Twitter login cookies in the Facebook browser. I suspect Facebook is quite happy to keep things that way.
- zeveb 10y agoAndroid also supports a real Firefox, so one needn't trust one's web browsing to the tender mercies of Google.