Requested again via support. A returning customer keeps a single address book shared between Google Contacts and iCloud through a third-party sync utility, and wants Dex to participate in that loop rather than sit beside it. Today the two-way sync reaches the device's own address book over CardDAV, so Google Contacts is only ever touched indirectly, via whatever the device happens to be syncing. The ask is a direct Dex to Google Contacts two-way sync so edits made in either place converge without a device in the middle.
Dex Operations
Team•
Sep 15
Raised again by a customer who treats Google Contacts as what their phone and their email client actually read from. Contacts do not flow from Dex back into Google today, so Dex could not act as the place they manage their contact list from.
Worth noting for anyone arriving here from the CardDAV request: the two-way CardDAV sync does not cover this case. It pairs Dex with a device address book rather than with a Google account.
Dex Operations
Team•
Aug 31
Another request in from support. The customer keeps their primary address book in Google Contacts and connected a Google account to Dex expecting edits to flow both ways, so that a change made in Dex reaches Google Contacts and a change made in Google Contacts reaches Dex. Today the Google connection reads only, and the two-way path runs through CardDAV against the device's own address book, which does not cover their case.
Dex Operations
Team•
Aug 24
Requested again by a customer who has been using the CardDAV two-way sync and assumed it also kept his Google Contacts account in sync. His use case is having edits made in Dex flow back into his Google Contacts directly, rather than only into a separate Dex account added on his devices.
Nicolas Kammerdiener
•
Jul 9
This would really help to solve a lot of Google Voice on the desktop as well.
Log in to comment and vote
Comments6
Dex Operations
Sep 18
Requested again via support. A returning customer keeps a single address book shared between Google Contacts and iCloud through a third-party sync utility, and wants Dex to participate in that loop rather than sit beside it. Today the two-way sync reaches the device's own address book over CardDAV, so Google Contacts is only ever touched indirectly, via whatever the device happens to be syncing. The ask is a direct Dex to Google Contacts two-way sync so edits made in either place converge without a device in the middle.
Dex Operations
Sep 15
Raised again by a customer who treats Google Contacts as what their phone and their email client actually read from. Contacts do not flow from Dex back into Google today, so Dex could not act as the place they manage their contact list from.
Worth noting for anyone arriving here from the CardDAV request: the two-way CardDAV sync does not cover this case. It pairs Dex with a device address book rather than with a Google account.
Dex Operations
Aug 31
Another request in from support. The customer keeps their primary address book in Google Contacts and connected a Google account to Dex expecting edits to flow both ways, so that a change made in Dex reaches Google Contacts and a change made in Google Contacts reaches Dex. Today the Google connection reads only, and the two-way path runs through CardDAV against the device's own address book, which does not cover their case.
Dex Operations
Aug 24
Nicolas Kammerdiener
Jul 9
This would really help to solve a lot of Google Voice on the desktop as well.
Mitchell Starrenburg
Apr 26
Seconded. Using a DAV app on my phone is a clumsy workaround when Google has a RESTful CardDAV protocol: https://developers.google.com/people/carddav