<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (Aetles)</title>
    <link>https://pinboard.in/u:Aetles/public/</link>
    <description>recent bookmarks from Aetles</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.spurapp.com/"/>
	<rdf:li rdf:resource="http://moz.com/blog/5-lessons-learned-from-100000-usability-studies"/>
	<rdf:li rdf:resource="http://uxmovement.com/buttons/why-ok-buttons-in-dialog-boxes-work-best-on-the-right/"/>
	<rdf:li rdf:resource="http://userium.com/"/>
	<rdf:li rdf:resource="http://www.userfocus.co.uk/articles/cardgames.html"/>
	<rdf:li rdf:resource="http://www.not-implemented.com/urls-are-for-people-not-computers/"/>
	<rdf:li rdf:resource="http://www.solidifyapp.com/"/>
	<rdf:li rdf:resource="http://blog.edwardmarks.com/post/9859783254/improve-usability-with-a-black-status-bar-and-rounded"/>
	<rdf:li rdf:resource="http://baymard.com/blog/checkout-usability-apply-buttons"/>
	<rdf:li rdf:resource="http://www.useit.com/alertbox/mega-dropdown-menus.html"/>
	<rdf:li rdf:resource="http://www.uie.com/articles/three_hund_million_button/"/>
	<rdf:li rdf:resource="http://tantek.com/log/2007/02.html"/>
	<rdf:li rdf:resource="http://www.456bereastreet.com/archive/200411/who_framed_the_web_frames_and_usability"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.spurapp.com/">
    <title>Spur - A fun and easy way to critique a webpage.</title>
    <dc:date>2013-10-23T09:12:58+00:00</dc:date>
    <link>http://www.spurapp.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[A fun and easy way to critique your web pages.

What is Spur?
Spur is a fun and easy way to critique web designs in ways you’ve never done before. Just paste a URL (or upload an image) and you’ll be able to use seven different tools to help you find what’s working (and what isn’t!).]]></description>
<dc:subject>design usability webdesign testing tools web</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:9487b35c2c49/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://moz.com/blog/5-lessons-learned-from-100000-usability-studies">
    <title>5 Lessons Learned from 100,000 Usability Studies - Moz</title>
    <dc:date>2013-09-01T13:06:49+00:00</dc:date>
    <link>http://moz.com/blog/5-lessons-learned-from-100000-usability-studies</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[People get confused, frustrated, and angry while using websites. They sigh, they groan, and sometimes they even shout. I see it happen with my own eyes each and every day.

Over the years at UserTesting.com we’ve literally watched hundreds of thousands of usability studies, which gives us a unique perspective into some of the most common issues that impact users. I’d like to share five of those insights with you.]]></description>
<dc:subject>design usability</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:24c2f236dee3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://uxmovement.com/buttons/why-ok-buttons-in-dialog-boxes-work-best-on-the-right/">
    <title>Why ‘Ok’ Buttons in Dialog Boxes Work Best on the Right - UX Movement</title>
    <dc:date>2013-06-17T10:05:20+00:00</dc:date>
    <link>http://uxmovement.com/buttons/why-ok-buttons-in-dialog-boxes-work-best-on-the-right/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Designers often use dialog boxes when there’s an important message users need to read, or an important action they need to take. The order you place your buttons can affect which action the user chooses. When you place your buttons in an order that is clear and efficient to users, you can prevent them from choosing the wrong action and making a serious mistake.
Button placement is important, but remember to also pay attention to the visual weight and labels you give your buttons. All of these design aspects come into play when users process dialog boxes. Now that you understand the reasons why ‘Ok’ buttons work best on the right, you’ll have something more to refer to when figuring out button placement than the flimsy platform consistency argument.]]></description>
<dc:subject>design usability ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:c1dd1163c15a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://userium.com/">
    <title>Usability checklist | Userium | Catch common usability problems before user testing.</title>
    <dc:date>2013-04-29T21:00:48+00:00</dc:date>
    <link>http://userium.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[ Catch common usability problems before user testing.]]></description>
<dc:subject>usability webdesign testing ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:d18bcd998b47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.userfocus.co.uk/articles/cardgames.html">
    <title>Card Games for Information Architects</title>
    <dc:date>2013-04-15T09:23:59+00:00</dc:date>
    <link>http://www.userfocus.co.uk/articles/cardgames.html</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Over the last few years we've seen a quiet revolution in user experience research. Participants no longer need to come to a usability lab. Nowadays, we can carry out many user research activities over the web. Although we welcome this change (and have even developed our own remote usability testing tool), user experience research is fundamentally straightforward. There's a lot you can do with the simplest of tools.]]></description>
<dc:subject>usability ux techniques</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:72e3de6721e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:techniques"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.not-implemented.com/urls-are-for-people-not-computers/">
    <title>URLs are for People, not Computers | Not Implemented</title>
    <dc:date>2013-04-07T12:25:29+00:00</dc:date>
    <link>http://www.not-implemented.com/urls-are-for-people-not-computers/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[We are all familiar with URLs: the string uniquely identifying the requested document. However, we don’t always consider they are more than that: URLs are user facing and should be considered important UI elements.

