Build your own Twitter / X.

# Build an original app inspired by Twitter / X

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 microblogging app called Shortwave, inspired by Twitter/X. It serves a small public-interest community publishing short text posts. The primary journey is following an account, posting an update, replying, and organizing accounts into a list. Use transparent chronological timelines and clear moderation instead of copying a global algorithmic network.

## Design
Use an original compact timeline with readable text, threaded replies, a composer with a real character limit, and separate views for following and lists. Keep author identity, timestamps, reply context, and visibility clear. Repost and like controls need accessible labels and explicit active states.

## Features
1. Identity and following: register profiles with unique handles, follow/unfollow, block users, and search public handles. Validate reserved names and normalize handle uniqueness without silently changing display names.

2. Short posts: publish text with a documented Unicode-aware length rule, edit with a visible edited state, delete your own posts, and display permitted links safely. Reject empty or oversize content at the API boundary.

3. Threads and timelines: reply to posts, show bounded conversation threads, paginate following and public newest-first feeds, and keep deleted parents as tombstones. Direct post retrieval must obey blocking and visibility rules.

4. Reactions and lists: toggle likes and reposts once per user, create public/private account lists, and browse list timelines. Keep private list membership out of public responses.

5. Bookmarks and moderation: save private bookmarks, report content, review/remove posts as a moderator, and provide real in-app reply/follow notifications with per-user read state.

## Tech stack
Use a Go API, PostgreSQL, and a TypeScript client. Implement unique constraints for follows/reactions, cursor pagination, safe link rendering, and explicit user/moderator authorization. Do not fetch arbitrary private-network link previews. Keep push delivery optional and fall back to reliable polling with duplicate-safe event IDs.

## Data & behavior
User {handle, displayName}; Follow; Post {authorId, parentId, text, editedAt, deletedAt}; Like; Repost; List {ownerId, visibility}; ListMember; Bookmark; Block; Report; ModerationAction; Notification. Choose stable ordering by createdAt plus id and an explicit maximum reply depth.

Acceptance checks and scope:
Test duplicate reposts, emoji length boundaries, a deleted parent, a private list read by a stranger, blocked-user replies, feed pagination during posting, and retry after a dropped connection. Exclude Spaces, ads, commercial trends, paid verification, and scraped X timelines.

## 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.