CommunityCAN I VIBECODE
Pumble?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Pumble is a freemium business team-chat and collaboration app available on web, desktop, and mobile. Its distinctive free plan includes unlimited users, unlimited searchable chat history, user/workspace administration, and 24/7 web support. Core workflow: public and private channels, invitation-only group chats, one-to-one direct messages, threaded replies, voice and video messages, file sharing, and unlimited message search. Meetings: one-click video conferencing, screen sharing, and 'Pumble meet' links shareable into Google Calendar. Productivity features: scheduled messages, granular notification controls, user groups, external guest access, Slack import (public channels/messages/team), and integrations. Administration/security: role-based permissions, SSO (SAML2, OAuth2), data-retention policies, and SOC 2 certification. Newer capability: an MCP (Model Context Protocol) server lettin
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a Pumble-style team collaboration chat server (a named clone/tribute, not Pumble itself). Replicate the distinctive Pumble workflow: persistent workspaces; public and private channels; 1:1 DMs and invitation-only group chats; threaded replies that branch off messages; voice and video messages; file sharing with unlimited searchable history; scheduled messages; and one-click meet-link generation shareable into calendars. User-facing requirements: (1) workspace creation with admin invite flows; (2) real-time channel/DM messaging with typing indicators, edit/delete, unread counts, and per-channel notification preferences; (3) threads branching from any message; (4) file/image/video upload with full-text search across all history; (5) voice-message recording via MediaRecorder and video-message capture; (6) meet-link generator that opens a WebRTC room and returns a shareable URL; (7) scheduler queue that delivers messages at chosen times; (8) role-based permissions (admin/member/guest) and user groups; (9) external guests scoped to selected channels; (10) a simple importer accepting Slack-export-style JSON with public channels and messages. Technical requirements: TypeScript monorepo (apps/api, apps/web); Node.js backend (Fastify or Express) with Socket.IO/WebSockets; PostgreSQL with full-text search (or Meilisearch) for unlimited history; Redis for presence and scheduled delivery; React client (Vite) with a standard component library; JWT auth with an OAuth stub; S3-compatible object storage for uploads; basic 2-person video via PeerJS. Provide docker-compose (Postgres, Redis, MinIO), migrations, seed script, and CI lint/tests. Do not copy Pumble's brand, logo, colors, copy, or UI layout; build an original interface facilitating the same workflow. Out of scope: enterprise SSO/SCIM federation, E2E encryption, native mobile apps (responsive web/PWA only), admin analytics dashboards, the AI-agent MCP server, and desktop installers. Deliver a README covering setup (env vars, migrations, seed), architecture overview, test commands, and important limitations (e.g., polling fallback for presence, 2-person video-room cap, no offline sync).