While CardDAV works for syncing accounts in both ways, CardDAV is inherently client-dependent and introduces additional overhead (local account configuration, local client-side syncing etc.).
The discontinued one-way sync via direct Google Contacts integration offered cleaner cloud-based approach. It reduced reliance on local clients and provided a seamless way to treat Dex as the single source of truth for contacts.
Reinstating the direct Google Contacts one-way sync as an option alongside CardDAV would give users flexibility:
Those preferring cloud-based sync could rely on Google Contacts integration as a one-way sync
Those requiring two-way sync could continue to use CardDAV
Please authenticate to join the conversation.
Open
Feature Request
6 months ago

Jason Haak
Get notified by email when there are changes.
Open
Feature Request
6 months ago

Jason Haak
Get notified by email when there are changes.