<?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="https://blog.curtisherbert.com/slopes-diaries-26-killing-the-slopes-pass/"/>
	<rdf:li rdf:resource="https://www.diverseui.com/"/>
	<rdf:li rdf:resource="https://uxplanet.org/great-alternatives-to-hamburger-menus-d4c76d9414dd#.jhzoyvins"/>
	<rdf:li rdf:resource="http://alistapart.com/article/language-of-modular-design"/>
	<rdf:li rdf:resource="http://www.lukew.com/ff/entry.asp?1950"/>
	<rdf:li rdf:resource="https://storify.com/lukew/drop-downs-are-the-ui-of-last-resort"/>
	<rdf:li rdf:resource="https://medium.com/@joshpuckett/modern-design-tools-using-real-data-62d499e97482"/>
	<rdf:li rdf:resource="https://medium.com/@erqiudao/the-play-button-is-not-optical-alignment-4cea11bda175"/>
	<rdf:li rdf:resource="http://www.nngroup.com/articles/smartwatch/"/>
	<rdf:li rdf:resource="http://uxmovement.com/forms/why-users-fill-out-less-if-you-mark-required-fields/"/>
	<rdf:li rdf:resource="http://wagerfield.github.io/parallax/"/>
	<rdf:li rdf:resource="http://uxmovement.com/buttons/why-ok-buttons-in-dialog-boxes-work-best-on-the-right/"/>
	<rdf:li rdf:resource="http://sketchmine.co/"/>
	<rdf:li rdf:resource="http://www.goodui.org/"/>
	<rdf:li rdf:resource="http://boxesandarrows.com/let-them-pee-avoiding-the-sign-upsign-in-mobile-antipattern/"/>
	<rdf:li rdf:resource="http://scottberkun.com/2013/the-no-ui-debate-is-rubbish/"/>
	<rdf:li rdf:resource="http://conversionxl.com/dont-use-automatic-image-sliders-or-carousels-ignore-the-fad/"/>
	<rdf:li rdf:resource="http://labs.voronianski.com/jquery.avgrund.js/#"/>
	<rdf:li rdf:resource="https://github.com/simplebits/Pears"/>
	<rdf:li rdf:resource="http://www.uiparade.com/ui-toolkit/"/>
	<rdf:li rdf:resource="http://mrgan.tumblr.com/post/10492926111/labeling-the-back-button"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://blog.curtisherbert.com/slopes-diaries-26-killing-the-slopes-pass/">
    <title>Slopes Diaries #26: Killing the Slopes Pass — Curtis Herbert</title>
    <dc:date>2018-11-13T22:02:05+00:00</dc:date>
    <link>https://blog.curtisherbert.com/slopes-diaries-26-killing-the-slopes-pass/</link>
    <dc:creator>Aetles</dc:creator><dc:subject>marketing ios ux ui apps development business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:d0804b578cd2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:marketing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:apps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.diverseui.com/">
    <title>Diverse UI</title>
    <dc:date>2017-04-06T10:33:47+00:00</dc:date>
    <link>https://www.diverseui.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Diverse UI is a free set of user images that can be used in personal or commercial projects. 

We built Diverse UI because who we assume our users are, and how we represent that in our visuals, affects who those users turn out to be. We want those users to be diverse. For more information, we wrote a blog post about why we think diversity in UI mockups is important.]]></description>
<dc:subject>design ui photos diversity mockup webdevelopment webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:af313f47d469/</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:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:photos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:diversity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mockup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://uxplanet.org/great-alternatives-to-hamburger-menus-d4c76d9414dd#.jhzoyvins">
    <title>Great Alternatives to Hamburger Menus</title>
    <dc:date>2017-02-17T10:52:56+00:00</dc:date>
    <link>https://uxplanet.org/great-alternatives-to-hamburger-menus-d4c76d9414dd#.jhzoyvins</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[This is a much debated topic and while designers, developers mostly agree on when it is a good idea to use a navigational drawer and when not there are still a lot of mobile apps that rely on this pattern. It usually boils down to the fact that there is no place to put navigation on a small screen, because it lacks a well thought out information architecture or just because of the sheer amount of content.
