Anytype doesn’t have the facilities that a proper calendar app might have.
For the second one, I’m very excited that Anytype will support databases with (i) people and (ii) date relations. However, these will not be as useful as they could be if they are sequestered in the Anytype app.
Describe the solution you’d like
As part of this feature, objects in Anytype sets would show up in the phone’s contact list or calendar, as appropriate.
A user could choose various sets to show up as calendars or contact groups, and possibly the mapping between relations and vcard/icalendar properties.
Possibly, the user could even edit the sets using a contacts or calendar app.
Additional context
The best example of a sync provider is probably [DAVx5](https://www.davx5.com/), which syncs with a CalDAV/CardDAV server (I’ve tried hosting one and it works, but Anytype is far more accessible and doesn’t require maintenance)
My business is currently looking into professional indemnity insurance for cyber and data risk. Being able to say that our contacts data are never stored on 3rd party servers would probably reduce our premium.
I like this idea as well. Would be great to store my contacts in one place where I also can link them to other objects.
I think this is broader than just Android. If anytype would act as a server, it will be available to all platforms/apps that support CalDAV/CardDAV.
I landed here when searching for any possibility of sync’ing Android’s contacts with contact objects in AnyType. Any discussions or plans about this happening now?
Well idk if webdav would break anytypes sync protocol and just make conflicts at one point. There’s a solution already but its not easy to maintain. Truly wish prebuild anytype images one day without rebuilding each time an update comes.
AnyType could implement the Content Provider, so that it shows as another Calendar or Contacts provider. Then, in apps that list these (calendar, address book), you would see AnyType as a book/collection/source. This might be read-only or read/write, editing directly the objects in AnyType.
However, this is significantly different to synchronizing via DAV or doing other transformations, I think. That part is a whole another ballgame. And there’s probably no need for that in the app directly. With the AT API, you can create and expose a Cal/Card-DAV server and use AnyType instance as the storage mechanism.
