01
Generation is slow, so the product is asynchronous by default
A ten-page comic is many image generations. The work is queued and reported on rather than awaited, so the app stays responsive and a dropped connection never costs a user their comic.
Case study — COMAIC
Photos and a story idea become illustrated comics
Add up to five character photos, pick an art style, describe a plot — and COMAIC generates a multi-page comic with panels, dialogue and illustrated pages, in Manga, Manhwa, Comic, Seinen, Shonen, Shojo, Josei and Manhua styles. Up to ten pages per comic, exportable as PDF.
An end-to-end generative-media product: the prompt and image pipeline, asynchronous generation, character consistency across panels, the credit system, PDF export, storage and the App Store release.

What shipped
Stack
Engineering
01
A ten-page comic is many image generations. The work is queued and reported on rather than awaited, so the app stays responsive and a dropped connection never costs a user their comic.
02
The hard requirement is that the same person still looks like the same person on page seven. That constrains how reference images are carried through the pipeline and how each panel prompt is composed.
03
Image generation has real per-call cost, so the subscription is metered in credits — three per page — rather than sold as unlimited. The billing model follows the unit economics instead of fighting them.
Screens


Still to publish
I have not published usage numbers for this app. When I do, they will be figures I can stand behind rather than rounded-up vanity metrics — so for now the evidence here is the product itself, which you can download and use.
Building something like this?