Build your own Miro.

# Build an original app inspired by Miro

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 digital whiteboard called Wideboard, inspired by Miro. It is for individuals mapping ideas and planning workshops. The main flow is opening a board, arranging notes and shapes, connecting ideas, and exporting the board.

## Design
Use a bright, spacious canvas with a subtle dot grid, a floating left tool palette, top board controls, and zoom controls. Sticky notes use a restrained palette; object controls appear on selection. Make the canvas intuitive without obscuring content.

## Features
1. Boards and navigation: create, rename, duplicate, and archive boards. Pan, zoom, fit all content, and preserve the last viewport.

2. Content: add sticky notes, text, rectangles, circles, and arrows. Edit text inline, choose colors, resize notes, and draw basic freehand strokes.

3. Organization: select multiple objects, group, align, duplicate, and change z-order. Frames organize regions without changing object coordinates unexpectedly.

4. Connectors: attach arrow endpoints to shape anchors so moving a shape updates its connectors. Delete connections cleanly when an object is removed.

5. History and export: undo/redo coherent actions, autosave board changes, export a selected frame or entire board to PNG, and download/import validated board JSON.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
Board {id, name, viewport}; Object {id, boardId, type, x, y, width, height, text, style, points, groupId, frameId, order}; Connector {id, boardId, startObjectId, endObjectId, anchors, style}; Frame {id, boardId, title, bounds}. Persist the personal workspace in IndexedDB. Use canvas or SVG with a serializable state model and a command-based undo history.

Acceptance checks and scope:
Test arrow attachment after moves, coordinate accuracy at different zooms, undo/redo after deleting connected objects, reload persistence, and export cropping. Provide a list-based object navigator and keyboard movement for accessibility. Exclude real-time collaboration, video calls, and third-party integrations from the first version.

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