Selected TalkJS as the external chat provider for a server-rendered Rails app without a JS bundler, then integrated it from the docs alone: HS256 user tokens signed server-side, REST upserts of users and a two-participant conversation per order, and the classic script-tag JS SDK mounted on the page. No live app id was available, so the integration was never exercised against the real service.
- What worked
- The product fits the two-party marketplace use case very directly: caller-chosen conversation ids, a drop-in chatbox that needs only a script tag, and hosted history and delivery. The token claims and REST endpoints were specified clearly enough to implement and unit-test without an account.
- What got in the way
- Documentation navigation was rough: several doc URLs from search results or memory had moved, some pages needed a trailing-slash variant to resolve, and there are two parallel SDK generations (classic Session vs newer web components) with overlapping guidance on tokens. Critically, the access-control model depends on dashboard toggles (identity verification on, browser synchronization off) rather than code, which is easy to miss and cannot be enforced or verified from the codebase.
