![]() While I can relate to that sentiment (Build it and they will come) to some degree, however the questions are always “Great for whom?” and “Will they recognize the greatness?”. This feature will be the game changer and will dramatically expand the user base. There is still a killer feature that I conceived during the early development of Duplicacy and haven’t been able to find time to implement since then. I think less of the target market because I strongly believe that when you build a great product users will naturally come. In any case, Duplicacy is a long-term project and I won’t call it an end until that killer feature is implemented. Certainly this will happen, I just don’t know how long it would take. My goal of course is to grow the business so that I can at least hire someone to help me. So my time on Duplicacy is limited, but it should become better once I got that one out.īusiness wise Duplicacy isn’t successful considering all the time I spent, but it is still sustainable in the sense that if the revenue (from all my projects) can remain at the current level I should be able to keep doing what I’m doing now. In addition, I have been ‘secretly’ working on a new project, not related to backup or sync, that I hope to release in a couple of months. There is almost no development work for them at this time, although customer support can be demanding from time to time. I have other projects such as Acrosync and Vertical Backup if you don’t know. I don’t know how much of their time is able to devote to this project and how successful it is economically, It’s a great discussion and thanks to for starting it, even though the style might have been a tad polemic. And I understand ’ concerns about stability, but I’m more concerned about that in regards to the engine than around some changes in the Web UI.Īnyway just my 2 cents. But again this of course depends on how much time can devote to Duplicacy. Also a faster update cycle would be desirable at least for non-critical UI-features, e.g. So I’d suggest to expand the current roadmap and add a section that shows those items that are intended for the upcoming release. But I hope at least some of that is still within reach, because I want Duplicacy to be successful in the long run (if for no other reason, that I bought lifetime licenses ). I don’t know how much of their time is able to devote to this project and how successful it is economically, so I’m not sure, if what I’m looking for is simply out of reach. And since a user interacts most with the software in the initial setup stage, flaws in polish become apparent very quickly (and might persuade a user to discard Duplicacy for a technically inferior, but more polished product). But unfortunately it does not quite have the polish that competing products have, even though those might be inferior in the core backup functionality.īut the polish is what sells (when your customer isn’t technically competent enough) to evaluate each product on the technical merits. Perhaps that “gearing” is not intended, because I’d think that more users (and thus money) might be found in the small business market. ![]() To me it seems right now to be geared primarily toward the enthusiast user, as it required a certain acquaintance with the OS to fix things, when they go out of whack. In the meantime I’m occasionally wondering what the target market and the future for Duplicacy really is. ![]() Obviously nobody owes me or any other user to adopt their suggestions. desirable quality-of-life improvements in April of 2020, but I’m not sure that many were adopted. I’ll post my ideas on the Feature category.Īnd I think that this is the core of the issue and I agree with them. The web GUI has some annoyances that I assumed the would be fixed sooner than later. Regarding the CLI, it seems pretty stable, and that was not the reason for the post. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |