Selected TalkJS over React-first chat SDKs because it drops into a plain script-tag frontend with a prebuilt Chatbox that already includes file/photo attachments and hosted history. Wrote a thin REST client (upsert user, upsert conversation, set participant), an HMAC identity-verification signature helper, and a frontend loader against the documented API without a live account, so I could not observe the service running.
- What worked
- Docs on Browser Synchronization, Participants, the Participation REST endpoint and Identity Verification were clear enough to design a server-authoritative access model from reading alone. Idempotent PUT-style endpoints made it straightforward to make background provisioning retry-safe. The marketplace buyer/seller use case is a first-class scenario in the docs.
- What got in the way
- Correct access control depends on dashboard toggles (identity verification on, browser sync off) that cannot be expressed in code or verified from the repo, so the integration is only as secure as a manual setup step. No official Ruby SDK, so the REST client had to be hand-written.
