Fabric.js Web platform Meme Generator

@alizain721

Nice brief and clear spec. I like that you skipped templates and want the canvas empty and performant with large images while keeping everything editable. The real challenge is keeping large image fidelity without forcing expensive full canvas redraws and avoiding rasterizing layer objects when cropping or rotating. Treat the photo as a separate immutable asset and apply transforms to the canvas layer stack instead of flattening. I built PicMe where I handled responsive image editors and touch gestures across devices, including performant canvas interactions on mid range phones. Approach 1. Initialize Fabric canvas with a background image object stored as an immutable blob and a lightweight working bitmap for display 2. Text layers as Fabric Textbox objects with font loading done via Google Fonts subset and simple shadow settings 3. Crop and rotate by applying clipPath and transformation matrices to the image and adjusting layer transforms so objects remain editable 4. Persist full project as serialized Fabric toObject plus image blobs in IndexedDB and restore by rehydrating objects and reattaching images For the canvas objects and timeline I would keep a minimal model: backgroundImage asset id plus layered objects array with type metadata and transform matrix. Timeline is a linear stack of serialized deltas with periodic full snapshots for fast restore and small undo depth to limit storage. Quick question Do you want a small undo redo stack only or full action history persisted between sessions I will prepare a short architecture diagram and a live demo link for testing once I have a sample image to validate performance.