Why does it take 20 seconds to composite a string onto a shirt? Are you using generative AI for something that can be done in milliseconds with traditional techniques?
It cannot be that, surely since the page prior to the CTA actually shows the shirt with the string composited. So is it perhaps doing some live pricing based on a collection of vendors on the backend? Better to show an initial price and then a progress bar that moves up as the vendors return prices I think. Either way, I reflexively almost clicked away as soon as the 20 s started.
Damn, ok. Good feedback. I heard that from someone else, too. Our attention spans are fried, lol. Can't wait 20 seconds for a shirt preview! It's true though. So the first "preview" is just rendering text on top of a blank shirt mockup, and the the second one (after you click and go to /preview) actually sends the text to the Printful API to get a render of how the shirt will actually appear. That's the delay, waiting for the final image to come back from Printful.
What print on demand supplier are you using? I'm building a merch builder website for startups and most PODs (Gelato, Printify, Printful) all have their own issues.
i built teebot.dev because every time i wanted to put text on a shirt, i got lost in some enshitified print companies design flow. i just wanted to get words on a shirt.
So i made teebot.dev. type your text and ship it. that's it.
Banner says "custom tees, delivered at cost" but then the preview page shows a price that is double what I get going to their drop shipper directly (printful). No detailed product info on shirt type or quality. No company info. Hard pass.
39 comments
teeis just too strong.tee(1)as soon as my terminal opens. I guess this is just another case of really, really bad naming.So i made teebot.dev. type your text and ship it. that's it.
here's the CLI:
npx teebot "wtf?"