Syncing with Google Contacts

[Androz2091]

Description / 功能描述

Hi, do you have any idea about how I can sync bonds with Google Contacts? I probably want bi-directional syncing which might be a bit tricky to get.. How would you approach this?

Motivation / 动机

No response

Proposed Solution / 建议方案

No response

Alternatives Considered / 备选方案

No response

Additional Context / 补充信息

No response

[naiba]

For Google Contacts, I would not start with a custom Google-only sync engine if we can avoid it. Bonds already has CardDAV support, so the safest first question is whether Google Contacts can be bridged through a CardDAV-compatible path for the user's setup. If direct Google integration is still needed, I would design it as a separate sync connector with explicit conflict handling rather than mixing it into normal contact CRUD.\n\nThe hard parts to decide before implementation are:\n\n- Identity matching: Google resource name / etag vs Bonds contact id / vCard uid.\n- Direction: one-way import, one-way export, or true bidirectional sync.\n- Conflict policy: last-write-wins, manual review, or per-field merge.\n- Scope of fields: start with names/emails/phones/photos/addresses before relationships or Bonds-specific metadata.\n- OAuth/storage: token encryption, revocation, and per-vault configuration.\n\nMy recommendation is to first implement a conservative connector: per-vault opt-in, explicit dry-run/preview, basic fields only, then add bidirectional writes after the conflict model is clear.