My first experience with Beta software was Windows “Chicago” which would become Windows 95. I can say it felt pretty cool for 20 something me to be running an early build of Windows long before the general public had access to it.
Flash forward to the year 2000 and I’d be using beta software almost every day while preparing wireless devices for release. Back then you were pretty excited when you found a bug. 15-20 bugs were pretty common in the average product back then and most were fixed prior to launch. This was a good thing since the concept of “over the air” updates was just a gleam in a manufacturer’s eye in those days.
Time marches on as it always does. With the ubiquity of the Internet patching software for your connected devices is the new normal. As the complexity of connected devices continues to increase the number of bugs within the software will continue to climb. The number of security issues will also continue to climb in lockstep.
It’s beginning to feel like every software product we currently rely on is always in Beta, isn’t it?
Like it or not the idea of a perfect product is dead. As a developer, you must accept that you have to release your product at some point. With the rapid pace of software development cycles today you risk having your launch “hype” stolen by a competitor if your date slips.
As a user, we have a role in this too. We can no longer just assume that every feature will work out of the box. It is important to do research on a product before you buy and make sure that the key features you need are working. More importantly, working as you expect. If a purchased piece of software isn’t working as you intended you must report the issue to the developer to get them addressed.
This isn’t entirely limited to software either. By the end of this year folding screens on Smartphones will be available from at least 2 major manufacturers. Early buyers of these devices will be essentially paying Beta testers. 20 something me would love to be one of the first to get his hands on these devices. 40 something me says “Not for my $3000 CAD.”
It would be easy to be cynical about our software update driven future but, I think I’ll embrace it. No matter how many eyes you have looking at your product before it launches you can’t catch everything. Some of the most unique and challenging issues that I ever encountered were in a post-launch setting. Customers had created use cases that surprised everyone in the room.
Get your software out to the public in Beta form as quickly as you can. It helps your customers feel like they are are a part of the process. Find ways to reward them for finding issues you missed. It doesn’t have to be large sums of money. Maybe some unique Merch that makes them feel like they are a part of the team and helps build your brand too!R
NoShade's 