If your app gets too complex, think about unbundling. Look at what Facebook did with Messenger. They broke out functionality around key actions and put it in their own separate app.
Hamburger menus drive engagement down, slow down exploration and confuse people. If you are reading this, it won’t confuse you, but it damn will confuse others who might be happy to consume your content.]]></description>
<dc:subject>ui ux webdevelopment webdesign userinterface userexperience navigation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:922e5f3ec6de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:userinterface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:userexperience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:navigation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alistapart.com/article/language-of-modular-design">
    <title>The Language of Modular Design · An A List Apart Article</title>
    <dc:date>2015-08-12T20:33:43+00:00</dc:date>
    <link>http://alistapart.com/article/language-of-modular-design</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Start with language
Language is fundamental to collaboration. In her book How to Make Sense of Any Mess, Abby Covert says that the biggest obstacle teams face is the lack of a shared language. To help establish that shared language, she suggests that we discuss, vet, and document our ontological decisions in the form of “controlled vocabularies.”

In short, we should start with language, not interfaces.

For about a year now, our team at FutureLearn, an open education platform, has been experimenting with a modular approach. I’d like to share a few ways we have tried to hone a shared language to help our team transition into modular design.]]></description>
<dc:subject>css design webdesign webdevelopment ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:5f8755fda187/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.lukew.com/ff/entry.asp?1950">
    <title>LukeW | Dropdowns Should be the UI of Last Resort</title>
    <dc:date>2015-07-21T21:18:30+00:00</dc:date>
    <link>http://www.lukew.com/ff/entry.asp?1950</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[All too often mobile forms make use of dropdown menus for input when simpler or more appropriate controls would work better. Here's several alternatives to dropdowns to consider in your designs and why.]]></description>
<dc:subject>design ux ui webdevelopment webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:662a0cbe1f3c/</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:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://storify.com/lukew/drop-downs-are-the-ui-of-last-resort">
    <title>Drop Downs Should be the UI of Last Resort (with images, tweets) · lukew · Storify</title>
    <dc:date>2015-06-28T21:17:30+00:00</dc:date>
    <link>https://storify.com/lukew/drop-downs-are-the-ui-of-last-resort</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[All too often mobile forms make use of drop-down menus for input when simpler, more appropriate controls would work better. Here's a few alternatives.]]></description>
<dc:subject>design dropdown interface ux ui webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:36ea36ac7f93/</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:dropdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@joshpuckett/modern-design-tools-using-real-data-62d499e97482">
    <title>Modern Design Tools: Using Real Data — Design Insights from Bridge — Medium</title>
    <dc:date>2015-06-16T14:50:57+00:00</dc:date>
    <link>https://medium.com/@joshpuckett/modern-design-tools-using-real-data-62d499e97482</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[I believe one of the biggest flaws of today’s tools is their failure to allow designers to easily work with real data. Because of this, designers often fill their mocks with idealized information that is anything but representative. Beautifully composed photos. Perfectly sized bits of text. Just the right amount of content to fit. We spend an inordinate amount of time making our pixel-perfect fabrications. We then make sub-optimal decisions based on this, considering only our single, perfect state. We are surprised when our designs are implemented because we forgot to solve a variety of edge cases and problems. When we don’t work with real data, we deceive ourselves.

In contrast, when designers work with real data they design in reality. They allow data to inform and constrain their work. Their decisions are wholly informed; implementation details carefully considered; edge cases solved. They build empathy for how their users will actually experience things in a variety of contexts. They are not surprised when their designs get implemented because they’ve been using real data all along.]]></description>
<dc:subject>data design ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:f2dfb8da3f3d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@erqiudao/the-play-button-is-not-optical-alignment-4cea11bda175">
    <title>The PLAY button is not optical alignment — Medium</title>
    <dc:date>2015-06-04T23:06:53+00:00</dc:date>
    <link>https://medium.com/@erqiudao/the-play-button-is-not-optical-alignment-4cea11bda175</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Lots of people say that you can not center align the play button,the physics center is not the visual center . Well,actually I think you can,the key is to find the real center of the triangle.]]></description>
