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.

Источник