That depends. What's fantastic feature for one, others don't care
about at all. Upgrading is a choice. Not upgrading is a good choice
if the version you purchased works well for you (I for one admire all
the great features, but only use minor part of the feature set)
> To be completely honest the development of MLO has been
> sluggish.
Sluggishness depends on what are you comparing with. I'm loyal to
software with new release every 2 years. And I was spoiled by another
developer who at one point kept releasing new versions almost if not
every week (for Win, Linux and BSD at same time).
Just looked into change-log, and the time is 9-10 months from the
last major version (not counting the bugfix release in the meantime).
Well yes, for one thing, in the past (2005,2006) development seemed
to move way quicker (counting by the time of releases, not by source
code lines or any other better measure)
> Fair enough, I'm not a developer and so do not fully
> appreciate the complexity of the development process.
I'm only mildly acquainted with what's behind the curtain, from my
limited knowledge I think the filtering system and the related
changes must have been fairly complex and worthy to be called major
release.
> However, if
> users are expected to pay for every new release they should be offered
> a set of new features that's really worth paying for. And at a
> schedule that's better than 1 major release every 3 years.
3 years? But major releases are not by the number (1.x, 2.x).
Numbering has little to do with it. I'm sure you have seen or used
applications where they are for few years still in 0.x, yet keep
adding new major features. They just use different numbering system.
Here IMHO 1->2 doesn't reflect that it has now twice the features the
1.x had. Features were being added all the time into 1.x, and now
came the time to ask for an upgrade fee, after all, at some point
most developers do so.
Andrey could keep all the features for himself and only to introduce
them at one time in the 2.x version, so that we would become
thunderstruck and eager to upgrade, I'm sure at that time we would be
rightfully complaining about the 3year release time, yet we would
probably be sitting awestruck by all the awesome improvements and
ready to upgrade without objections.
But we would have missed the 3 years of free updates in the meantime!
Yeah they seem minor if you spread them over 3 years one by one.
> I may be completely wrong but it seems like the development team
> consists of 1 member (yourself) and even the only member doesn't work
> on the product full time.
Sorry but that's good argument only for sake of arguing.
Andrey is upfront about that.
95% of the shareware companies out there are one-man show that the
developer runs after the working hours. Yes, many of them have sales,
support, marketing and more departments, but that's just on the web.
Website can take anything.
Moreover he isn't the only guy working on it, there are other people
on the contract. I'm not fully acquainted but I believe Oleg (PPC
version developer) is not the only other developer besides Andrey.
> However, knowing I'm paying for somebody who's not fully
> committed to the product.
Full time on the product is not equivalent of fully committed to the product.
At least not in the shareware world.
> And decide not to upgrade.
Absolutely ! The upgrade is not mandatory.
> 6000 people. Even if only half of them have to pay the upgrade fee
> that's $90,000 in upgrade charges.
Well numbers look nice in a simple calculation, but I wouldn't be daring to put out an estimate.
Many people use the free version. Some subscribed shortly while
testing (and not many people unsubscribe after leaving the
group....they just stop visiting). Some are subscribed under more
addresses. Some just keep watching new developments (waiting for
feature x). Some are spammers.
And this is todo software. Similar to self-help books. Some people
buy it as yet another magical remedy to all their problems, and stop
using after a week.
That all shall be considered.
> Ok, so that is a rant and I realize it may be one founded on incorrect
> assumptions.
Well..you are definitely entitled to an opinion and welcome to air it here on the forum.
> But bear in mind that I'm probably not the only person who'll think
> to himself " whoa! So I have to pay $30 again..? Is it justified? I
> guess I'll just stick to the latest beta".
But that happens all the time, with all the software.
Simply there is always someone for whom the upgrade doesn't seem
reasonable, due to many valid reasons.
> but maybe it's worth writing a post
> explaining what exactly it is we're expected to pay for
http://www.mylifeorganized.net/products/my-life-organized/change-log.htm
> how the money
> will go towards improving the product
That would be real nice from Andrey, but my phone company doesn't do
that, Microsoft doesn't do that, not even my government with the
taxes they collect from me.
> getting extra team members to work on the application (if it's true)
I guess there are some already.
> I think that could go a long way towards making some of the users
> less p***d off.
That's right, the better communication towards the users, the less of them p***d.
Tom
I can't agree more.
Part of thing is that the new features delivered, are worthy to some,
yet not worthy of bother for others.
There is still the choice to keep the old version and only upgrade
when the new features that you can justify paying for are delivered,
or when you feel that enough effort was made already.
I know I'm sounding stupid/simplistic. But I feel part of this thing
is driven by emotions and people momentarily forget that they are not
required to upgrade.
And I know from my own experience that it's really hard to resist
form upgrading, even if you don't need the new features. I admit I
keep checking for new updates to products I didn't use in a
year....because I feel I want the new version.
Yet it's so liberating experience NOT to upgrade if one doesn't
really need it.
> The beta releases can not be counted in because they are part of the
> development process.
True.
> help the development and at the end of their effort they are met with
> this(in my own words):"Now that you all helped with the product
> development, pay me."
Beta testing is voluntary.
(It's probably driven by the same desire that's the upgrading driven
by - people want to have their hands on the "latest thing").
Still kudos to all beta testers and hats off, particularly before the
active ones (as many beta testers are rather passive, just driven by
the desire to have the latest toy).
> I don't want to reduce what the developer makes, I would like to
> request that license fees are charged based on what is delivered to
> us, paying customers, not based on how long the developer has taken to
> add some features.
Same for me. It's good to have an open discussion.
In my book what is delivered is a perceived value by the user. Whether the price is right or not, is up to the user.
With the software, when you have paid, it was say " for version 1.4 + 12 months if any updates within that period".
Do you have some suggestions as for what shall be a better road for Andrey to take?
I feel the only way to be 100% transparent is to put out a release schedule for next 2-3 years, clearly indicating major milestones and when upgrade fees will be requested, yet it's probably unrealistic due to impossibility to predict how long coding takes, and due to competition and similar reasons.
Another way is a timed license, as in "$20 per year". (Not that I like it myself, quite opposite.)
Or maybe not waiting 3 long years before proclaiming new major number
version, but perhaps keeping the current more or less regular
development progress (eg. 1-3 updates per year), and asking for an
update fee every year, but significantly smaller update fee than this
one.
Some more and better ideas?
PS. This is based on my understanding that it's hard to judge whether
the value delivered is enough - it's enough for some, yet not by far
for others, that's unavoidable though and rather subjective.
>
> I think when one looks at this one can see it fair enough.
No, it isn't - and I will tell you why, simply because the BETA has
been of v1 not of v2
If they had said, up front, that the new version was going to be V2
then that would have been fair enough - we'd have had warning of the
paid upgrade and, in my case, would simply have ignored the beta
completely pending the release of v2 (at which point I'd probably
still have continued with V1 which - as I have said before - does
enough for me).
Again, as I've said before, the version after 1.9 is 1.10 not 2.0 and
its this that I find disapointing.
--
Murph
I wouldn't say it teaches you better self-discipline as such, but it does give you a strategic program for overcoming procrastination. Uses a lot of reverse psychology to get you to want to work but at the same time enjoy guilt-free play. There is a Yahoo discussion group about the Now Habit, and the author is a member.
http://groups.yahoo.com/group/TheNowHabit/
Or check out Do It Tomorrow (DIT), by Mark Forster. This implements the function of a Will-Do/Closed List rather than an open todo list ala GTD context list.
There is also a Yahoo discussion group on DIT, again the author is a member.
http://groups.yahoo.com/group/do_it_tomorrow/
All the best
Steve
Apparently we learned different math somewhere along the way 1.9 >
1.10. Yes I've seen some products (most open source) that use .xx
version numbering scheme - but its usually to avoid having a 1.0
release which people expect to be stable.
I also believe if you dig back through the messages on this forum that
the arrival of 2.0 has been discussed more than a few times. On at
least one occaision I recall Andrey chiming in with a rough outline of
his plans.
So while I appreciate your beef I believe you're wrong two key points of fact.
Cheers
Mark
----------------------------------------------------------------------
Blog: http://www.notesfromatooluser.com/
One Year of Scrum: Lessons Learned
http://www.notesfromatooluser.com/2007/10/one-year-of-scr.html
Aperture vs. Lightroom - best comparisons
http://www.notesfromatooluser.com/2007/02/aperture_vs_lig.html
Customer Retention Department - Vonage Customer Service Sucks
http://www.notesfromatooluser.com/2007/06/customer_retent.html
Tom
It is, if we're discussing maths (-: however we're not, we're
discussing application version numbering schemes which tend to be
along the lines of Major.Minor.Revision and sometimes .build too.
It has to be said that Numbering for betas is a pain - but even so
labeling a beta as 1.n and then releasing it as 2.0 is, erm, perhaps
not the ideal (something for future reference).
Can I be clear about a couple of things - I don't object to paid
upgrades for major version changes and I do think that the filtering
and other changes justify describing the new release as a major
version change what I'm not happy about is being mislead (even if, as
I believe, it wasn't intentional).
--
Murph
> What the author of this post does
> not understand
If you're referring to me then I wish you wouldn't join the list of
participants that make bad assumptions about what I do and don't
understand - and further that you'd read what I'm unhappy about
(because its NOT the notion of paying for major version upgrades). If
you're not referring to me then ignore me (-:
--
Murph
Wow Andrey! Congratulations!
This is the kind of news I waited years to hear! :D
Task dependencies looking good, 2.0 looking good, MLO is really taking off.
Looks like we all have a lot to celebrate!!!
Best Regards,
Luciano Passuello
http://litemind.com
~Exploring ways to use our minds efficiently.
-----Original Message-----
From: myLifeO...@googlegroups.com
[mailto:myLifeO...@googlegroups.com] On Behalf Of Andrey Tkachuk (MLO)
Sent: Thursday, April 24, 2008 1:02 PM
To: MyLifeOrganized
Subject: [MLO] Re: MLO v 2.0 Upgrade charge - a joke?
Hi ALL,
Yes it was very important milestone for us and thanks to those why
support us!
I decided not to hide new functionality until final releases and
publish it in beta-s so that people who want to use it have this
possibility. It might be more clever decision to hide it until the
final release so that nobody disappointed with "no changes". But I
decided that it is more important to give people new cool features as
soon as possible since they need it. Even if the cost of this is to
get messages like this I am ready to answer them :-) MLO becomes
better because of this public beta-s policy also. I would hate if you
got FINAL releases with bugs and surprised changes you don't like. So
I will keep publishing beta-s for those who want to use them. There is
also a restricted group of beta testers who test the initial alpha
releases if there are critical changes which might affect stability.
Let me say that 2.0 has been published according to EULA. Many people
have been using MLO for 2-3 years already and this is the first paid
upgrade for them. The list of features is in the change log.
>what exactly it is we're expected to pay for
I think you pay for the new functionality already implemented after
1.9.1. If you like it and want to use it you upgrade to 2.0. If you do
not need it yet - you do not upgrade and use 1.9.1. The new features
better soon - see below why.
Wow - congrats Andrey that is just amazing.
Regards,
jimmo
PS. Hey man! He broke the President!
--
---------------------------------------
"Be more concerned with your character than with your reputation. Your
character is what you really are while your reputation is merely what others
think you are." -- John Wooden
---------------------------------------
Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info
--
---------------------------------------
"Be more concerned with your character than with your reputation. Your
character is what you really are while your reputation is merely what others
think you are." -- John Wooden
---------------------------------------
Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info