Comments on: If you aren’t embarrassed by v1.0 you didn’t release it early enough

By: Ensi

Ensi — Mon, 24 Mar 2008 21:11:09 +0000

I see. Well thats all right then.

By: Andy Brice

Andy Brice — Mon, 24 Mar 2008 14:40:14 +0000

Ensi,

I take your point, but I was only talking about releasing v1.0. Not subsequent releases. That will have to wait for a separate article. ;0)

By: ensi

ensi — Mon, 24 Mar 2008 12:29:30 +0000

Probably very sound advice. Just one note though, releasing often puts an extra burden on the user, since in order to stay up to date and get the most out of your software they are forced to upgrade every time you release. And we all know that when you upgrade change something around, something always breaks no matter how well tested the release was. This is even worse if the versions are not compatible with each other.

By: maria

maria — Tue, 02 Oct 2007 10:02:28 +0000

I fully agree. But really make it stable. It must not have many feature. But stability. Don’t let the banane ripe in the hand of the customer.

maria

By: BrandonZ

BrandonZ — Sat, 15 Sep 2007 07:20:03 +0000

I completely agree with your philosophy. Personally I have just did the same thing with an open-source app. I decided that it was better to just get out a 1.0 version with a minimal amount of features and just take in user feedback and work my way up so that I can continue to have frequent releases. The program is called ZScreen by the way and it is available on my website. It is a C# app that can FTP screenshots and put the URL in your clipboard in a single keystroke.

By: Best of Feeds - 37 links - lifehacks, tips, productivity, programming, blogging « Internet Duct Tape

Sun, 26 Aug 2007 02:41:11 +0000

[...] [CODE] If you aren’t embarrassed by v1.0 you didn’t release it early enough (successfulsoftware.net, 4 saves, 8 inbound links, 4 diggs) [...]

By: First advice « Startupping echoes

First advice « Startupping echoes — Thu, 23 Aug 2007 15:10:47 +0000

[...] by vladhorby on August 23rd, 2007 Here. Couldn’t agree more… now let’s see if we can build a stable-enough [...]

By: lb

lb — Fri, 17 Aug 2007 06:27:48 +0000

top stuff. fully agree!

By: “Release early, release often”: why bother at all « Meltin’ Posts

Thu, 16 Aug 2007 20:01:04 +0000

[...] 16th, 2007 Here is a very nice post by Andy Brice @ “Successful Software” about the importance of releasing early in software development. I commented the post as well, so I [...]

By: savino

savino — Thu, 16 Aug 2007 19:31:56 +0000

Personally I believe releasing a minimally featured version early in the development process is - of course - a good practice, but it also gets a bit frustrating.

At least this is actually what I am experiencing with my current project: I know what I’d like the app to do, so giving the user a list of “TODOs” and a small features set, gives the feeling he maybe won’t really understand the right potential of the app.

On the other hand, late releasing is absolutely unacceptable in business scenarios, and user feedback is way too important since the very first moments of a product’s life cycle, so the “release early, release often” motto surely holds.