-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement error handling & empty-states #4
Comments
luhmann
changed the title
Implement error handling
Implement error handling & empty-states
Sep 15, 2017
luhmann
added a commit
that referenced
this issue
Sep 15, 2017
* should now provide a better experience during loading for #4
luhmann
added a commit
that referenced
this issue
Sep 16, 2017
Adresses #4 * Add component to display error-messages * Add generalized error-handling for failing requests * Add ability to use a local mock-server for greater control
luhmann
added a commit
that referenced
this issue
Sep 17, 2017
Show a message to the user in case he should really never have listened to a single track on spotify. #4
All issues besides handling of the user being offline has been adressed. Offline-Behavior will be adressed with #10. Closing for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is no error-handling when the backend returns an error or the app crashes.
The user should see as message aplogizing and providing some feedback of what he can do.
Also the user might be offline implement a screen to inform him that no connection could be established and he should be patient.
Also while not strictly an error, it is a possibility that the user does not have any recent songs, for example if he just signed up. She should see an encouraging method to start listening and explain that through this songs will start to show up.
The text was updated successfully, but these errors were encountered: