# Build brief — a focused alternative to Canva

> **Verdict:** Partly, if you narrow it · **Buildability:** 44/100 · **Category:** Design
> **Source:** https://www.canitbevibecoded.com/canva
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Canva. Verify current pricing and capabilities before acting.

## Context

**Canva** — Template-based design suite for social posts, docs, decks, and brand assets. It currently costs $18/mo.

A prompt-to-template design generator is buildable, but Canva's value is templates, stock assets, collaboration, brand kits, print/export workflows, and distribution.

This brief describes a focused, single-operator replacement for the part of Canva that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Generate simple social graphics from templates, edit text/images on a canvas, export PNG/PDF, and save brand colors.

- Generate a constrained editing workflow with reusable templates and deterministic exports.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Canvas editor library.
- Template assets.
- File export pipeline.
- Hosted app.

### Data and integrations

- Image generation/editing API.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a small canvas design editor to replace Canva Pro. Requirements:

- A local web app: Fabric.js on a canvas element with vanilla JS, and a tiny
  Express server for saving and export. Script tags only, no build step.
- Canvas presets: Instagram post 1080x1080, story 1080x1920, X header
  1500x500, A4 poster, plus a custom-size dialog.
- Editing: text using my local fonts, image upload, rectangles and lines, a
  layer list with reorder, align-to-center helpers, and snap guides at the
  canvas center.
- A brand panel loaded from brand.json: my 4 colors and 2 fonts as one-click
  swatches.
- Every design serializes to designs/<name>.json and reopens exactly;
  duplicate-as-template is the template system. Ship 3 starter designs.
- Export PNG at 1x and 2x via Fabric's toDataURL, and PDF by printing the
  canvas page with Playwright.
- All files local, no accounts, no telemetry.
- Out of scope: stock photos, AI image tools, and collaboration. The asset
  library is what the Pro fee buys, I bring my own images.
- README: how to add fonts and where designs live on disk.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Template library.
- Stock/licensed assets.
- Magic Studio depth.
- Collaboration.
- Licensed content and distribution rights are not reproducible with an LLM.
- Permissions, presence, and shared workflows are difficult to simplify.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Penpot](https://github.com/penpot/penpot) — Open-source design/prototyping platform; not a Canva clone, but real prior art for browser

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/canva