<dc:subject>design ui ux webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:672b9437ac76/</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:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nngroup.com/articles/smartwatch/">
    <title>The Apple Watch: User-Experience Appraisal</title>
    <dc:date>2015-05-19T14:49:13+00:00</dc:date>
    <link>http://www.nngroup.com/articles/smartwatch/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Summary: Smartwatch apps should rely on gestures more than on navigation elements, prioritize the essential, support handoff, and create tailored, standalone content.]]></description>
<dc:subject>apple applewatch ux ui design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:9e634903cddc/</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:applewatch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://uxmovement.com/forms/why-users-fill-out-less-if-you-mark-required-fields/">
    <title>Why Users Fill Out Less If You Mark Required Fields - UX Movement</title>
    <dc:date>2014-04-17T09:27:56+00:00</dc:date>
    <link>http://uxmovement.com/forms/why-users-fill-out-less-if-you-mark-required-fields/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Are most of your users skipping the optional fields on your form? You might not need that extra information, but having it could help you learn more about users and give them a better experience. If you want more users to fill out the optional fields on your form, avoid marking required fields and mark optional ones only.]]></description>
<dc:subject>design forms ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:a7e2f6878c79/</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:forms"/>
	<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://wagerfield.github.io/parallax/">
    <title>parallax.js</title>
    <dc:date>2013-08-28T08:46:03+00:00</dc:date>
    <link>http://wagerfield.github.io/parallax/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[WOW, that's deep man! parallax.js reacts to the orientation of your smart device, offsetting layers depending on their depth within a scene... Oh, you don't have a smart device? No worries, if no gyroscope or motion detection hardware is available, parallax.js uses the position of your cursor instead. Radical.]]></description>
<dc:subject>javascript js animation ui parallax</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:b81788ad77bb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:js"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:animation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:parallax"/>
</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://sketchmine.co/">
    <title>SketchMine</title>
    <dc:date>2013-06-03T08:03:12+00:00</dc:date>
    <link>http://sketchmine.co/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Sketch files from the design community]]></description>
<dc:subject>design ui sketch osx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:fa26578aeb18/</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:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sketch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:osx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.goodui.org/">
    <title>A Good User Interface</title>
    <dc:date>2013-04-15T08:49:08+00:00</dc:date>
    <link>http://www.goodui.org/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[A Good User Interface
has high conversion rates and is easy to use. In other words, it's nice to both the business side as well as the people using it. Here is a running list of practical ideas to try out.]]></description>
<dc:subject>design ux ui webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:ce46045f7c83/</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:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://boxesandarrows.com/let-them-pee-avoiding-the-sign-upsign-in-mobile-antipattern/">
    <title>Let Them Pee: Avoiding the Sign-Up/Sign-In Mobile Antipattern « Boxes and Arrows</title>
    <dc:date>2013-03-25T22:21:20+00:00</dc:date>
    <link>http://boxesandarrows.com/let-them-pee-avoiding-the-sign-upsign-in-mobile-antipattern/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Anything that slows down customers or gets in their way after they download your app is a bad thing. That includes sign-up/sign-in forms that show up even before potential customers can figure out if the app is actually worth using.
It’s a simple UX equation
This antipattern seems to be going away more and more as companies are beginning to figure out the following simple UX equation:
Long sign-up form before you can use the app = Delete app
However, a fair number of apps still force customers to sign up, sign in, or perform some other useless action before they can use the app.]]></description>
<dc:subject>app design ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:e930fe81bbd2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:app"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<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://scottberkun.com/2013/the-no-ui-debate-is-rubbish/">
    <title>The No UI debate is rubbish</title>
    <dc:date>2013-03-17T13:22:05+00:00</dc:date>
    <link>http://scottberkun.com/2013/the-no-ui-debate-is-rubbish/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[A debate is rising on whether the old platitude No UI is the best UI is good or bad. I’ll tell you who is right: no one.
