I just built and released WebnoteHappy 1.3.0 beta 8. I added support for DEVONagent for all you DEVONfans out there. Thanks to Eric of DEVONtechnologies for helping out.
Also, I promoted Command-E to be Edit Webnote, and demoted Edit > Find > Use Selection for Find to Command-Shift-E.
I’m curious – what do people think of the public beta process? That is, versus completely a private beta, or private betas for 80% and public betas at the end, or even a completely beta-less app that springs forth from the head of its creators? I personally like betas, but then again I love new technology when I can get my hands on it.
I like very much the model that follows Textmate with its bleeding edge betas: not too much or too little updates (from once a week to once a month), and 4 or 5 new features and bug squashes with every release.
Using the Sparkle framework also helps, I feel nice when I restart Textmate (or any other app which uses Sparkle) and says “new update available!” and does its thing automatically :)
I enjoy using software that has a public beta process, not only for access to new features and fixes but also as an indicator of the health and future of the product.
I also agree with the point Robert makes: making frequent updates is an indicator of your product’s health.
ditto with oscar.
Application menu can be a little clutterless. “Buy…” and “Register…” can be one line.
And, “Check for updates”? Most people seem to use “check at startup”. Or, making it under Help would be another idea.
Please, oh please – implement “suggested tags” when adding new bookmark to delicious and you will have a new & happy customer!