Build your own Telegram.

# Build an original app inspired by Telegram

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original web messaging service called Channelpost, inspired by Telegram’s group and broadcast-channel workflows. A small community uses direct chats, moderated groups, and owner-managed announcement channels with history synchronized across browser sessions. This is an independent authenticated cloud messenger, with no Telegram network integration.

## Design
Create an original responsive chat workspace with a conversation sidebar, message history, clear channel/group labels, member settings, and unread indicators. Make broadcast permissions distinct from ordinary group participation. Show actual connection, send, edit, and deletion state.

## Features
1. Conversations: create direct chats, small groups, and broadcast channels with explicit membership roles. Only channel publishers can post to a broadcast; group members follow a separate permission model.

2. Invitations and membership: issue revocable/expiring invitations, approve joins where configured, remove or ban members, and prevent removing the sole owner. Enforce membership on HTTP history and live subscriptions.

3. Messages: send safe text and bounded attachments, reply, edit your own messages, pin permitted messages, and paginate synchronized history. Use client IDs and server sequence numbers for retry and reconnect correctness.

4. Read state and search: persist per-user read positions, calculate unread counts, search only authorized conversations, and handle a removed message referenced by a reply with an explicit tombstone.

5. Safety and administration: mute, block, report, moderate channel/group content, export your allowed history, and revoke all browser sessions on request. Restrict attachment delivery to authorized recipients.

## Tech stack
Use TypeScript browser clients, a Go API/WebSocket service, PostgreSQL, and private object storage. Enforce roles on every real-time operation and use TLS. The starter is server-stored cloud messaging; end-to-end encrypted secret chats require a separately reviewed protocol and must not be implied.

## Data & behavior
User; BrowserSession; Conversation {type}; Membership {role, bannedAt}; Invite {tokenHash, expiry}; Message {clientId, sequence, editedAt, deletedAt}; Attachment; ReadPosition; PinnedMessage; Block; Report; ModerationEvent. Define history visibility on join/leave explicitly.

Acceptance checks and scope:
Test publisher versus subscriber posting, removed-member socket access, two-session read synchronization, duplicate sends, revoked invites, attachment access, and blocked DMs. Exclude Telegram interoperability, bots, calls, secret-chat encryption claims, unlimited public groups, and automated message scraping.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.