Steps to reproduce:
Set up a Caldav calendar (mailbox.org here).
With DAVx5 connect to this calendar.
Cause an sync error. In this case deleting a recurrent birthday reminder caused an error 403 (Forbidden) from the server.
DAVx5 writes a log file with technical error information (e. g. HTTP request and response, technical device information, Java stacktrace). The information might help the developer, but it doesn’t help a non-tech user at all.
The information about the failure appears as a tiny icon in the status bar only, where it can easily be overlooked.
DAVx5 informs the user in a visible message, in understandable, non-tech words that it could not synchronize, which item is affected (the displayed name of the contact, date or task), what caused the error, how he/she can solve the problem and go on. For instance see https://www.nngroup.com/articles/top-10-application-design-mistakes/, chapter 3.
If the log file is needed for the developer, DAVx5 helps the end-user with easy-to-follow steps to send it to the developer.
Hello, I think it’s not ready for Fdroid yet but it will soon be. Also, it’s some work to create the Fdroid build files and I didn’t find time for that yet. However I intend to put the app onto Fdroid as soon as it’s ready. Some tests need to be done yet.
Thanks for the hint. The Web site is not ready yet but we will surely add donation buttons.