<?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>Yostivanich &#187; Web Design</title> <atom:link href="http://www.yostivanich.com/category/communication/design/web-design/feed/" rel="self" type="application/rss+xml" /><link>http://www.yostivanich.com</link> <description>Surfing the web and hopefully learning something new every day</description> <lastBuildDate>Wed, 08 Sep 2010 17:20:41 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <atom:link rel='hub' href='http://www.yostivanich.com/?pushpress=hub'/> <item><title>Signal vs. Noise &#8211; Smiley: An app in 24 hours</title><link>http://www.yostivanich.com/2010/09/03/signal-vs-noise-smiley-an-app-in-24-hours/</link> <comments>http://www.yostivanich.com/2010/09/03/signal-vs-noise-smiley-an-app-in-24-hours/#comments</comments> <pubDate>Sat, 04 Sep 2010 04:48:06 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Programming]]></category> <category><![CDATA[Quick Posts]]></category> <category><![CDATA[User Experience]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[37signals]]></category> <category><![CDATA[Design]]></category> <category><![CDATA[project management]]></category> <category><![CDATA[usability]]></category> <category><![CDATA[user experience]]></category> <category><![CDATA[user interface]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1399</guid> <description><![CDATA[37signals builds an app to measure feedback of their customer support team.]]></description> <content:encoded><![CDATA[<blockquote><p>We talked about it for a bit and came up with this basic goal: Let’s make it really easy for our customers to quickly rate our customer service every time we talk to them. It’s not rocket science, and it’s not a breakthrough idea, but it wasn’t something we were doing. It was time we experimented with the concept. We’d write some software and try it out. We’d call the app Smiley.</p></blockquote><p>via <a
href="http://37signals.com/svn/posts/2550-smiley-an-app-in-24-hours" title="Signal vs. Noise &ndash; Smiley: An app in 24 hours">Signal vs. Noise &ndash; Smiley: An app in 24 hours</a>. 37signals shows how they went from concept to finished product in 24 hours. The great thing is that it&#8217;s a pretty simple app, but seems like a solid concept and well executed.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/09/03/signal-vs-noise-smiley-an-app-in-24-hours/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Borderleft Labs &#8211; Toucan CSS reset</title><link>http://www.yostivanich.com/2010/08/29/borderleft-labs-toucan-css-reset/</link> <comments>http://www.yostivanich.com/2010/08/29/borderleft-labs-toucan-css-reset/#comments</comments> <pubDate>Sun, 29 Aug 2010 08:14:42 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Programming]]></category> <category><![CDATA[Quick Posts]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[css]]></category> <category><![CDATA[css framework]]></category> <category><![CDATA[css reset]]></category> <category><![CDATA[style sheet]]></category> <category><![CDATA[webdesign]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1393</guid> <description><![CDATA[A very basic style sheet, good to use if you want to roll most everything on your but want to be sure all the simple stuff is covered.]]></description> <content:encoded><![CDATA[<blockquote><p>It is a reset stylesheet. Unlike Meyer’s or YUI’s, it not only removes the default styling of HTML elements, but also rebuilds the new generic rules for the typography, headings, paragraphs, lists, forms, tables etc. It’s light-weight, flexible and browser-friendly.</p></blockquote><p>via <a
href='http://borderleft.com/labs/' title="Borderleft Labs &ndash; Toucan CSS reset">Borderleft Labs &ndash; Toucan CSS reset</a>. I like it, just in-between a normal CSS framework and basic CSS rest style sheet.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/08/29/borderleft-labs-toucan-css-reset/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Drawar &#8211; Design The Experience: Expectations</title><link>http://www.yostivanich.com/2010/08/04/drawar-design-the-experience-expectations/</link> <comments>http://www.yostivanich.com/2010/08/04/drawar-design-the-experience-expectations/#comments</comments> <pubDate>Thu, 05 Aug 2010 04:21:05 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Communication]]></category> <category><![CDATA[Design]]></category> <category><![CDATA[Quick Posts]]></category> <category><![CDATA[User Experience]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[business]]></category> <category><![CDATA[marketing]]></category> <category><![CDATA[user experience]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1381</guid> <description><![CDATA[Set your customers up for an awesome experience by succeeding their expectations.]]></description> <content:encoded><![CDATA[<blockquote><p>Price isn&#8217;t always the first impression that one gets from an experience, but it is a key component on how expectations can be set for a person. A couple of weeks ago I flew Midwest Airlines and I didn&#8217;t know anything about them. They had the cheapest price flight so I went with them. Upon arriving at the terminal I saw they had different seats than Southwest which was right across the aisle. Their seats sucked and were uncomfortable. I always figured that all airlines had the same seats, but Southwest had lounge chairs that looked like you could sit down in them all day. Midwest had seats built for a three-year old.</p></blockquote><p>via <a
href='http://www.drawar.com/articles/design-experience-expectations' title="Drawar &ndash; Design The Experience: Expectations">Drawar &ndash; Design The Experience: Expectations</a>. If you set up your site for a bad expectation, the customer gets a bad experience.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/08/04/drawar-design-the-experience-expectations/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>52 Weeks of UX &#8211; Time to Delight</title><link>http://www.yostivanich.com/2010/07/27/52-weeks-of-ux-time-to-delight/</link> <comments>http://www.yostivanich.com/2010/07/27/52-weeks-of-ux-time-to-delight/#comments</comments> <pubDate>Wed, 28 Jul 2010 04:43:30 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Programming]]></category> <category><![CDATA[Quick Posts]]></category> <category><![CDATA[User Experience]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[apple]]></category> <category><![CDATA[computer science]]></category> <category><![CDATA[Design]]></category> <category><![CDATA[human computer interaction]]></category> <category><![CDATA[texas tech]]></category> <category><![CDATA[user experience]]></category> <category><![CDATA[ux]]></category> <category><![CDATA[webdesign]]></category> <category><![CDATA[webdevelopment]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1367</guid> <description><![CDATA[Let's focus on making great software that delights the customer, ok.]]></description> <content:encoded><![CDATA[<blockquote><p>How long does it take for a new visitor/customer to be delighted using your product or service?</p></blockquote><p>via <a
href='http://52weeksofux.com/post/866407309/time-to-delight'>52 Weeks of UX &ndash; Time to Delight</a>. Probably the most important and hardest metric. The most important because that is the real job of a product or service to delight the customer. The hardest because you have to go out and ask your customers one by one and find out how to replicate that awesome experience or that one thing that wowed your customers for all of the others.</p><p>One of the things missing from Texas Tech&#8217;s Computer Science degree is a course in Human &#038; Computer Interaction, or along similar lines. We learn a lot about how to write good software but nothing of how to make people experience delight in using it. And the real key behind good software isn&#8217;t how bug free it is, but does the customer absolutely love using that application, if they do you&#8217;ve made a customer for life. <a
href="http://www.appple.com/" title="Apple, Inc.">Apple</a> is the obvious and perfect example of this.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/07/27/52-weeks-of-ux-time-to-delight/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Drawar – Sometimes A Grid Can Save You</title><link>http://www.yostivanich.com/2010/07/25/drawar-sometimes-a-grid-can-save-you/</link> <comments>http://www.yostivanich.com/2010/07/25/drawar-sometimes-a-grid-can-save-you/#comments</comments> <pubDate>Mon, 26 Jul 2010 02:32:15 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Design]]></category> <category><![CDATA[Quick Posts]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[grid]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1361</guid> <description><![CDATA[A grid is an important design element for almost all designs.]]></description> <content:encoded><![CDATA[<blockquote><p>The idea by some web designers that a grid isn&#8217;t necessary goes to show how silly some people in our industry can be. Sure sometimes you can simply get by with a design by &quot;eyeing&quot; it, but a grid helps to keep the chaos under control with a bit of structure. Even the best effects and elements won&#8217;t carry a design if the grid isn&#8217;t there to prop it up.</p></blockquote><p>via <a
href='http://www.drawar.com/journal/16' title="Drawar &ndash; Sometimes A Grid Can Save You">Drawar &ndash; Sometimes A Grid Can Save You</a>. A grid creates structure to an otherwise unstructured document.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/07/25/drawar-sometimes-a-grid-can-save-you/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>A List Apart &#8211; Never Use a Warning When you Mean Undo</title><link>http://www.yostivanich.com/2010/07/08/a-list-apart-never-use-a-warning-when-you-mean-undo/</link> <comments>http://www.yostivanich.com/2010/07/08/a-list-apart-never-use-a-warning-when-you-mean-undo/#comments</comments> <pubDate>Fri, 09 Jul 2010 03:19:19 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Design]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[User Experience]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[user experience]]></category> <category><![CDATA[user interface]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1345</guid> <description><![CDATA[Stop using a warning when you should really just have the ability to undo the action.]]></description> <content:encoded><![CDATA[<blockquote><p>Merely removing warnings doesn’t save our work from peril, but using an “undo” function does. Let me say that again: The solution to our warning woes is undo. With a robust undo, we can close our work with reckless abandon and be secure in the knowledge that we can always get it back. With undo, we can make that horrible “oops!” feeling go away by getting our work back.</p></blockquote><p>via <a
href="http://www.alistapart.com/articles/neveruseawarning/" title="A List Apart &ndash; Never Use a Warning When you Mean Undo">A List Apart &ndash; Never Use a Warning When you Mean Undo</a>. Rather than use a warning consider using the ability to just undo. Less hassle to do the action and easy to fix in the case of a mistake.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/07/08/a-list-apart-never-use-a-warning-when-you-mean-undo/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>A List Apart &#8211; Responsive Web Design</title><link>http://www.yostivanich.com/2010/07/05/a-list-apart-responsive-web-design/</link> <comments>http://www.yostivanich.com/2010/07/05/a-list-apart-responsive-web-design/#comments</comments> <pubDate>Mon, 05 Jul 2010 20:55:34 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Web Design]]></category> <category><![CDATA[iphone]]></category> <category><![CDATA[mobile]]></category> <category><![CDATA[user experience]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1341</guid> <description><![CDATA[A List Apart on creating designs that respond to all users and devices.]]></description> <content:encoded><![CDATA[<blockquote><p>Fluid grids, flexible images, and media queries are the three technical ingredients for responsive web design, but it also requires a different way of thinking. Rather than quarantining our content into disparate, device-specific experiences, we can use media queries to progressively enhance our work within different viewing contexts. That’s not to say there isn’t a business case for separate sites geared toward specific devices; for example, if the user goals for your mobile site are more limited in scope than its desktop equivalent, then serving different content to each might be the best approach.</p></p></blockquote><p>via <a
href="http://www.alistapart.com/articles/responsive-web-design/" title="A List Apart &ndash; Responsive Web Design">A List Apart &ndash; Responsive Web Design</a>. A List Apart on creating designs that respond to all users and devices.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/07/05/a-list-apart-responsive-web-design/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>QuirksBlog &#8211; IE’s big leap forward; CSS3 selectors fully supported</title><link>http://www.yostivanich.com/2010/07/05/quirksblog-ie%e2%80%99s-big-leap-forward-css3-selectors-fully-supported/</link> <comments>http://www.yostivanich.com/2010/07/05/quirksblog-ie%e2%80%99s-big-leap-forward-css3-selectors-fully-supported/#comments</comments> <pubDate>Mon, 05 Jul 2010 20:19:16 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Programming]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[css]]></category> <category><![CDATA[css3]]></category> <category><![CDATA[ie9]]></category> <category><![CDATA[internet explorer]]></category> <category><![CDATA[mozilla firefox]]></category> <category><![CDATA[opera]]></category> <category><![CDATA[safari]]></category> <category><![CDATA[webkit]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1340</guid> <description><![CDATA[IE9 is shaping up to be a huge leap forward for web standards and for Internet Explorer.]]></description> <content:encoded><![CDATA[<blockquote><p>In the past few days I’ve been revising the CSS compatibility table with information about the latest crop of browsers. There’s no doubt about it: this is IE9’s show. It just supports nearly everything. No hassle, no buts.</p><p>Besides, CSS3 selectors are now fully supported by all browsers but one. And that one browser is not IE. It’s, curiously, Opera.</p></blockquote><p>via <a
href="http://www.quirksmode.org/blog/archives/2010/06/ies_big_leap_fo.html" title="QuirksBlog &ndash; IE’s big leap forward; CSS3 selectors fully supported">QuirksBlog &ndash; IE’s big leap forward; CSS3 selectors fully supported</a>. Awesome news and big kudos to the IE team for turning IE into a real browser.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/07/05/quirksblog-ie%e2%80%99s-big-leap-forward-css3-selectors-fully-supported/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Impressive Webs &#8211; Dear Microsoft, You Missed the Boat</title><link>http://www.yostivanich.com/2010/06/15/impressive-webs-dear-microsoft-you-missed-the-boat/</link> <comments>http://www.yostivanich.com/2010/06/15/impressive-webs-dear-microsoft-you-missed-the-boat/#comments</comments> <pubDate>Tue, 15 Jun 2010 06:32:22 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Programming]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[ie]]></category> <category><![CDATA[ie6]]></category> <category><![CDATA[microsoft]]></category> <category><![CDATA[webdesign]]></category> <category><![CDATA[webdevelopment]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1326</guid> <description><![CDATA[How much a few years can change your opinion of a company and it's products.]]></description> <content:encoded><![CDATA[<blockquote><p>You had your chance, Microsoft, and you blew it. There are enough browser makers now that care about the user experience, that care about the developer experience, and that realize what’s important in this community. Even if you did everything right from now on, there’s no amount of promotion, branding, or mock integrity that can change how developers perceive your products. It’s too late.</p></blockquote><p>via <a
href="http://www.impressivewebs.com/dear-microsoft/" title="Impressive Webs &ndash; Dear Microsoft, You Missed the Boat">Impressive Webs &ndash; Dear Microsoft, You Missed the Boat</a>. It&#8217;s sad but in nine years the web design community has turned from being enthralled with IE to wanting it to wither away and disappear. It probably doesn&#8217;t help that most of the web development crowd has turned to the Mac and Microsoft decided long ago to turn it&#8217;s back on IE for the Mac, thus relegating it to a chore to test new designs or features.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/06/15/impressive-webs-dear-microsoft-you-missed-the-boat/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>hsivonen &#8211; -webkit-HTML5</title><link>http://www.yostivanich.com/2010/06/07/hsivonen-webkit-html5/</link> <comments>http://www.yostivanich.com/2010/06/07/hsivonen-webkit-html5/#comments</comments> <pubDate>Tue, 08 Jun 2010 04:12:04 +0000</pubDate> <dc:creator>Justin Yost</dc:creator> <category><![CDATA[Programming]]></category> <category><![CDATA[Technology]]></category> <category><![CDATA[Web Design]]></category> <category><![CDATA[apple]]></category> <category><![CDATA[css]]></category> <category><![CDATA[html5]]></category> <category><![CDATA[standards]]></category> <category><![CDATA[w3c]]></category> <category><![CDATA[webdevelopment]]></category> <category><![CDATA[webkit]]></category><guid
isPermaLink="false">http://www.yostivanich.com/?p=1325</guid> <description><![CDATA[Apple calls it open and HTML5 but it really isn't.]]></description> <content:encoded><![CDATA[<blockquote><p>The demos have three levels of obstacles for non-Safari browsers even if the other browsers implemented the HTML5 features being demoed (only video and audio; the rest is CSS!) and implemented the proposed CSS features once standardized:</p></blockquote><p>via <a
href="http://hsivonen.iki.fi/-webkit-html5/" title="hsivonen &ndash; -webkit-HTML5">hsivonen &ndash; -webkit-HTML5</a>. Apple promotes open standards by calling them by the wrong name and using the most closed version possible to prevent all other browsers from seeing the effects. Oh and one of the demos doesn&#8217;t even work in anything other than the latest version of Mac OSX.</p> ]]></content:encoded> <wfw:commentRss>http://www.yostivanich.com/2010/06/07/hsivonen-webkit-html5/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching 8/26 queries in 0.077 seconds using disk

Served from: www.yostivanich.com @ 2010-09-09 23:38:38 -->