Closed elgrangrifon45 closed 9 years ago
Maybe we need to be more specific about catching the type of authentication error (EntryPoint errorHandlerUser line 115) , so we can handle this properly. If no connection, then a helpful modal dialog with a retry button. If connection ok but authentication could not be done, then the signup screen.
What do you think of a flow like this?
Looks good. I think that should work...
On 27 Oct 2014 19:52, "elgrangrifon45" notifications@github.com wrote:
What do you think of a flow like this?
[image: moodsstartup] https://cloud.githubusercontent.com/assets/8495210/4797260/48e81638-5e0a-11e4-9575-0af579ede9c8.jpg
— Reply to this email directly or view it on GitHub https://github.com/ERNICommunity/erni-moods-android/issues/17#issuecomment-60648734 .
Implemented.
At application Startup, the app checks against the backend, whether the user stored in the preferences exists. If the user doesn't exist, the app Redirects to the sign-up Screen.
However, if there is no connecetion available, the app can't authenticate. We don't know whether the user is registered or not. What Fragment/Screen shall be displayed then?
Can we design a Startup Screen? There might also be a button Retry, in case authentication could not be performed.