Larry,
Question. Say you make this, and it is great and the bugs are worked out. Everyone is using it and all letters are better. Two months go by. Now as more people use it, they will find ways to make it better. Some ways will benefit all, some will benefit only them. Doesn't matter, it's all good.
So, you are getting one suggestion a day. A tweak here and a change there.
How does a developer decide how to deal with this? For instance, will my small programs and complete access to the developer, I can email him with an idea and it is done in a day. But, if I write to Microsoft with a good idea, it may get in when Office 2007 upgrades to 2010.
Do you wait for the next version? Do you just come out with a quite update. Or can you do one-click web installs and just let people know a new version is available?
Also, say there is a checkbox at the top where if it is checked, the date shows in the letter. Unchecked, it doesn't. Say in the current version, it is checked by default, but someone emails you and says it would be better if it were unchecked by default, and their logic made sense. How do you know if you should change it? The change may make 100 people happy, but upset 200 people. You can't make preferences for every single feature, can you?
Just wondering.
