ship69 wrote:In general unless really large structural changes are involved, the modern method is to solicit as much user feedback as possible, to listen to it very carefully, to deliberately not follow quite a lot of it, to have numerous short development cycles, to see how the introduction of new features affects user various metrics of behavior including Net Promoter Score and of course sales, and to remove as much complexity as possible if users in fact respond negatively to the new features. Google "The Lean Startup" business movement for further info.
Numerous short development cycles are indeed very common for web-based software, but neither Scapple nor Scrivener is web-based.
For more traditional, locally installed software, each new release imposes support and learning costs on both the user and the vendor. If the users don't like the new features, they will insist on reverting to the old version, and there's no good way to force them to switch. (Witness the number of users still running Windows XP.) Even if the users do like the new features, they will still cause some degree of confusion, leading to additional support queries.
Moreover, most users don't want to be beta testers, they want to get work done. They're perfectly happy to wait for months or years between versions, provided the current version fits their needs reasonably well. I'm sorry to hear that Scapple does not appear to meet yours.
PS FWIW, the lean startup model does not appear to be universally acclaimed. http://www.johnffinneran.com/blog/fat-s ... he-lessons