Build your own Canva.

# Build an original app inspired by Canva

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 graphic design editor called Postcard, inspired by Canva. It is for people creating social graphics, posters, and simple presentations from original templates. The main flow is picking a canvas size, composing a design, and exporting a high-quality image.

## Design
Use a friendly editor with a template and elements library on the left, a centered canvas, and contextual controls above it. Use a light workspace, turquoise accent, clear selected-object handles, and responsive panels. Template previews should be generated from actual document data.

## Features
1. Start a design: choose a social post, story, poster, or custom canvas size; start blank or from six original templates created for this app.

2. Compose: add text, geometric shapes, and user-uploaded images; move, resize, rotate, crop images, change layering, and align selected objects.

3. Typography and styles: edit text, font size, weight, color, alignment, and background; apply original color palettes and basic design presets.

4. Documents: rename, duplicate, save, and reopen designs; add multiple pages and reorder them. Undo and redo grouped edit operations.

5. Export: download the active page as PNG or JPEG at a chosen scale; export all pages as a ZIP if an appropriate library is available. Save a portable document as validated 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
Design {id, title, width, height}; Page {id, designId, background, order}; Element {id, pageId, type, position, dimensions, rotation, content, style, order}; Asset {id, designId, mimeType, blob}; Template {id, originalSchema}. Use IndexedDB for designs and uploaded blobs. Bundle original or appropriately licensed fonts and graphics; do not scrape template libraries.

Acceptance checks and scope:
Verify exported dimensions and text rendering, crop behavior, layer order, reload persistence, undo after multiple object changes, and large image validation. Make multi-page state independent. Exclude premium asset marketplaces, background-removal services, AI generation, and live collaboration from the MVP.

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