Launchlist, and How You Don’t Need Much to Launch Your Site
June 28, 2010There’s a new site that’s been being sent around for a few days now, Launchlist. There is one main issue with it: instead of focusing on why not to launch a new site, you should focus on why to launch a new site.
It’s far too easy to get bogged down in the details of what else do I need to launch a new site. Granted, when you have a major site already in production, that is a different scenario and you’re going to want to go through a full set of testing. However, when it’s something new, it’s easy to get distracted by things that ultimately will not matter.
The 28 items that Launchlist recommends are great items to accomplish with a site, and really should be part of every site. But, when it comes down to it, many things can be eventual goals. Like support for Opera and larger resolution testing. Sure, those things should be on the to-do list, and yes, I am a big fan of Opera, but the fact is it’s not a high percentage of users who will be affected, so is it really worth delaying a launch because of that?
In the day and age of modern web development, it’s very easy to put out new releases when you need to update. The stringent testing should always be there, but in an agile environment, it’s easy to update something on the fly and roll out a new version for all users, so why give someone a reason to not launch?
