Conversations & Notes
Chat Record API: Messages, History, and Sync
Keep message identities, edits, replies, attachments, and reconnects aligned with the conversation people actually had.
Read guide →FOCUS / FIELD NOTES
Synchronization.
Design reconnects and revisions without silent data loss.
Synchronization is easier to reason about when every client knows which state it last observed. Chat histories need event identity and repeatable delivery; notes need a revision-aware save contract and a recovery path for conflicts. These guides focus on preserving work rather than hiding every disagreement automatically. Test with two devices, delayed events, and content changing during pagination. An honest conflict state is preferable to a silent overwrite that leaves people unable to explain what disappeared.
Read this focus across workflows.
Conversations & Notes
Note Taking Record API: Revisions, Sync, and Export
Protect the relationship between a draft and its accepted revision, from offline saves to linked media and portable exports.
Read guide →