Of course these URLs are “well known” (to you and me). For non tech-savy people it might be a different story.
If you’re able to set up your own OwnCloud instance, you’re also able to set up well-known URLs. They’re just a redirection, this is one or two lines in your Web server config and it’s even mentioned in the OwnCloud docs.
Apart from that, comfort would be much increased if you don’t have to lookup these URLs and type in by hand (on a tiny smartphone!) something like https://demo.ownlcoud.org/remote.php/caldav/calendars/demo/personal.
With well-known URLs, you only have to enter your host name.
You may also use the “Login with email” option: DAVdroid will then detect the host name from the email address domain and use the email address as user name.
So why not giving users this extra comfort? Does your answer mean you would decline a pull request if I provide this?
DAVdroid won’t use provider-specific settings. That would mean to have a database of providers and URLs and keep it up-to-date. Also, it’s an error-prone approach because who says that you can’t have a prefix for your OwnCloud installation or rename
remote.php and what to do when the next OwnCloud version uses another path? Also, there are hundreds of different servers and services and keeping an up-to-date “path database” would be a very time consuming task.
I think the solution for dealing with complicated paths is support of well-known paths, so please don’t submit a pull request for that.