This has two major problems (probably more, depending on which way you look at it, i am just analysing from a commercial/marketing pov): One, You have a faulty program at launch, that frustrates users and helps with a bad company/product rep. The rest of the development would be carried out during the next couple months, and applied to the product through hotfixes. What ended up happening: they crammed all the features they could in the 8-10 months they had for development, then tested as much as they could until launch.
That's because, most of the time, bugs and crashes would be so critical, at the start of the new version cycle, it just wasn't practical to use it in production setup. "Finish the project in the version you started working on it", they say. Any of you started working with the new version right away? I have never done so. I think they are shifting the way they make new releases, here is how i think they will do it and why i think it's a good thing.Įvery Archicad version, for the past decade, launched with a certain degree of major bugs. Now, the first sentence of that post is this one:īy releasing new capabilities and enhancements with every Archicad update, our users benefit from continuous improvements throughout the year. Hotfixes started to be called Updates, they had new features added to the software, and they even have articles on the site.Take a look here: Bear with me, it's a long one, but i hope it makes sense.