<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>studiojmc.com &#187; Bad Design Hall of Fame</title>
	<atom:link href="http://www.studiojmc.com/design-blog/category/bad-design-hall-of-fame/feed" rel="self" type="application/rss+xml" />
	<link>http://www.studiojmc.com/design-blog</link>
	<description>Design Blog</description>
	<lastBuildDate>Wed, 23 Jun 2010 21:13:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Adobe CS3: One man&#8217;s bloat is another man&#8217;s feature</title>
		<link>http://www.studiojmc.com/design-blog/abode-bloat.html</link>
		<comments>http://www.studiojmc.com/design-blog/abode-bloat.html#comments</comments>
		<pubDate>Mon, 24 Sep 2007 17:01:24 +0000</pubDate>
		<dc:creator>studioJMC</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[User Interface]]></category>

		<guid isPermaLink="false">http://www.designrefugee.com/design-blog/abode-bloat.html</guid>
		<description><![CDATA[I recently became involved in an interesting thread in the AIGA Design Education online discussion group. Basically the topic was the increasing complexity and bloating of design software. Here’s a few relevant comments from the discussion:]]></description>
			<content:encoded><![CDATA[<p></p><p>I recently became involved in an interesting thread in the AIGA Design Education online discussion group. Basically the topic was the increasing complexity and bloating of design software. Here’s a few relevant comments from the discussion:</p>
<p><em>graphicdavid started it off:</em></p>
<blockquote><p>“… it seems that Adobe is making the software increasingly<br />
complex, instead of just making it work better.</p>
<p>They seem to think that we all want cross-hybrids of their software.”</p></blockquote>
<p><em>from citizendesign</em></p>
<blockquote><p>“A number of years ago, Adobe seemed to be headed the other direction. Making things simpler and leaving features up to other developers to ‘plug-in’.”</p></blockquote>
<p><em>artgibel</em></p>
<blockquote><p>“As far as InDesign, you have pinpointed one of the reasons I still prefer teaching print production starting with Quark and moving to InDesign later.  I always tell students, the issues are the same in both programs; if your document is not set up properly for the printing process you are using, it will not print well. With InDesign, they have made it so much easier to make a mess.”</p></blockquote>
<p><strong>Here’s my thoughts:</strong></p>
<p>I can sympathize with the desire on the part of some designers for Adobe to “simplify” its software. Occasionally I fire up my Mac SE and long for the days when computing was simple. But would I actually trade my current Mac for an SE? Of course not! Neither would I trade Photoshop for MacPaint. I may not use all the features Photoshop CS3 offers but I certainly appreciate the features I do use.</p>
<p>Instead of moaning about bloat, why not try to come up with a list of the features you would like Adobe to REMOVE from their programs? I’m sure, if you could get the profession to agree, Adobe would be happy to offer stripped down “Designer” editions. Of course you’ll never get the profession to agree.  The fact is your “bloat” is another designer’s necessity.</p>
<p>I’m also shocked that anyone can suggest plug-ins as the answer to simplifying programs. Plug-ins don’t simplify the user interface or improve the user experience. While a well-designed plug-in can fit seamlessly into a program, it’s rare and the potential pitfalls are numerous including (but not limited to):</p>
<ul>
<li>Installations issues</li>
<li>Inconsistent user interfaces</li>
<li>Additional costs</li>
<li>Incompatibilities with other plug-ins or program updates</li>
</ul>
<p>Consider the nightmare of trying to maintain your suite of Adobe applications along with a set of “core” plug-ins. I’m willing to bet that, once a plug-in became a standard, you’d be among the throng clamoring for Adobe to make the functionality native.</p>
<p>I was also surprised by the kind comments for Quark. Perhaps things have changed since the days when I used XPress but back then the user interface was crap and the company was notorious for its lack of responsiveness to customer concerns. That’s the reason Quark has gone from having a stranglehold on page design software to being an also ran. Adobe, on the other hand, has created well-designed programs and been responsive to its customers.</p>
<p>And, speaking of responsiveness, we should admit that the true cause of program bloat is that we, the users, demand it. If we own Photoshop, we don’t want to buy Illustrator just to add one small bit of functionality, we want Adobe to add that functionality to Photoshop. That new functionality may be “bloat” and it may duplicate functionality already available elsewhere but as Photoshop users we’re grateful. Everyone else can feel free to ignore it.</p>
<p>Finally, simpler isn’t necessarily better. Sure it’s easy to do some bad things using InDesign but it’s also possible to stab someone with an X-acto knife. Neither action is the fault of the tool. There is a learning curve with any tool. It’s possible to ignore InDesign’s learning curve and produce substandard work but that’s not Adobe’s fault. Design professionals need to accept that the software learning curve now extends throughout their professional lifetime. The only alternative is obsolescence.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.studiojmc.com/design-blog/abode-bloat.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>800 by 600 pixel monitors: An endangered species</title>
		<link>http://www.studiojmc.com/design-blog/monitor-size.html</link>
		<comments>http://www.studiojmc.com/design-blog/monitor-size.html#comments</comments>
		<pubDate>Fri, 17 Aug 2007 14:40:55 +0000</pubDate>
		<dc:creator>studioJMC</dc:creator>
				<category><![CDATA[More...]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.designrefugee.com/design-blog/monitor-size.html</guid>
		<description><![CDATA[Back in June I mentioned being surprised by the low number of visitors to this site using 800 x 600 pixel monitors. At the time the exact number was zero. Well it's increased a bit since then. Now a whopping 0.67% of visitors here have the mini-monitors.]]></description>
			<content:encoded><![CDATA[<p></p><p>Back in June I mentioned being surprised by the low number of <a href="http://www.designrefugee.com/design-blog/wp-admin/post.php?action=edit&amp;post=19">visitors to this site using 800 x 600 pixel monitors</a>. At the time the exact number was zero. Well it&#8217;s increased a bit since then. Now a whopping 0.67% of  visitors here have the mini-monitors. In spite of that, I think I&#8217;ll still feel comfortable ignoring them when I get around to the redesign.</p>
<p>I still find those results a bit startling, so I decided to do a quick survey of a few other sites I manage. Here&#8217;s the results:</p>
<p><strong>Percent of users with 800&#215;600 monitors</strong><br />
Website: 2007 to date / for July 2007 (target audience)</p>
<p>SEOrefugee.com: 2.01% / 2.01% (search engine optimizers)</p>
<p>NetDetours.com: 10.31% / 7.07% (general interest)</p>
<p>TOONrefugee.com: 7.34% / 6.08% (general interest with focus on sports, computers, etc.)</p>
<p>Extrapolating (unscientifically) I&#8217;d guess that most sites have already reached the magic 10% level where it suddenly seems OK to ignore the resolution-challenged in their audience. And I wouldn&#8217;t rule out that most of them will be at the 5% level by the end of the year.</p>
<p>To help confirm my conclusions, I check five other sites whose information I can only share in a general manner. The highest concentration of the smaller monitors was 13%. Another site was right at the magic 10% level. A third was at 7% and the other two were below 5%.</p>
<p>So it looks like 1024 x 768 is the new 800 x 600.</p>
<p>It makes me feel old, I remember when 800 x 600 was the new 640 x 480.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.studiojmc.com/design-blog/monitor-size.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My favorite Google Search</title>
		<link>http://www.studiojmc.com/design-blog/favorite-google-search.html</link>
		<comments>http://www.studiojmc.com/design-blog/favorite-google-search.html#comments</comments>
		<pubDate>Fri, 08 Jun 2007 05:06:17 +0000</pubDate>
		<dc:creator>studioJMC</dc:creator>
				<category><![CDATA[Bad Design Hall of Fame]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.designrefugee.com/design-blog/favorite-google-search.html</guid>
		<description><![CDATA[&#8220;Untitled Document&#8221; is the default page title for web pages created in Dreamweaver and a variety of other web page editors. According to Google &#8220;about 32,900,000&#8243; with that title now populate the web. And, if you&#8217;re interested (which apparently few people are), according to Yahoo! the number is &#8220;about 44,700,000.&#8221;]]></description>
			<content:encoded><![CDATA[<p></p><p>&#8220;<a href="http://www.google.com/search?hl=en&amp;rls=en&amp;q=Untitled+Document&amp;btnG=Search" target="_blank">Untitled Document</a>&#8221; is the default page title for web pages created in Dreamweaver and a variety of other web page editors. According to Google &#8220;about 32,900,000&#8243; with that title now populate the web. And, if you&#8217;re interested (which apparently few people are), according to <a href="http://search.yahoo.com/search?p=Untitled+Document" target="_blank">Yahoo!</a> the number is &#8220;about 44,700,000.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.studiojmc.com/design-blog/favorite-google-search.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adobe CS3 Palettes</title>
		<link>http://www.studiojmc.com/design-blog/adobe-cs3-palettes.html</link>
		<comments>http://www.studiojmc.com/design-blog/adobe-cs3-palettes.html#comments</comments>
		<pubDate>Tue, 29 May 2007 21:38:17 +0000</pubDate>
		<dc:creator>studioJMC</dc:creator>
				<category><![CDATA[Bad Design Hall of Fame]]></category>
		<category><![CDATA[User Interface]]></category>

		<guid isPermaLink="false">http://www.designrefugee.com/design-blog/?p=6</guid>
		<description><![CDATA[From time to time we'll recognize significant accomplishments in bad  design with nominations to our Bad Design Hall of fame...]]></description>
			<content:encoded><![CDATA[<p></p><p><em>From time to time we&#8217;ll recognize significant accomplishments in bad  design with nominations to our Bad Design Hall of fame. The potential nominees are almost limitless and we invite Design Refugees to make their own nominations. And, just to be fair, DesignRefugee.com isn&#8217;t exempt. When we blow it, feel free to let us know.</em>I&#8217;ve been a fan of Adobe&#8217;s user interface design since Illustrator 1.1, about twenty years ago. Designing a usable and somewhat intuitive interface for graphics programs is a daunting challenge and few have done it as well as they have. Of course the task has gotten more difficult as new features have bloated my favorite programs. Still, especially considering some of the competing interfaces from the likes of Macromedia (before the takeover) and Microsoft, Adobe remains a leader. That&#8217;s why I&#8217;m so disappointed in the palettes Adobe has inflicted on Mac users with the CS3 bersions of Photoshop, Illustrator and Flash (apparently Windows users have been suffering through something similar for a while).<span id="more-62"></span><img src="http://www.designrefugee.com/design-blog/wp-content/picture-1.gif" align="right" alt="Photoshop User Interface" title="Photoshop User Interface" />Imagine you want to create a new layer in Photoshop. You head to the upper right corner of the Layers palette and click. Surprise, instead of displaying a menu, the palette disappears. That&#8217;s because Adobe has moved the minimize and close palette icons from their former location on the top left side of palettes – which happens to be their standard position for ALL Mac windows – and placed them directly above the pop-up menu icon. To make matters worse, the icons are excruciatingly small (shown here actual size and magnified 4x).I&#8217;m really trying to be more careful when activating these menus (I don&#8217;t really have any choice) but this is particularly annoying because there was no reason for the change. And, if the change was going to be made, why couldn&#8217;t Adobe have made the icons larger, added a bit of space between them, used stronger contrast or color to distinguish between the icons or all of the above? The answer, of course, is that in &#8220;standardizing&#8221; the Mac and Windows versions nobody really gave any thought to what is best for users.I&#8217;ve been at it two weeks and I still find myself making this mistake a few times a day. Given that my eyes and motor skills aren&#8217;t improving with age, I figure this &#8220;feature&#8221; will become a chronic annoyance.Is there any chance someone will write a plugin to move the close and minimize icons back where they belong or, better yet, that Adobe will undo this? Probably not but, just in case someone at Adobe is listening, here&#8217;s a reminder of how things used to be:
<p style="text-align: center"><img src="http://www.designrefugee.com/design-blog/wp-content/old-palette1.gif" style="float: none" alt="Old Palette" title="Old Palette" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.studiojmc.com/design-blog/adobe-cs3-palettes.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
