Comments
9 comments
-
Dear dwainew,
Thanks for your feedback. May I ask if you think the beta should have no time limit? If so, given that Red Gate betas generally support quite a significant amount of functionality, what would be the driving incentive to buy the full version when it comes out?
If you have any suggestions in this arena I'll see that they're considered for future betas with which I'm involved.
Regards,
Dan
Dan J Archer
SQL Dependency Tracker Project Lead -
Perhaps in place of the 14 days, you could hard-wire the Beta to expire the day before the product is projected to go live...
From the feedback you've had so far, you can see that there's no tool like it on the market or in freebie-world. You're highly likely to reap a bunch of orders on day 1. Until then, the tool is very usable as-is and would be a great one to have in our pockets until "the great day". Goodwill, and all that... -
I agree with a longer trial period for beta products. Since the beta expired, I've been hunting the internet for a similar tool. If the beta lasted until the release, I wouldn't be looking for a competitors product. :?
-
Dan,
Of course you need a time limit, but setting it the same as that of a full release version is pretty restrictive, especially when it expires even before the release date! This is the first instance I've ever seen that situation.
Your first Beta had no time limit, right? At least I didn't notice, because I ran it, liked the concept, spent a few days playing and commenting on the forum, and then got board and forgot about it till Beta 2.
If you're concerned about the Beta 2 harming sales, make it a time limit that extends beyond the projected release date by 30 or 45 days...
It's not going to kill your sales, as those that are using it often are GOING TO BUY THE REALEASE!! Those that don't weren't going to buy it anyway so an extra month of use is irrelevant to red-gate.
But then again, why would someone bother beta testing a product they have no interest in using? And, why would you ever want to treat beta testers just like some user trying a demo? They are spending their time HELPING you with a product that, by definition, isn't ready for prime time. If you think you can release a working product that fully solves the majority of users' needs and has no bugs, based solely on developers' opinions, I've got some land to sell you in Florida!
Has red-gate learned nothing from MS's new approach using CTPs and "interactive" product development? -
Hello all,
Some good points well made there.
If any of our beta users would like to extend their trial, please private message me on this board and I will reply to arrange this for you.
Regards,
Dan
Dan J Archer
SQL Dependency Tracker Project Lead
Red Gate Software -
I think that the lack of posts since the expiry period passed demonstrates that setting a 2 week expiry time was a bit restrictive. It means that you are no longer getting feedback! :-(
I'll be PMing to ask for an extension.
Thanks,
Alex Weatherall
TeleWare.com -
So what happened with the extension?
Besides the fact that I read in this group that company was going to keep it free. :? -
I've been granting free time extensions to those who've private messaged me. If you'd like one, please feel free to do so.
All the best,
Dan -
IMO, I think 14-day trials are too restrictive when found on development tools. Lord knows our overworked staff have very little time to spend on trying out tools. Oftentimes, we install and use once (not enough for decision-making) maybe twice before time runs out. I mean, seriously, there is higher priority actual work to do!
Counterpoint: Many consultants do a lot of short-engagement work with trial tools that last 30+ days. They keep re-installing trial software on new systems...
- alphadog
Add comment
Please sign in to leave a comment.
Don't you think a 14 day "TRIAL" is a little harsh for a Beta version of software? What's the logic behind that decision? We are users who are willing to invest the time to download it, install it, figure out how it works (without any documentation whatsoever), and then start reporting errors and omissions to you. Obviously, anyone willing to invest this kind of time is interested in helping make the product as useful and functional as possible and will most likely buy it later if the end result is worth buying. Putting a restrictive timeout on such a release is a slap in the face to your users. Don't you get it?
As far as I can tell, the production release isn't even out yet, but my Beta will expire tomorrow?? OUCH!!!