{"push_id":886816938,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a464ff40445d1b1c1b1aaa265f9d43748a99f8db","before":"53ab108d568578747f032563e668e87773f037a4","commits":[{"sha":"a464ff40445d1b1c1b1aaa265f9d43748a99f8db","author":{"email":"3926a507e07fbdb272d52aaae15787b434a8f695@users.noreply.github.com","name":"Solomon Bier"},"message":"Remove Default Safari View Controller\n\nDespite Facebook's internal team's internal testing showing that the Safari View Controller method is more user friendly, developers are seeing otherwise in a massive drop-off in sign-up rates. First, the additional alerts switching back and forth presents much less friction than having to retype your password on a safari modal. Facebook may see on a large scale more users are using Safari than native app (I'd be surprised), the users who are downloading most apps are more likely to be logged in via a native app. Many users use the Facebook so much that they haven't typed their passwords in ages. Facebook has also claimed that after the first time that users type in their password, the friction will decrease as the session is stored, but we are seeing that this session storage in unreliable. Even getting a user to sign in that very first time is enough to cause abandonment. Please see the negative feedback from developers here: \r\n\r\n`http://stackoverflow.com/questions/32566734/native-facebook-app-does-not-open-with-facebook-login-in-ios-9`\r\n\r\nWhile the graph api is great, the most important feature is a frictionless sign up process. This is more important than the extra features of the graph-api, would can not even be used if a user abandons an app. Please reconsider Facebook !","distinct":true,"url":"https://api.github.com/repos/SolomonBier/facebook-ios-sdk/commits/a464ff40445d1b1c1b1aaa265f9d43748a99f8db"}]}