From one phone photo to a complete product pack
A phone-friendly studio extracts visible facts, creates product-scene alternatives, checks likely visual changes, writes editable Thai copy, builds short vertical video, and keeps the results together.
Durable image and video queues · source-versus-result checks · Thai copy · shared gallery · credit use and refunds
What needed to change
A seller needed a repeatable content workflow, not a prompt box and a pile of downloaded files.
The constraint shaping the build
Keep provider credentials and model controls away from the seller interface, make paid work durable, and prevent generated claims from outrunning visible product facts.
How the pieces connect
- Phone photo
- Visible facts
- Image alternatives
- Fidelity check
- Editable Thai copy
- Short video and shared gallery
See whether this starting point fits your workflow
The matching system explains who it is for, what a first release includes, and the rough cost. Supporting links show the implementation evidence.
How I built it
- Extract visible facts before writing copy or generating a scene.
- Run images and video through durable jobs so closing the app does not lose paid work.
- Compare the source and generated product, then show warnings instead of claiming perfect fidelity.
- Keep model choice, prompts, credentials, credits, refunds, and provider controls on the owner side.
What I verified
- Phone upload and camera capture
- Structured fact extraction, image generation, fidelity comparison, and Thai copy
- Durable image and video queues with usage deductions and refunds
- Seller and owner roles, persistent settings, and shared history
Current state: The current build is for one seller. A multi-tenant version is not built, and source-versus-result checks cannot guarantee that generated media preserves every product detail.