Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

We built four chats. Obviously, that was the sensible thing to do.

说明与用途

创建了一个统一的聊天组件,分享核心逻辑,让每个主机应用定义自己的行为,消除了代码重复。

问题

Multiple parallel projects required similar chat functionality, leading to four separate chat implementations with duplicated effort.

结果

Unified chat component reduced duplication, streamlined maintenance, and allowed each application to customize behavior while sharing core functionality.

工作流

  • Identify common chat requirements across projects.
  • Extract shared UI and API logic into a standalone chat engine.
  • Expose configuration options for host-specific behavior (FAQ, live data, actions).
  • Embed the chat via a script tag with project ID and public key.
  • Host applications implement callbacks for domain logic (booking, support).
  • Iterate improvements across all projects through the shared component.

证据

We had a problem with our hotel websites: tourists were having to navigate them.

来源

We were also building a taxi service. Passengers needed a way to talk to drivers.

来源

Four chats. Each one better than the other three. Naturally.

来源

We pulled the shared parts behind one embeddable interface.

来源

The host application still owns its data, business rules and decisions.

来源

  • 记录日期: 2026-10-17T15:56:18.395Z