Debates like these fall into the same stupid trap academics have fallen into for centuries: Platonic ideals are an illusion. They’re fun to play with, but they’re useless when your hands are dirty trying to solve a real problem for a real person.
The only sane replacement is The best UI is what’s best for the person and situation I’m designing for. That’s all. Who cares what’s best in the abstract? No one hires you to design abstractions, and if they did, your business card should say “Platonic Theorist” not “Designer”.]]></description>
<dc:subject>design ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:db8592070995/</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:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://conversionxl.com/dont-use-automatic-image-sliders-or-carousels-ignore-the-fad/">
    <title>Don’t Use Automatic Image Sliders or Carousels, Ignore the Fad | ConversionXL</title>
    <dc:date>2013-02-25T08:08:50+00:00</dc:date>
    <link>http://conversionxl.com/dont-use-automatic-image-sliders-or-carousels-ignore-the-fad/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[I’m sure you’ve come across dozens, if not hundreds of image sliders or carousels (also called ‘rotating offers’). You might even like them. But the truth is that they’re conversion killers.]]></description>
<dc:subject>carousels sliders design ux ui webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:342762e8817a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:carousels"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sliders"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://labs.voronianski.com/jquery.avgrund.js/#">
    <title>jQuery plugin for Avgrund concept popin</title>
    <dc:date>2012-09-02T20:21:53+00:00</dc:date>
    <link>http://labs.voronianski.com/jquery.avgrund.js/#</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Avgrund is a jQuery plugin for modal boxes and popups. It uses interesting concept showing depth between popup and page. It works in all modern browsers and gracefully degrade in those that do not support CSS transitions and transformations (e.g. in IE 6-9 has standard behavior). Tested with jQuery 1.4+, file size is under 2Kb, MIT Licensed.]]></description>
<dc:subject>javascript jquery js ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:d7123eff1ff8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:jquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:js"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/simplebits/Pears">
    <title>simplebits/Pears - GitHub</title>
    <dc:date>2012-02-06T22:48:10+00:00</dc:date>
    <link>https://github.com/simplebits/Pears</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Pears are common patterns of markup & style.

Pears is an open source WordPress theme. I'll admit the code 
is a bit rough, initially based on the default 'twentyone' theme.

I wanted a handy way of collecting HTML & CSS pattern pairs. 
Often used modules with a minimal of style applied. It's become 
a valuable learning tool, whereby breaking interfaces down into 
small pieces make it easier to learn and improve running code.

Learn more and see it in action here:
http://pea.rs
]]></description>
<dc:subject>theme ui wordpress html css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:2e62dba2567a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:theme"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:wordpress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.uiparade.com/ui-toolkit/">
    <title>The Ui Toolkit | Ui Parade – User Interface Inspiration</title>
    <dc:date>2012-01-17T10:25:13+00:00</dc:date>
    <link>http://www.uiparade.com/ui-toolkit/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Grab this awesome bundle of essential Ui design resources and speed up your design workflow for just $8. The toolkit is packed with well over 300 premium quality royalty free design elements created specifically with Ui developers and designers in mind.]]></description>
<dc:subject>icons photoshop ui design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:e02cd83e40a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:icons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:photoshop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mrgan.tumblr.com/post/10492926111/labeling-the-back-button">
    <title>Labeling the Back button - Neven Mrgan's tumbl</title>
    <dc:date>2011-10-25T21:42:48+00:00</dc:date>
    <link>http://mrgan.tumblr.com/post/10492926111/labeling-the-back-button</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Most “deep” apps require some amount of navigation, moving the user deeper into child views and then back out to the parent view. That navigational backtracking is typically done with a “Back” button, positioned in the top-left corner, and denoted by a pointed left side. You’ve all seen it:



The title of the entire bar is the title of this view; the Back button shows the previous, parent view’s title. Here, then, is a piece of advice for app designers: The Back button should never show the text “Back”. 

This is a widespread issue, present in many extremely popular apps.]]></description>
<dc:subject>userinterface design ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:4be2b89c0a47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:userinterface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>