Caldav is broken

CalDAV implementation on Jolla is broken in a number of ways, and don't let me started over CardDAV! Trouble is, Jolla doesn't care, it's never been a priority for them and, as far as I understand, also for the vast majority of users. This sucks.

Not sure that's very accurate. Chris has been updating things pretty regularly over the past few months, and both CalDAV and CardDAV are in a workable state when used with ownCloud, after he implemented several things suggested on this forum.

These protocols are very complicated, and coping with the variation between different servers makes them even more so. Reporting bugs on here is the best way to help this improve, but if you really want to make a difference you could contribute directly to the open source project on github instead of questioning the developers commitment.

Jolla DID listen to customers, and later started to implement CalDAV and CardDAV. It's know to be experimental release, so I really have no expectations :P

By management do you mean server side web app r something? If you do, I think it means that the birthday calendar is another calendar, so you could setup another CalDAV account in Jolla for it...just a thought.

PS I'm suffering from double DST correction, so, yeah. Otherwise it eorks for me.

@Andy Branson@Direc I have nothing against @chris.adams (he's been helpful to me), rather against Jolla's management in setting priorities and allocating resources. Yeah, armchair CEO and all that, I know.

Nevertheless, paraphrasing Agent Smith: "what good is a smartphone if you're unable to sync?".

Heck, on Android there's several third-party *DAV implementations and they work with any server, not just ownCloud!

@IZ1IVA I get what you're saying, but it's a sad fact that Jolla is still a startup, with limited resources and great pressure to make themselves sustainable before the money runs out. They've already managed to get Sailfish to a greater level of maturity than Android did in the same amount of time, and that's with the support and feedback that we've been giving them. It might seem like they're ignoring stuff, but time and time again we've seen a major issue crop up that's the end of the world for someone or other, which sometimes takes a while to get fixed but they eventually get around to, but often doesn't even get acknowledged on here as we move on to the next showstopper.

It's rare that device manufacturers give consumers the opportunity to discuss things so frankly on an official public forum, much less pay any attention to it and even more rarely actually act on its context. If this community goes toxic, we'll lose that. And I'm not sure we'll get it again.