DEV Community

Dancing With Santa
Dancing With Santa

Posted on

Why I Locked the Constraints on a One-Photo Dancing With Santa AI Video Pipeline

I operate Dancing With Santa, a seasonal tool I built and run as an individual developer. This is a first-party note, not an affiliate post. I wanted a narrow path: you bring one still, and a dancing with Santa AI video comes back as a short vertical clip. No prompt. No filming. No editing step. The interesting work was not adding options. It was deciding what the pipeline would refuse.

Why one photo, and why no prompt

A prompt box looks harmless. In practice it turns a seasonal meme tool into an open-ended video desk. People will ask for a different dance, a different backdrop, a longer take, a second character, or a joke the job was never designed to handle. I would then have to explain, on every odd result, whether the tool failed or simply did not do a thing I never promised.

I also declined a multi-photo or reference-video path. Those might be useful in a general motion tool. They are a different product. I wanted a one-shot job: one photo of yourself, or one photo of your own pet, and a single intended output — that subject dancing beside Santa Claus. If I cannot describe the job in one sentence, I cannot operate the refunds, the support replies, or the input checks consistently.

That is why the public product stays a one-photo job that returns a short vertical clip. The constraint is the product.

Why I froze the clip shape

The output is about 15 seconds, 720p, and 9:16. I picked a short vertical file because that is the shape I was willing to stand behind: a brief clip, not a custom-length video, and not a second landscape version. I did not add a duration control, a resolution picker, or a format menu. Those sound like modest features. For a tool I operate alone, they split one pipeline into several, and they make it harder to say what a completed job is.

I am not claiming this is the only reasonable output shape. I am saying I would rather ship one clear object than a list of toggles I cannot fully support.

The input gate is part of the product

The tool is for adults 18 and older. It accepts a photo of yourself or of your own pet. It does not accept photos of children, and it does not accept photos of other people. That is a policy gate at the entrance, not a style option and not something generation is supposed to fix.

If you are building a similar one-shot media tool, write this part down before you talk about queues or vendors. An input you should not have accepted becomes a mess later: you cannot treat it as a normal failed job, and you should not be generating from it in the first place.

What counts as a failed job

Credits force you to define failure. I sell one-time credit packs, with no subscription and no auto-renewal. The packs are $9.99, $14.99, $24.99, and $34.99, for 50, 100, 200, and 300 credits — enough for 1, 2, 4, or 6 videos. Credits stay valid for one year.

A job can fail in a way that is on me, or on the generation path: the run does not complete, it times out, or the video cannot be played. In those cases, deducted credits are returned automatically. That is the definition I use for a failed job.

Not liking the result is not a failure. Taste is not a timeout. If the clip plays and the job finished, the credits stay used. I know that is a harder line to hear than a blanket refund, but it is the only line that stays honest once a completed file exists.

There is a separate rule for unused packs. If a pack is completely unused within seven days of purchase, a full refund can be requested. The "completely unused" condition matters. Partial use is not the same case.

Photo retention is a constraint too

I did not want the upload to turn into an informal training set for a model I own, because I do not train one. Photos are used for content-safety checks and for generation. Originals stored on the site are deleted within seven days. The generation vendor may still keep a copy of the job input; if someone wants that copy removed, they can write to support@dancingwithsanta.com and ask.

That split is easy to gloss over and worth stating plainly. Deleted on my side is not the same claim as deleted everywhere. I would rather say the second part than imply a clean wipe I cannot personally guarantee on a vendor system.

What I would tell someone building a similar tool

Write the refusals first. Decide what one job is, what the file out of it is, which inputs you will not take, and which failures return credits. If those answers are fuzzy, a prompt editor and a longer feature list will not save the product. They will only give you more cases to argue about.

The no-prompt generator I operate is just one seasonal example of that approach. The useful part, if you are evaluating a one-shot media tool, is not a long menu. It is a short list of things the job will not do.

Top comments (0)