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.
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.
EDIT - (thanks saagarjha) newer versions of Tweetbot appear to use SFSafariViewController not WKWebView.
* UIWebView: Old, slow, but dead simple.
* WKWebView: The new "WebKit" drop-in replacement for UIWebView. It uses Safari's Nitro engine, and allows for full customization for the chrome, but does not allow for content blocking. Most new apps use this.
* SFSafariViewController: A "Safari view"; you have no control over the UI chrome (or browsing history, etc.), but it uses Nitro and loads content blockers.
* Safari app: The actual app. Loads content blockers.
Or are apps generally switching over to SFSafariViewController? Curious to hear some iOS folks' thoughts on the matter since I'm uninformed.
SFSafariViewController provides its own Safari-like interface and has an extremely limited set of configuration/customization options.
While I am all for escaping the "black box" that is Facebook's in-app browser due to our inability to see what they are loading/tracking on the backend, that likely won't happen until people stop using Facebook all together, as it is more convenient for the everyday user. Simply put, Facebook's in-app browser creates less visual noise than a link opening externally in Safari (where there is often the animation of a new tab being created). This ignores the fact, however, that Facebook requires this behavior and thus I cannot be sure that my above statement "everyday people prefer a more convenient / less UX noisy solution" holds true.