Skip to content

[Feature Request] Discord, Telegram and Hybrid navigation layouts with universal chat folders #98

Open

Description

@pirate-boop

First of all, thank you for the incredible work on Vector. The mobile redesign in v0.5.1 is already remarkably close to what I would want from a modern Nostr messenger.

After exploring the source code, I noticed that Vector already has much of the necessary foundation: a collapsible Community rail, filtered chat tabs, synchronized Community folders, and the Main Menu.

I'd love to suggest taking this further by making navigation a first-class, user-configurable experience.

  1. Optional layout presets

Under Settings → Appearance → Layout, users could choose between:

Discord

  • The existing Community rail and channel sidebar.
  • Fast switching between Communities.
  • Persistent access to channels and voice rooms.

Telegram

  • A unified conversation list containing DMs, Communities and optionally individual channels.
  • Horizontal folder tabs above the conversation list.
  • No permanently visible Community rail.
  • Opening a Community shows its channels in a dedicated view.

Hybrid

  • The Community rail remains available.
  • User-created folders organize conversations in the main list.
  • Both navigation systems can coexist.

These would be interface presets rather than separate implementations of the messaging engine.

  1. Universal conversation folders

The existing Community folders are a great foundation, but Telegram-style organization would benefit from folders that can contain different conversation types.

Suggested capabilities:

  • Create, rename, reorder and delete folders.
  • Add DMs and Communities to the same folder.
  • Optionally include individual Community channels.
  • Allow a conversation to appear in multiple folders.
  • Create dynamic folders using rules such as Unread, Contacts, Communities or Muted.
  • Aggregate unread counters and mentions per folder.
  • Configure folder-specific notification behavior.
  • Support pinned conversations and folders.
  • Synchronize folder definitions securely between devices.

Example folders: All, Personal, Development, Nostr, Communities, Unread.

  1. Mobile navigation and gestures
  • Swipe horizontally between folder tabs.
  • Allow the Community rail to be opened with a deliberate edge gesture.
  • Preserve the current conversation when switching layout preferences.
  • Remember the last selected folder.
  • Optional compact and comfortable conversation row densities.
  • Accessible one-handed navigation.
  • Support reduced-motion preferences.
  1. Desktop experience
  • Independent desktop and mobile layout preferences.
  • Optional persistent folder sidebar.
  • Keyboard shortcuts for switching folders and Communities.
  • Adjustable sidebar widths.
  • Retain the existing widescreen layout for users who prefer it.

Implementation considerations

Some existing areas that appear relevant:

  • "src/components/lib/console.svelte.js"
  • "src/components/shell/ChatListPane.svelte"
  • "src/components/shell/ConsoleTabs.svelte"
  • "src/components/settings/Display.svelte"
  • "crates/vector-core/src/rail_layout.rs"

The existing encrypted rail preferences could serve as an architectural reference for universal chat-folder synchronization, without mixing chat organization with Community membership or cryptographic material.

I'd suggest implementing this incrementally:

  1. Expose explicit layout preferences using the existing rail behavior.
  2. Add local user-defined chat folders and filters.
  3. Introduce encrypted cross-device folder synchronization.
  4. Add the optional Hybrid layout and additional customization.

The goal is not to replace Vector's identity with a Telegram clone. It's to let users choose the navigation style that feels natural while retaining Vector's privacy, decentralization and advanced Community features.

I'd love to hear whether this direction aligns with the project's UX roadmap.

Activity

  1. YuurinBee commented on Nov 8, 2026

    @YuurinBee

    Hey @pirate-boop, firstly thanks for taking the time to not only think about this from your experience with Vector, but type it all and organize it nicely to share with us. We will review this more in detail tomorrow, but the general concept is nice in terms of templates per types of users. We have thought about something similar, not just for chats but the general app in terms of Simple, Standard, Advanced. Really, just different userflows for types of users which is pretty much what you have mentioned, along with some other things.

    We will keep this open. Appreciate you sharing and we will discuss more to see what all options make the most sense and give this feedback the attention it deserves. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions