[wpietri]

I'm a big fan of "ship early, ship often", but you have to set expectations properly. If something is not ready for prime time, you should signal that. Call it v 0.7, say it's a beta, label it as a "labs" product. Say up front where the known weaknesses are, and say what audience you want.

I also strongly recommend working with a small, carefully selected audience to begin with. Typically only a small percentage of your eventual audience will put up with the rough edges of a work in progress. Getting the average audience member involved early on is frustrating for both sides. You get a lot of feedback on things you a) already know about, and b) are intentionally avoiding for now. And they waste a bunch of time on stuff that wasn't intended for them.

[sp332]

Good points, just thought I'd mention that Mozilla Labs shut down a while ago.

[Lerc]

Did they? Seems like something they should mention on https://mozillalabs.com

No-one to turn out the lights?

[sp332]

Yeah. http://www.ianbicking.org/blog/2014/09/professional-transiti... "It’s a little hard to tell – I guess we didn’t actually shutter anything, and though it was announced internally it is entirely unclear externally. But Mozilla Labs is definitely shut down."

[arenaninja]

Honestly, I thought it was obvious that the entire thing is probably alpha or thereabout

[magpi3]

The "Brick 2.0" version number says otherwise. I agree with the parent post. Version numbers say a lot about waht a user can expect. They should change this to 0.2.