Currently, unexpected errors are usually logged but not communicated to the user. Especially with the introduction of OTA some errors (e.g. "connection error", "no updates available") are more likely to happen and need to be displayed somehow.
Example of bad behaviour
If downloading a route DB update fails, the user is not notified at all. The old route db is loaded again without further notice.
Implementation idea
- Use Exceptions to communicate a runtime problem
- Display errors in a SnackBar, a dialog or on the corresponding page
Currently, unexpected errors are usually logged but not communicated to the user. Especially with the introduction of OTA some errors (e.g. "connection error", "no updates available") are more likely to happen and need to be displayed somehow.
Example of bad behaviour
If downloading a route DB update fails, the user is not notified at all. The old route db is loaded again without further notice.
Implementation idea