I was content with my VersionTracker app. However, things change and CNET bought it - c'est la vie.

That being said, I would've assumed that the project lead would've had his crap in one sock. I'm not a luddite, so I think this is an innovative way of updating software. However, has anyone on the team actually used VersionTracker? I think "beta" is an overly optimistic term, and think this should still be in an alpha phase.

Point 1: Make your software, i.e. TechTracker, accessible. Where the 'f' can I download beta 3? If I'm not logged in then I either have to register or login. Once logged in I can't find a link, but I can still see the software list from one of my other Macs, which leads me to ...

Point 2: VersionTracker had the capability to differentiate which Macs needed updates. Why am I being told I need to update PostBox when I don't have PostBox on my 13" MacBook Pro? As a small business owner, I refuse to lug my 20" iMac around so TechTracker can somewhat work like it should.

Point 3: QC. Yes, it's beta, but beta is usually 1 step closer to RC. If you can't even see RC possibility then it isn't a beta. After submitting reports to CNET about how Business Card Composer isn't the Art Text app then I would've assumed it would've been fixed after a week, or maybe removed the app in question until someone figures out a fix for unassociated apps and links.

Point 4: Listen to your feedback. Sure I know I'm coming off harsh, and I'm sure people are more flowery with expressing their dislike, but a good developer would put their delicate emotions aside and look at the problem through the anger. I'm peeved because I was using something that worked and now everything is jacked, so common sense would dictate that I'm not happy.

Point 5: E-mail updates should let me know which computer's software needs updating. Nothing is more aggravating to see Speed Download needs to be updated and yet when I check the system I'm currently on is in fact updated, but the computer I hardly use might not be.

My suggestion would be to suspend TechTracker temporarily, accept the verbal abuse that will come with that. Get competent developers and project managers who work cohesively together, list what VersionTracker did and what TechTracker currently does so repeated mistakes aren't made, and set a goal for what TechTracker will be.

Next, develop a framework to build off of, i.e. at least get make TechTracker consistent on all platforms because a lot of people are multiplatform users, and make sure the updates work. After that foundation has been set then work on the bells and whistles, i.e. e-mail updates, etc.