This was crazy fast, that you were able to implement this so quickly after getting feedback from HN (and replying to our questions and queries at the same time).
Kudos is all I have to say. I wish I had those skills!
Cool, thanks for answering. I hope you won't mind if I pick your brain&ways a little more. So, some questions:
1) Are you doing this white-label?
2) Is this a "passive income" side-project, or something you've put a lot of time to? (Well, it's clear that you've put a lot of time to it... it's a beautiful finished product in every way, but I'm still curious to know how much effort has been put into this)
3) Are you working closely with scalablepress folks, or do you find their api to be powerful enough that you need not get in touch with them?
4) I see that just the blocks are being printed, not the code. There is probably a lot of demand for the printed-code shirts - why not go for that? (is it markedly more expensive to print text on shirts?)
1) There's no branding on the shirt at all. The shirt is shipped from Scalable Press, so I'm not sure what the packaging will say, but I imagine they have something in place for white-labelling.
2) "Passive income" side project, though with all the HN hate it's turning into a bit more scrambling than I'd imagined :).
3) I do ask them questions since I'm a pretty early user of the API, but it's pretty well-documented at this point so I don't imagine you'd run into much trouble developing on it.
Please don't mind the 'HN hate', we're a nit-picky bunch. Remember that almost always you can make it better.
The current upset seems to be about confusion as to whether shirts will have actual code or not on them -- give the folks who've ordered some sort of a clarification note, and hope for the best.
Regardless, this was a pretty nifty project. I give it a 9/10 (1 pt. lost for lacking UX in some areas and slight misrepresentation of product, but I know your next project, whatever it'll be, will more than make up for it :))
After seeing the proof, I was still confused what I would receive, and thought maybe the blocks were placeholders for the text that would appear in the final print. You should definitely make this more clear, because the phrasing on the site gives the impression you'll get the actual code.
Without a doubt you'll get lots of requests for refunds if this isn't adjusted.
While our webhooks are perfect for building things like receipts, we want to make the seller experience for the most common use case as nice as possible.
We do encourage folks to use our webhooks to build receipts for more complex use cases (e.g. if you want to include maps, images, or just in general need a more complex receipt structure for your particular business), but the simplest case is one we can and should provide well for :).
