chocolat-public
chocolat-public copied to clipboard
atg
Remove the product from the sale, it is obsolete
they should withdraw the product ... I don't know if they accept purchases or not ... but for nothing it is an act of good faith ... they don't even answer ...
Maybe developer is working on a new version and don't have time/resources to answer.
I have sent many crash reports, bu there have been no updates published for three years. If the developers no longer have time to maintain it, perhaps source could be made available so we could fix it ourselves.
@borisyurkevich Nothing stops them from writing on the blog a simple sentence saying "Hey guys, sorry for the lack of updates, we're working on a new version, watch this space". It takes less than a minute to get that on their blog, so I'd say from the lack of any form of communication, this project is dead
@DannyJJK I never wrote a blog a post which takes less than 30 minutes to write, but that besides the point. I completely understand author of application who might not want to share anything until there's an update to ship. Such a post would be a commitment and huge burden. Developers have no obligations to work on new version or releasing app updates, and they are not obligated to share their plans. It's their choice to do so.
@borisyurkevich The blog post could be one or two sentences long, just a little "hey, we're still working on this, stay tuned", I know blog posts are usually longer than that, but if the developer is really busy then that will do. No developer is forced to do anything, and if this product was free then I wouldn't blame him, but it's a paid product and you have to ask yourself what are you actually paying for? If I pay for an application, it's because I want to see that developer succeed and reward him for his hard work, but I couldn't pay for an application that's no longer receiving updates.
It's easy to see the developer's general timeframe for releasing updates when there's a clear release notes page, which there is for Chocolat, and we can see that the developer always releases at least a few updates yearly. That doesn't mean to say that as soon as the developer hasn't released an update for a year it means the application is dead, but it's now been over 3 years. No news on the "Release notes + Blog" page, no news on the Twitter account. If there was at least some activity on Twitter or the blog to keep everybody in the loop and let us know that the project isn't dead I wouldn't mind the long wait. But the fact that there isn't anything signifies to me (and many others) that this project is dead.
You can believe what you like, but I've seen enough applications get abandoned to know the telltale signs. I hope you're right, and that the developer is planning something, but it really doesn't seem that way. The lack of communication won't hurt the consumer, it will only hurt the developer through significantly less purchases and also refunds when people find that the application they just purchased hasn't been updated in over 3 years without anything new in sight.
@DannyJJK I understand frustration of staying in the dark. You are right that it feels like a bad deal when you buy something and it gets abandoned. It's easy to check release notes before making a purchase, and if it's important for you that product gets updated, just choose something which is regularly updated. There's very rich Mac ecosystem with strong competition out there.
There's many developers and organisations out there with different communication styles. Some of them are open and share their plans in advance, but others, Apple included, never talk unless they have something finished to show.
The blog post could be one or two sentences long, just a little "hey, we're still working on this, stay tuned", I know blog posts are usually longer than that.
I agree that it takes very little time to type the words. Anyone can find a time for a short post. But in some cases it can take forever to figure out what to write. Even if it's one sentence, what it should be? And once you put something out there, you will feel forever obligated to fulfil a promise. It's better to not give people any hope at all, then promise something and break it later. Anything can happen, people get ill or die, projects get in legal trouble, personal circumstances can change, there can be dispute if there's more than one developer involved.