For the record, I don't think it's a problem if someone's prototype is buggy. That's inherent to the nature of prototypes and setting the quality-expectation too high would prevent independent or amateur developers from implementing and sharing their ideas.

What I do think, is that:

1) there is a significant difference between a prototype and a product,

2) I should expect a product to meet industry standard practice,

3) it should clearly communicated what is a prototype and what is a product,

4) and it's generally a bad idea to further-develop a prototype into a product, without going back to the design board one more time.

I will continue to share interesting prototypes, as I find them, as I like seeing how people react to the basic idea.

But you will know, when I think something is a product worth relying on.

This is where I am.