Building CraftyAI in public
CraftyAI is changing quickly. This developer blog is where we slow down long enough to explain what changed, why we made the call, and what we learned while building creative workflows for marketers.
More than a changelog
A release list tells you what shipped. We want these notes to preserve the useful part: the trade-offs, failed approaches, performance discoveries, and tiny interface details that made a feature feel right.
Our goal is simple: make the work legible while it is still fresh.
Expect practical notes from image generation, video workflows, prompt tooling, and the infrastructure holding it together. We will not publish private customer data, credentials, or claims that cannot be supported by the shipped product.
What we intend to publish
Product decisions
Some posts explain why a control behaves a particular way or why a workflow has a deliberate constraint. Prompt workflows that remember context, for example, describes why a generated prompt belongs to a specific group of settings rather than remaining valid after every change.
Creative workflows
Practical guides focus on completing a real marketing task. They should help a reader plan inputs, choose settings, avoid common mistakes, and judge an output—even if that reader arrived through a nonbranded search. Our Whiteboard and Paper Collage articles introduce the formats; step-by-step guides connect those formats to repeatable work.
Model behavior and cost
Model names are less useful than knowing what each option accepts and what it is suited to. We will document supported text-to-image, image-to-video, duration, resolution, and reference workflows without pretending every model is interchangeable. The CraftyAI model guide is the living starting point, while predictable video pricing explains how the interface and backend calculate cost.
Performance and infrastructure
Creative tools handle large files and long-running jobs, so small implementation decisions can directly affect trust. We will share useful lessons about media delivery, validation, failure handling, and keeping browser state aligned with backend rules. These posts may be technical, but they should still explain the user consequence.
Release notes versus practical guides
A release note starts with a shipped change: what became available, how it works now, and any important limits. Introducing Whiteboard Video and Introducing Paper Collage are examples.
A practical guide starts with a reader’s goal. It should remain useful beyond a single release and provide a process that can be repeated. Tags and descriptive titles will make the distinction easier to see, while related-reading links connect an announcement to the deeper workflow behind it.
Engineering notes sit between the two. They explain a design or architecture choice with enough implementation detail to be credible, then translate it into a consequence a user can understand.
Why return
Prospective users can see how the product actually behaves before investing time in a workflow. Marketers can pick up repeatable ways to prepare references, prompts, and output settings. Developers can follow the trade-offs behind billing, caching, media performance, and generation orchestration.
Publishing close to the work also creates a useful discipline for us. If a feature is difficult to explain clearly, its interface or contract may need another pass. If an article cannot verify a claim against source or tested behavior, that claim should not be published.
What comes next
We will publish concise build notes alongside deeper technical write-ups and task-focused guides. Each post will be tagged, searchable, dated, and updated when the underlying behavior changes. The aim is a useful record, not a stream of announcements for their own sake.
Explore CraftyAI
Create product-ready marketing images, or begin with the articles below to understand the models and workflow decisions behind the studio.
Start exploring
Read about prompt workflows that remember context or browse the models available on CraftyAI.