xPulse Chat – Roadmap

As of: March 2026 Companion documents: TOOL_chat_concept-ui-layout.md, MAIN_roadmap-ecosystem.md

Version Overview

1
v1.2.0  Bug fixes, performance, pairing UI                       [LIVE]
2
v1.3.0  UI/CSS refactoring + app shell layout                    [PROGRESS|TESTING]
3
v1.4.0  Components + i18n (de/en)                                [PLANNED]
4
v1.5.0  Themes (dark/light)                                      [PLANNED]
5
v1.6.0  Profile features + avatar + chat images                  [PLANNED]
6
v1.7.0  Emojis, stickers, GIFs                                   [PLANNED]
7
v1.8.0  Chat history paging (lazy render, local)                 [PLANNED]
8
v1.9.0  Peer sync (history + profile via DataChannel)            [PLANNED]
9
v2.0.0  Abrax – AI assistant via @xpulse/ai                     [PLANNED]

v1.3.0 – App Shell + Landing Page + Project Foundation

Status: PROGRESS · Staging: rc-1-3-0.stage.xpulse.one

UI/UX

• App shell with CSS Grid (layout-shell / layout-fullscreen)
• Left sidebar – peer list, [+] button, footer with toggle, version pill
• Top bar – hamburger, title, status dot, user menu
• CSS extracted: base.css, components.css, layout.css, views/*.css
• Router: routeShell, routeShellParam, routeFullscreen
• Mobile sidebar as overlay with backdrop
• Chat landing page chat.xpulse.one/ – live on Stage RC-v1.3.0

Project Foundation

• Integrate xpulse-chat-logo.svg in sidebar (replaces "xPulse" text)
• Integrate xpulse-chat-logo.svg in feedback form
• Create xpulse.json in repo root (name + type set)
• Create docs/ base structure (index.md, de/index.md, en/index.md, de/adr/) – not yet in repo root, only on RC branch

v1.4.0 – Components + i18n

Status: PLANNED Prerequisite: Verdaccio running, @xpulse/theme + @xpulse/theme available

Extraction

• Integrate @xpulse/theme (replaces local base.css + components.css)
• Integrate @xpulse/theme (colours + effects extracted from @xpulse/theme)
• Integrate @xpulse/logger (replaces modules/logger.js)
• Integrate @xpulse/crypto (replaces crypto.js)
• Integrate @xpulse/session (replaces session.js)
• Integrate @xpulse/notify (replaces modules/notify.js)
• Integrate @xpulse/presence (replaces modules/presence.js)

i18n

• Integrate @xpulse/i18n
• German / English
• Move all UI strings out of code into src/translations/
• Language selection in profile or settings

Feedback

• Feedback link in sidebar footer (Info · Guidelines · Feedback)
• Modal with feedback / bug report via mailto:

Docs

• Fully develop docs/ (guide, security, changelog)
• Create CHAT-001 ff. ADRs
• Fully develop docs/ incl. de/ + en/ subdirectories (no _meta.json – navigation via structure + TOC)

v1.5.0 – Themes

• Dark/light theme toggle
• Theme encapsulable via @xpulse/theme
• User preference in localStorage

v1.6.0 – Profile Features + Avatar + Chat Images

• Avatar (initials or upload)
• Display name (independent of login)
• Send images via DataChannel
• IndexedDB as local cache for images

v1.7.0 – Emojis, Stickers, GIFs

• Emoji picker
• Sticker support
• GIF integration (TBD: source)

v1.8.0 – Chat History Paging

Prerequisite: v1.6.0 completed (IndexedDB)

Lazy rendering of chat history: initially only the last 50 messages are rendered. Older messages can be loaded via button (50 at a time, cursor-based via timestamp). All data comes from local storage – no network required.

Features

• loadChatHistory receives limit + before parameters (cursor)
• Initial: last 50 messages
• "Load older messages" button at the top of #chat-messages
• Prepend + maintain scroll position (scrollTop += newHeight - oldHeight)
• Button disappears when no more messages are available

v1.9.0 – Peer Sync

Version: v1.9.0 (after v1.6.0 – IndexedDB prerequisite for image sync)

Problem

Chat history and profile data currently only exist locally in localStorage (via session.js). If Peer A writes a new message while Peer B is offline, that message is gone for B forever. Similarly, B always only sees A's login name – no display name, no avatar, no current profile state.

Goal

When two peers connect, two things are synchronised – without a server, purely P2P over the DataChannel:

1. Profile sync – current display name, avatar, etc. from A → B and vice versa
2. History sync – missing messages since the last shared timestamp

How It Works (Draft)

1
Peer A connects to Peer B
2
  ↓
3
── Phase 1: Profile Sync ────────────────────────────
4
A sends: { type: 'sync:profile', displayName: 'Alex', avatar: null, updatedAt: ... }
5
B stores A's profile locally → from now on shows "Alex" instead of login name
6
B sends the same back → A knows B's current profile state
7
  ↓
8
── Phase 2: History Sync ────────────────────────────
9
A sends: { type: 'sync:request', lastTs: 1710000000000 }
10
  (= timestamp of the last known message from B)
11
B responds: { type: 'sync:response', messages: [...] }
12
  (= all messages B sent after lastTs)
13
A stores missing messages in localStorage + renders them
14
B does the same in the other direction

Profile Data in Sync

Profile sync is therefore already useful from v1.7.0 onwards – once display name exists. History sync can come earlier (no profile required).

Limitations (by design)

• No server buffer – sync only works when both peers are online
• No offline sending – messages sent while the other is offline are lost (stays this way)
• Direct peers only – no relay, no multi-hop
• One-time at connection establishment – no persistent sync channel

Open Questions

Possible Version

• History sync → v1.9.0, standalone after v1.4.0 (i18n)
• Profile sync → v1.9.0, together with v1.6.0 (profile features)
• Full sync incl. images → v1.9.0, after v1.6.0 when IndexedDB is available

v2.0.0 – Abrax (Codename: Abra)

Status: PLANNED Prerequisite: v1.9.0 completed, @xpulse/ai package ready Concept: COMP_ai_concept.md

AI integration via @xpulse/ai – a special AI peer in the peers list, with full conversation context, streaming, and full user control over provider, model, and personality. Browser-to-provider directly, no detour via xPulse server.

Opt-in & Legal

• Implement consent flow (modal on "activate AI")
• xp_ai_consent in localStorage with version tracking
• Create legal page xpulse.one/tool/chat/ai-terms/
• "Deactivate AI" + complete deletion of all AI data

AI Peer

• 🤖 AI peer in peers list (only visible after opt-in)
• Name configurable in peer details (default: "Abrax")
• Personality configurable in peer details (templates + free text)
• Chat history in @xpulse/session like any other peer

Provider & Settings (Profile)

• Provider selection: Anthropic, OpenAI, xAI, Google, Ollama
• API key input – stored encrypted, never leaves the browser
• Direct link to API key page of the respective provider
• Ollama URL configurable (for local instances)
• Ollama marked as "Advanced" with link to guide

Chat Info Panel

• Model selection (dynamically queried via provider API)
• Streaming on/off
• Context size (number of messages)
• Creativity / temperature (0.0 – 1.0)
• Max. response length (tokens)
• (i) Tooltip with help text for each setting
• Context warning when older messages are dropped
• Token usage (this session + total local)
• "Clear history" button

i18n

• Create src/translations/ai.de.json + ai.en.json
• All UI texts, help texts, personality templates in de + en

Chat UX

• Input field disabled while Abrax is responding (streaming + normal)
• Automatic focus return after complete response
• Persistent AI notice below input ({trans:ai.chat.disclaimer})