<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Making Websites Beta</title>
	<link>http://fadtastic.net/2007/01/11/making-websites-beta/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Fri, 25 Jul 2008 10:15:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Matt</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22579</link>
		<author>Matt</author>
		<pubDate>Thu, 11 Jan 2007 20:37:00 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22579</guid>
					<description>It seems like a lot of sites are labeling their product/page as "Beta" because they've seen it being done on some of the Web2.0 giants. In fact, quite a lot of "2.0" features are being mimicked by smaller sites that just don't need them (ie Javascript effects, unnecessary AJAX  etc).
Personally, I think it's just a nuisance.</description>
		<content:encoded><![CDATA[<p>It seems like a lot of sites are labeling their product/page as &#8220;Beta&#8221; because they&#8217;ve seen it being done on some of the Web2.0 giants. In fact, quite a lot of &#8220;2.0&#8243; features are being mimicked by smaller sites that just don&#8217;t need them (ie Javascript effects, unnecessary AJAX  etc).<br />
Personally, I think it&#8217;s just a nuisance.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Trevor</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22584</link>
		<author>Trevor</author>
		<pubDate>Thu, 11 Jan 2007 21:27:54 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22584</guid>
					<description>HAHA, so is it OK for me to make put a BETA icon on my site?? &lt;a&gt;http://trevordavis.net&lt;/a&gt;

I'm trying to do all of the content for my site first and get the whole structure setup. Then I am going to work on the design.

That damn beta icon irritates me too.</description>
		<content:encoded><![CDATA[<p>HAHA, so is it OK for me to make put a BETA icon on my site?? <a>http://trevordavis.net</a></p>
<p>I&#8217;m trying to do all of the content for my site first and get the whole structure setup. Then I am going to work on the design.</p>
<p>That damn beta icon irritates me too.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22589</link>
		<author>Johan</author>
		<pubDate>Thu, 11 Jan 2007 21:55:32 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22589</guid>
					<description>beta in webdesignland here is synonym to a broken link, broken content, broken presentation. It scares users.</description>
		<content:encoded><![CDATA[<p>beta in webdesignland here is synonym to a broken link, broken content, broken presentation. It scares users.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22632</link>
		<author>David</author>
		<pubDate>Fri, 12 Jan 2007 01:17:22 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22632</guid>
					<description>I think I am guilty for some of this "beta" stuff, but by the same token - when I use the term I actually have a design/site that is unfinished (AND still being worked on).

But, I guess I fail in letting users know WHAT is beta in it. :)</description>
		<content:encoded><![CDATA[<p>I think I am guilty for some of this &#8220;beta&#8221; stuff, but by the same token - when I use the term I actually have a design/site that is unfinished (AND still being worked on).</p>
<p>But, I guess I fail in letting users know WHAT is beta in it. :)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Teskey</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22714</link>
		<author>Steven Teskey</author>
		<pubDate>Fri, 12 Jan 2007 06:14:41 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22714</guid>
					<description>Trevor, I wish more people were as smart as you are.</description>
		<content:encoded><![CDATA[<p>Trevor, I wish more people were as smart as you are.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22752</link>
		<author>Andrew Faulkner</author>
		<pubDate>Fri, 12 Jan 2007 09:07:07 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22752</guid>
					<description>Nice methodology, Trevor.

Johan, I'd still say that beta is important, it's how one goes about it that decides whether it's worthwhile or pointless.

David, interesting. Do you (or anyone for that matter) think that a design can be in beta then? Or the functionality? Or both?</description>
		<content:encoded><![CDATA[<p>Nice methodology, Trevor.</p>
<p>Johan, I&#8217;d still say that beta is important, it&#8217;s how one goes about it that decides whether it&#8217;s worthwhile or pointless.</p>
<p>David, interesting. Do you (or anyone for that matter) think that a design can be in beta then? Or the functionality? Or both?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Abhijit Nadgouda</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22757</link>
		<author>Abhijit Nadgouda</author>
		<pubDate>Fri, 12 Jan 2007 09:58:12 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22757</guid>
					<description>Just coming up with reasons, one reason can be that it is difficult for the sites to come up with traffic prediction, and hence requirements to handle it. The beta stage can be used to get a feel of it and then incorporate that.

Of course, the beta also justifies if the site goes down unexpectedly ;-)</description>
		<content:encoded><![CDATA[<p>Just coming up with reasons, one reason can be that it is difficult for the sites to come up with traffic prediction, and hence requirements to handle it. The beta stage can be used to get a feel of it and then incorporate that.</p>
<p>Of course, the beta also justifies if the site goes down unexpectedly ;-)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Tammie Lister</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22792</link>
		<author>Tammie Lister</author>
		<pubDate>Fri, 12 Jan 2007 14:25:18 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22792</guid>
					<description>I studied software engineering and in those terms 'beta' means non public. I always have found it odd to apply the word beta to something 'live' and never advise a client to do it. To me beta always will be a testing process NOT a live site. The beta fad is really just that to me. It always makes me think of things like 'too lazy to full test'. There are arguments saying it's useful for testing and trying - why not have a private beta - much more elegant in my thoughts.</description>
		<content:encoded><![CDATA[<p>I studied software engineering and in those terms &#8216;beta&#8217; means non public. I always have found it odd to apply the word beta to something &#8216;live&#8217; and never advise a client to do it. To me beta always will be a testing process NOT a live site. The beta fad is really just that to me. It always makes me think of things like &#8216;too lazy to full test&#8217;. There are arguments saying it&#8217;s useful for testing and trying - why not have a private beta - much more elegant in my thoughts.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: olandesina</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22801</link>
		<author>olandesina</author>
		<pubDate>Fri, 12 Jan 2007 15:49:11 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22801</guid>
					<description>I saw a gamma site the other day... ah yes... it's flickr! Web2.0 giants are evolving. Soon we will get to the web 3.0 fase!!</description>
		<content:encoded><![CDATA[<p>I saw a gamma site the other day&#8230; ah yes&#8230; it&#8217;s flickr! Web2.0 giants are evolving. Soon we will get to the web 3.0 fase!!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Matt</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22883</link>
		<author>Matt</author>
		<pubDate>Fri, 12 Jan 2007 22:15:15 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22883</guid>
					<description>I personally have always interpreted "beta" to mean a sort of testing phase. To me its where you have mainly what you set out to do, but there still needs to be some adjusting to get it just right. Maybe more features, maybe tweaking some, but not things you knew before the release.

Tammie: I think the Web and and Software Engineering are on two totally separate wave lengths when it comes to "beta testing." With software you can't sell it and then take it back and fix it, however with a website (granted its not an e-commerce site or anything like that) you can always change things along the way without effecting much, especially blogs.

Either way I don't necessarily think it means an unfinished stage, more of a way to improve through the comments and evaluation of others.</description>
		<content:encoded><![CDATA[<p>I personally have always interpreted &#8220;beta&#8221; to mean a sort of testing phase. To me its where you have mainly what you set out to do, but there still needs to be some adjusting to get it just right. Maybe more features, maybe tweaking some, but not things you knew before the release.</p>
<p>Tammie: I think the Web and and Software Engineering are on two totally separate wave lengths when it comes to &#8220;beta testing.&#8221; With software you can&#8217;t sell it and then take it back and fix it, however with a website (granted its not an e-commerce site or anything like that) you can always change things along the way without effecting much, especially blogs.</p>
<p>Either way I don&#8217;t necessarily think it means an unfinished stage, more of a way to improve through the comments and evaluation of others.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Tammie Lister</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22925</link>
		<author>Tammie Lister</author>
		<pubDate>Fri, 12 Jan 2007 23:39:23 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22925</guid>
					<description>The thing is web = development at the core. So why should you be any less professional about it if you are in any form serious? If it doesn't work why call it beta and make live? I think it only taints the quality. The difference is when it comes to the use of websites or just a few non functional errors? Change does not equal putting something in beta. Beta is a borrowed term with marketing spin that is now often (sadly) used as an excuse to not go through testing and just release and hope - only removing the beta when either web 2.0 unicorns have left the building OR when you get venture funding. Software engineering and web aren't seperate wave lengths one is part of the other to a huge extent now in both methodology and process - mainly because of the shift towards web as application. It is also a point that Software Engineering even when I studied it didn't mean just software it actually is an educational term for programming in many organisations. I majored in web development through it so the processes are real world.</description>
		<content:encoded><![CDATA[<p>The thing is web = development at the core. So why should you be any less professional about it if you are in any form serious? If it doesn&#8217;t work why call it beta and make live? I think it only taints the quality. The difference is when it comes to the use of websites or just a few non functional errors? Change does not equal putting something in beta. Beta is a borrowed term with marketing spin that is now often (sadly) used as an excuse to not go through testing and just release and hope - only removing the beta when either web 2.0 unicorns have left the building OR when you get venture funding. Software engineering and web aren&#8217;t seperate wave lengths one is part of the other to a huge extent now in both methodology and process - mainly because of the shift towards web as application. It is also a point that Software Engineering even when I studied it didn&#8217;t mean just software it actually is an educational term for programming in many organisations. I majored in web development through it so the processes are real world.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Christian Watson</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22941</link>
		<author>Christian Watson</author>
		<pubDate>Sat, 13 Jan 2007 00:31:50 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-22941</guid>
					<description>I'm okay with something being beta and public, but what drives me nuts is when something seems to stay in perpetual beta - or even &lt;a href="http://www.measuremap.com/" rel="nofollow"&gt;Alpha&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I&#8217;m okay with something being beta and public, but what drives me nuts is when something seems to stay in perpetual beta - or even <a href="http://www.measuremap.com/" rel="nofollow">Alpha</a>.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: kabari</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-23023</link>
		<author>kabari</author>
		<pubDate>Sat, 13 Jan 2007 05:13:28 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-23023</guid>
					<description>&lt;blockquote&gt;* “All the cool kids do it so it must be a good thing to do.” ~ I think this is the most common reason for putting something into beta. It’s also the most pointless. There isn’t a goal in this.&lt;/blockquote&gt;

you could say this for everything associated with the buzz word "web 2.0" haha</description>
		<content:encoded><![CDATA[<blockquote><p>* “All the cool kids do it so it must be a good thing to do.” ~ I think this is the most common reason for putting something into beta. It’s also the most pointless. There isn’t a goal in this.</p>
</blockquote>
<p>you could say this for everything associated with the buzz word &#8220;web 2.0&#8243; haha</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ben Rogerson</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-23335</link>
		<author>Ben Rogerson</author>
		<pubDate>Sun, 14 Jan 2007 15:20:18 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-23335</guid>
					<description>In my opinion, I think a website that's been launched for the public eye should be past the 'beta' version. After beta is when when the site goes live and have been properly tested with a small group of users. If a site absolutely must be released prior to full bug testing then the current bugs should be acknowledged.

I'm making &lt;a href="http://www.benrogerson.com.au" rel="nofollow"&gt;my site&lt;/a&gt; much the same as Trevor from response 2.
The content was created first without CSS and all along, displayed a large message telling users what's going on and when the site will be launched. It's always a good thing to let your users know what's happening :)</description>
		<content:encoded><![CDATA[<p>In my opinion, I think a website that&#8217;s been launched for the public eye should be past the &#8216;beta&#8217; version. After beta is when when the site goes live and have been properly tested with a small group of users. If a site absolutely must be released prior to full bug testing then the current bugs should be acknowledged.</p>
<p>I&#8217;m making <a href="http://www.benrogerson.com.au" rel="nofollow">my site</a> much the same as Trevor from response 2.<br />
The content was created first without CSS and all along, displayed a large message telling users what&#8217;s going on and when the site will be launched. It&#8217;s always a good thing to let your users know what&#8217;s happening :)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-23343</link>
		<author>Johan</author>
		<pubDate>Sun, 14 Jan 2007 16:57:58 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-23343</guid>
					<description>&lt;blockquote&gt;
The content was created first without CSS and all along, displayed a large message telling users what’s going on and when the site will be launched.
&lt;/blockquote&gt;

Why not apply already basic font styling for links, headings and text?</description>
		<content:encoded><![CDATA[<blockquote><p>
The content was created first without CSS and all along, displayed a large message telling users what’s going on and when the site will be launched.
</p>
</blockquote>
<p>Why not apply already basic font styling for links, headings and text?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ben Rogerson</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-24072</link>
		<author>Ben Rogerson</author>
		<pubDate>Wed, 17 Jan 2007 02:53:50 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-24072</guid>
					<description>&lt;blockquote&gt;Why not apply already basic font styling for links, headings and text?&lt;/blockquote&gt;

It's a plain site that is built up over time. But yes, I got around to the typography fairly early in the design.</description>
		<content:encoded><![CDATA[<blockquote><p>Why not apply already basic font styling for links, headings and text?</p>
</blockquote>
<p>It&#8217;s a plain site that is built up over time. But yes, I got around to the typography fairly early in the design.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jewschool &#187; Blog Archive &#187; Jewish Coaltion for Service Shoots, Misses with JSoN</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-24185</link>
		<author>Jewschool &#187; Blog Archive &#187; Jewish Coaltion for Service Shoots, Misses with JSoN</author>
		<pubDate>Wed, 17 Jan 2007 14:48:47 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-24185</guid>
					<description>[...] The site&#8217;s pretty barren currently &#8212; I think I might be among the first dozen or so people to have signed up. It&#8217;s also in beta, like everything else these days, so I don&#8217;t want to be too judgmental. Nonetheless, a precursory glance leaves me skeptical about the site&#8217;s value &#8212; and, I swear, not just because I&#8217;m working on a social networking project of my own. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The site&#8217;s pretty barren currently &#8212; I think I might be among the first dozen or so people to have signed up. It&#8217;s also in beta, like everything else these days, so I don&#8217;t want to be too judgmental. Nonetheless, a precursory glance leaves me skeptical about the site&#8217;s value &#8212; and, I swear, not just because I&#8217;m working on a social networking project of my own. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Devlounge &#124; Custom Reading Containers</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-25125</link>
		<author>Devlounge &#124; Custom Reading Containers</author>
		<pubDate>Mon, 22 Jan 2007 03:41:33 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-25125</guid>
					<description>[...] In all honesty, I've only tested out the script in Firefox 2.0, IE 6, and Opera 9. I should have labeled the script as a beta, but I'm taking Andrew Faulkner's advice and leaving the beta out of it. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] In all honesty, I&#8217;ve only tested out the script in Firefox 2.0, IE 6, and Opera 9. I should have labeled the script as a beta, but I&#8217;m taking Andrew Faulkner&#8217;s advice and leaving the beta out of it. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Nilesh Gohil</title>
		<link>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-88535</link>
		<author>Nilesh Gohil</author>
		<pubDate>Sat, 08 Sep 2007 14:30:33 +0000</pubDate>
		<guid>http://fadtastic.net/2007/01/11/making-websites-beta/#comment-88535</guid>
					<description>Regarding the Beta argument...My website was originally launched in 2006. For the last few months I have been redesigning it for a relaunch this year. It has reached a certain phase in the design where the functionality is almost there and needs testing in its web environment. I have tested it as far as I can.&#160;I have launched the site in its 'beta' state and expect people to use it and understand its in its testing state. I have also placed a 'Report a Problem' link on all the pages including the homepage for users to use and identify and errors. And people have used it.This is what beta means to me. A prelaunch testing phase to try it out with real users. You'd be amazed at what people will point out in the testing phases. It can be a real eye opener. This makes sure that the actual launch is tried and trusted by your users with all their requirements met.I love live Beta testing. It benefits everybody.http://www.publicangel.com&#160;</description>
		<content:encoded><![CDATA[<p>Regarding the Beta argument&#8230;My website was originally launched in 2006. For the last few months I have been redesigning it for a relaunch this year. It has reached a certain phase in the design where the functionality is almost there and needs testing in its web environment. I have tested it as far as I can.&nbsp;I have launched the site in its &#8216;beta&#8217; state and expect people to use it and understand its in its testing state. I have also placed a &#8216;Report a Problem&#8217; link on all the pages including the homepage for users to use and identify and errors. And people have used it.This is what beta means to me. A prelaunch testing phase to try it out with real users. You&#8217;d be amazed at what people will point out in the testing phases. It can be a real eye opener. This makes sure that the actual launch is tried and trusted by your users with all their requirements met.I love live Beta testing. It benefits everybody.http://www.publicangel.com&nbsp;</p>
]]></content:encoded>
				</item>
</channel>
</rss>