They should be clean, understandable, semantic, hierarchical and not excessively long.]]></description>
<dc:subject>design usability url ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:b8b8da8b5057/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:url"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.solidifyapp.com/">
    <title>Solidify | Quick way to build prototypes for user testing</title>
    <dc:date>2012-10-22T10:43:05+00:00</dc:date>
    <link>http://www.solidifyapp.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Solidify lets you create clickable prototypes from sketches, wireframe, or mockup. Validate user flows on any device by performing user tests in person, remotely, or on your testers own time to get the feedback you need.]]></description>
<dc:subject>usability webdesign testing ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:e9c7afe0706f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.edwardmarks.com/post/9859783254/improve-usability-with-a-black-status-bar-and-rounded">
    <title>Edward Marks: Improve Usability With A Black Status Bar and Rounded Corners</title>
    <dc:date>2012-08-20T07:48:50+00:00</dc:date>
    <link>http://blog.edwardmarks.com/post/9859783254/improve-usability-with-a-black-status-bar-and-rounded</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[The use of a black status bar and rounded corners can increase the usability of your iPhone application by bounding your content and thus separating it from the viewport.]]></description>
<dc:subject>apple ios design usability development iphone</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:3144f672deeb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:iphone"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://baymard.com/blog/checkout-usability-apply-buttons">
    <title>Checkout Usability: Don't Use &quot;Apply&quot; Buttons (72% Get it Wrong) - Articles - Baymard Institute</title>
    <dc:date>2012-08-03T22:15:13+00:00</dc:date>
    <link>http://baymard.com/blog/checkout-usability-apply-buttons</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[When we conducted the checkout usability study last year we discovered that whenever an “Apply” button was used to submit only a section of a checkout form it was either:

Not clicked, even if the related input field was filled out, or
Mistaken for the primary button.
More than half of the test subjects were confused by e-commerce checkout forms with an inline “Apply” button. The test subjects simply didn’t understand the concept of having a separate “Apply” button for distinct sections of a form – i.e. for applying a shipping method or a coupon code to the order. Instead, the subjects expected a single primary button in the checkout flows which would submit everything and take them to the next checkout step.]]></description>
<dc:subject>forms usability ecommerce</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:48eeeca736cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:forms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ecommerce"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.useit.com/alertbox/mega-dropdown-menus.html">
    <title>Mega Drop-Down Navigation Menus Work Well (Jakob Nielsen's Alertbox)</title>
    <dc:date>2010-10-27T14:54:59+00:00</dc:date>
    <link>http://www.useit.com/alertbox/mega-dropdown-menus.html</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[To prepare for our upcoming Navigation Design seminar, we've been running user studies of various navigation features. As always, some test poorly. Also as always, the more faddish features — such as tag clouds — exhibit major usability problems.

Luckily, other Web trends fare well in user testing because they have inherently good usability and match user behaviors and goals. Indeed, one particular navigation design — the mega drop-down menu — tested well enough that I want to encourage its wider use.

Given that regular drop-down menus are rife with usability problems, it takes a lot for me to recommend a new form of drop-down. But, as our testing videos show, mega drop-downs overcome the downsides of regular drop-downs. Thus, I can recommend one while warning against the other.]]></description>
<dc:subject>interface usability webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:6fb217f30ca3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.uie.com/articles/three_hund_million_button/">
    <title>The $300 Million Button</title>
    <dc:date>2010-10-22T22:02:22+00:00</dc:date>
    <link>http://www.uie.com/articles/three_hund_million_button/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[It's hard to imagine a form that could be simpler: two fields, two buttons, and one link. Yet, it turns out this form was preventing customers from purchasing products from a major e-commerce site, to the tune of $300,000,000 a year. What was even worse: the designers of the site had no clue there was even a problem.]]></description>
<dc:subject>design usability</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:07c6aaba1058/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tantek.com/log/2007/02.html">
    <title>Three Hypotheses of Human Interface Design</title>
    <dc:date>2007-03-16T09:37:06+00:00</dc:date>
    <link>http://tantek.com/log/2007/02.html</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[En utmärkt hypotes för "Human Interface Design", användargränssnittsdesign, av Tantek Çelik. I korthet handlar det om att ett användargränssnitt blir bättre om det är enklare, färre klick för att genomföra en uppgift, färre textfält att fylla i och om det
]]></description>
<dc:subject>gränssnitt design interface användarvänlighet usability cognitive load Webbutveckling</dc:subject>
<dc:identifier>https://pinboard.in/u:Aetles/b:434deb1379c5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:gränssnitt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:användarvänlighet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:cognitive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:load"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:Webbutveckling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.456bereastreet.com/archive/200411/who_framed_the_web_frames_and_usability">
    <title>Who framed the web: Frames and usability</title>
    <dc:date>2004-11-19T10:10:01+00:00</dc:date>
    <link>http://www.456bereastreet.com/archive/200411/who_framed_the_web_frames_and_usability</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[En artikel om nackdelarna med frames.
]]></description>
<dc:subject>frames ramar iframe iframes usability användbarhet Webbutveckling</dc:subject>
<dc:identifier>https://pinboard.in/u:Aetles/b:19fb3a02dd1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:frames"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ramar"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:iframe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:iframes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:användbarhet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:Webbutveckling"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>