Hey folks, developer here, just wanting to chime in on a couple things.
1. First of all thanks for all of the solid and constructive feedback you've given so far. We've already identified a number of issues and fixed them here. A new beta version is due to be released today or tomorrow with many of the fixes
It's really helpful to receive detailed and accurate accounts of how to reproduce any issues you come across. Thanks for that!
2. There's a bit of discussion about the social login. These days, most users will have one of the 4 options provided. One of the main reasons we didn't elect to do a user name and password is simply because it's actually less secure to do that. It would mean we would have to store your username and a one way hash of your password on our servers.
Considering how many people use the same password for multiple services, there's an added liability on us if we store your passwords that I'd rather avoid. I won't get into details about how OAUTH2 works exactly, but basically now if your social 'token' gets exposed from our servers (which are hosted securely in Azure by the way), the worst someone could do with it is see your name and email address. We don't collect any personal information other than storing your email address locally on your device so that we can display it in the top left corner of the slide out menu in the app. That's it.
Implementing social authentication was actually MUCH more effort from a development perspective for me than implementing a simple username and password. I would rather have avoided that effort, but I don't think that would have been the right decision.
Eventually we may add the ability to login with your TFP forum account, but there's quite a bit of effort involved in making the app talk with the forum securely to do so. Also, that would mean anyone who wants to use the app would require a TFP account, which not everyone will (many users will download the app from the store without having heard of TFP - until they try it out and find out how great a resource it is!).
We require authentication in the app so that your pool data can be sync'd and saved to the cloud. We decided the workflow was too messy and would create a poor user experience if we wanted to allow local device storage only until a user logged in after that.
Hope that clears up the decision to use social auth!
Again thanks for all the feedback and keep it coming!
