<?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 (guardiantech)</title>
    <link>https://pinboard.in/u:guardiantech/public/</link>
    <description>recent bookmarks from guardiantech</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://medium.com/@designuxui/how-bad-ux-killed-jenny-ef915419879e"/>
	<rdf:li rdf:resource="http://gigaom.com/2014/08/28/a-failed-experiment-how-lg-screwed-up-its-webos-acquisition/"/>
	<rdf:li rdf:resource="http://www.donotlick.com/firefox-and-flux-a-new-beautiful-browser-is-coming/"/>
	<rdf:li rdf:resource="http://www.buzzfeed.com/charliewarzel/is-twitter-phasing-out-hashtags-and-at-replies"/>
	<rdf:li rdf:resource="http://www.hs.fi/kuukausiliite/This+is+how+a+Helsingin+Sanomat+journalist+tried+to+save+Nokia/a1381288411564?ref=hs-art-new-1"/>
	<rdf:li rdf:resource="http://winsupersite.com/windows-phone/windows-phone-81-rumors-emerge"/>
	<rdf:li rdf:resource="http://martinbelam.com/2013/gmail-tabbed-inbox/"/>
	<rdf:li rdf:resource="https://medium.com/design-ux/60a90256efe5"/>
	<rdf:li rdf:resource="http://www.androidpolice.com/2013/07/22/exclusive-moto-x-cameras-new-minimalist-user-interface-and-swipe-gestures/"/>
	<rdf:li rdf:resource="https://medium.com/design-ux/dbc28a521a10"/>
	<rdf:li rdf:resource="https://plus.google.com/u/0/+GoogleMaps/posts/4Cm8CfXz2qS"/>
	<rdf:li rdf:resource="http://mobileopportunity.blogspot.co.uk/2013/06/style-vs-substance-in-mobile-software.html"/>
	<rdf:li rdf:resource="http://getwired.com/2013/06/12/content-not-the-chrome-apps-not-the-phone/"/>
	<rdf:li rdf:resource="http://stratechery.com/2013/change-for-changes-sake/"/>
	<rdf:li rdf:resource="http://www.businessweek.com/articles/2013-05-02/sonys-first-mover-disadvantage-in-smart-watches"/>
	<rdf:li rdf:resource="http://9to5mac.com/2013/04/29/jony-ive-paints-a-fresh-yet-familiar-look-for-ios-7/"/>
	<rdf:li rdf:resource="http://techcrunch.com/2013/04/20/cognitive-overhead/"/>
	<rdf:li rdf:resource="http://www.pocketables.com/2013/03/microsoft-and-the-context-sensitive-search-problem.html"/>
	<rdf:li rdf:resource="http://allthingsd.com/20130321/a-universal-remote-thats-a-touch-too-much/"/>
	<rdf:li rdf:resource="http://boxesandarrows.com/let-them-pee-avoiding-the-sign-upsign-in-mobile-antipattern/"/>
	<rdf:li rdf:resource="http://www.techradar.com/news/phone-and-communications/mobile-phones/gimmick-watch-which-galaxy-s4-features-are-actually-useful-1137782"/>
	<rdf:li rdf:resource="http://www.zdnet.com/will-90-percent-of-users-always-hate-windows-8-7000012348/"/>
	<rdf:li rdf:resource="http://martinbelam.com/2013/ultraviolet/"/>
	<rdf:li rdf:resource="http://dcurt.is/yours-vs-mine"/>
	<rdf:li rdf:resource="http://macorios.com/files/iPhone-Settings-Mind-Map.html"/>
	<rdf:li rdf:resource="http://www.androidpolice.com/2012/09/18/ux-things-i-hate-about-android/"/>
	<rdf:li rdf:resource="http://www.useit.com/alertbox/windows-8.html"/>
	<rdf:li rdf:resource="http://skeu.it/"/>
	<rdf:li rdf:resource="http://counternotions.com/2012/11/05/sirjony/"/>
	<rdf:li rdf:resource="http://getwired.com/2012/10/28/ios-is-showing-its-age/"/>
	<rdf:li rdf:resource="https://skydrive.live.com/?cid=d57e836204feb061&amp;id=D57E836204FEB061%213317&amp;sff=1"/>
	<rdf:li rdf:resource="http://www.currybet.net/cbet_blog/2012/08/never-open-external-links-in-new-windows.php"/>
	<rdf:li rdf:resource="http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesign/"/>
	<rdf:li rdf:resource="http://vimeo.com/43224490"/>
	<rdf:li rdf:resource="http://www.totalmedia.co.uk/insights/news/145"/>
	<rdf:li rdf:resource="http://www.loper-os.org/?p=861"/>
	<rdf:li rdf:resource="http://www.youtube.com/watch?v=XeeOkHjV7nM"/>
	<rdf:li rdf:resource="http://icspapercuts.tumblr.com/"/>
	<rdf:li rdf:resource="http://www.elezea.com/2011/12/google-path-ui-design/"/>
	<rdf:li rdf:resource="http://mrgan.tumblr.com/post/10492926111/labeling-the-back-button"/>
	<rdf:li rdf:resource="http://googlesystem.blogspot.com/2011/07/google-tests-interface-optimized-for.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://medium.com/@designuxui/how-bad-ux-killed-jenny-ef915419879e">
    <title>How bad UX killed Jenny &gt;&gt; Medium</title>
    <dc:date>2014-10-20T14:44:04+00:00</dc:date>
    <link>https://medium.com/@designuxui/how-bad-ux-killed-jenny-ef915419879e</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Jonathan Shariat: <blockquote class="quoted">Jenny, as we will call her because the patient's name was never shared, was a little girl who had previously been in the hospital ward for cancer for four years and was discharged. Then a while later she relapsed and had to be given a very strong chemo treatment medicine. This medicine is so strong and so toxic that it requires pre-hydration and post-hydration for three days with I.V. fluid. However, after the medicine was administered, three nurses were attending to the charting software to enter in everything required of them and make the appropriate orders, missed a very critical piece of information. Jenny was supposed to be given 3 days of I.V. hydration. But the three nurses, with over 10 years experience, were too distracted trying to figure out the software they were using, they completely missed it.

When the morning nurse came in the next day, she had died of toxicity and dehydration. For two shifts, she had missed her hydration and all because the three, very good nurses, were stuck trying to figure this out…</blockquote>

The screenshot he posts is indeed a nightmare of user-hostility. Worth remembering: poor interface design can be literally lethal.]]></description>
<dc:subject>ux health design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:44cac828929d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:health"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gigaom.com/2014/08/28/a-failed-experiment-how-lg-screwed-up-its-webos-acquisition/">
    <title>A failed experiment: how LG screwed up its webOS acquisition &gt;&gt; Gigaom</title>
    <dc:date>2014-08-28T20:04:10+00:00</dc:date>
    <link>http://gigaom.com/2014/08/28/a-failed-experiment-how-lg-screwed-up-its-webos-acquisition/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Janko Roettgers: <blockquote class="quoted">[The Consumer Electronics Show] CES was approaching quickly, and LG’s engineers [in Korea] ran out of time trying to make their complicated interface work, so the decision was made to go with the webOS launcher instead in order to have anything up and running at all.

“We got lucky,” said one member of the original webOS team, who like others in this story declined to be identified by name.

I’ve been told that this anecdote was symptomatic of many of the struggles the webOS team was facing across all parts of its operation, including engineering. Despite repeated requests, LG never hired more engineers for the Silicon Valley group. Instead, it put them at the mercy of engineers in Korea who were beholden to their local management, and frequently built features that the webOS team didn’t ask for, or worse, had long fought against.

On the engineering side, the webOS team also struggled with a culture clash of sorts that pitted company politics against its attempt to simplify the company’s smart TV platform. Sources told me that LG had a policy in place to reward managers with bonuses or even promotions if their features were part of the final product. The result was a constant feature bloat, as everyone tried to add on one more thing.</blockquote>]]></description>
<dc:subject>ux smarttv lg</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:47713f952af4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:smarttv"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:lg"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.donotlick.com/firefox-and-flux-a-new-beautiful-browser-is-coming/">
    <title>Firefox and Flux: a new, beautiful browser is coming &gt;&gt; DO NOT LICK</title>
    <dc:date>2014-04-29T20:43:24+00:00</dc:date>
    <link>http://www.donotlick.com/firefox-and-flux-a-new-beautiful-browser-is-coming/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>This new Firefox, Firefox 29, was borne out of a series of incredible, detail-obsessed designers and engineers understanding that taking products from good to great requires more than a series of incremental improvements.

Good can be achieved through incrementalism. Great requires, at times, overhaul.

Firefox 29 contains extensive improvements that were planned back when Alex Faaborg, Madhava Enros, and myself were the only designers at Mozilla. Back then, Firefox was beginning to buckle under the weight of its inconsistent code and interface.

It’s common enough for large codebases maintained across years to develop inconsistencies. But, Firefox’s nature as an open-source community project contributed to idiosyncratic user experiences. Menus and dialogs used different tenses and tones. Add-ons behaved unpredictably. Customisation was handled differently throughout the browser. Over the past few years, we’ve been working to improve many instances of inconsistent behaviour, such as replacing modal dialogs for tab-modal ones, standardising notifications, and using a uniform tone-of-voice.

Making improvements here and there is often what user experience designers at an organisation are expected to do: fix what’s broken, slightly improve what isn’t, and generally don’t get in the way of engineering effort.  But, this method can only make an existing product slightly better, and the gaps it causes reveal themselves in time.

A sinking ship can’t be patched endlessly when it needs a new hull. This is when user experience design is most effective: when it envisions the system as a whole. When it steps away from the trees and sees the forest holistically.

Firefox needed a new hull, and the bulk of that hull is arriving on Tuesday.</blockquote>]]></description>
<dc:subject>firefox ux mozilla design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:7a4fd14dc09d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:firefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:mozilla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.buzzfeed.com/charliewarzel/is-twitter-phasing-out-hashtags-and-at-replies">
    <title>Twitter hints rhat @-replies and hashtags are about to be streamlined &gt;&gt; Buzzfeed</title>
    <dc:date>2014-03-19T21:57:57+00:00</dc:date>
    <link>http://www.buzzfeed.com/charliewarzel/is-twitter-phasing-out-hashtags-and-at-replies</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>What will Twitter look like in a year? Two years? A lot less like itself.<p>
At least that’s the impression Vivian Schiller, head of news at Twitter, gave addressing the crowd two days ago at the Newspaper Association of America’s mediaXchange conference in Denver. During her talk, Schiller called at-replies and hashtags “arcane” and hinted that Twitter might soon move them into the background of the service.</blockquote>

"Streamlined" isn't the same as "phased out". But to the average person, the grammar of Twitter is arcane.]]></description>
<dc:subject>twitter ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:db844fa7a6da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hs.fi/kuukausiliite/This+is+how+a+Helsingin+Sanomat+journalist+tried+to+save+Nokia/a1381288411564?ref=hs-art-new-1">
    <title>This is how a Helsingin Sanomat journalist tried to save Nokia &gt;&gt; Kuukausiliite - Helsingin Sanomat</title>
    <dc:date>2013-10-10T16:23:47+00:00</dc:date>
    <link>http://www.hs.fi/kuukausiliite/This+is+how+a+Helsingin+Sanomat+journalist+tried+to+save+Nokia/a1381288411564?ref=hs-art-new-1</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[The journalist wrote, inter alia: <blockquote>half a year ago a friend of mine at work showed me a device manufactured by Apple called the iPod Touch. I fell in love instantly. I wanted an iPod, and with that device I could also have convenient access to the internet and much more. I ordered my own iPod touch, turned it on, and knew immediately how to use it. I have used the device now on a daily basis for over six months, and I have not even thought about any manuals. The logic of the device opens up right away. It is no wonder that it is a huge success all over the world.<p>

My new Nokia telephone model is called the E 51. Unfortunately the phone has not been designed in so that just anybody could learn to use it easily.<p>

On the contrary, I think that it has been designed as if its most important mission would be to advertise itself to people who are interested in telephone technology. All kinds of amazing functions are offered on the display, but as I do not understand what they mean, I guess that I will never use them.</blockquote>

But keep reading to find out about the Nokia executive who visited the author of the letter, and what he said.]]></description>
<dc:subject>nokia iphone ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:ae419e71600b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:nokia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://winsupersite.com/windows-phone/windows-phone-81-rumors-emerge">
    <title>Windows Phone 8.1 rumours emerge &gt;&gt; SuperSite for Windows</title>
    <dc:date>2013-10-10T05:30:24+00:00</dc:date>
    <link>http://winsupersite.com/windows-phone/windows-phone-81-rumors-emerge</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Paul Thurrott outlines various things he has heard (single-source) about Windows Phone 8.1. The one that seems to have people worked up is this: <blockquote>No more Back button. Aping the iPhone navigation model, Microsoft will apparently remove the Back button from the Windows Phone hardware specification with 8.1. The Back button just doesn't make sense, I was told: Users navigate away from an app by pressing the Start button and then open a new app, just like they do on iPhone. And the "back stack" is ill-understood by users: Most don't realize what they're doing when they repeatedly hit the Back button.</blockquote>

Links to UX/UI studies of the use of the Back button welcomed.]]></description>
<dc:subject>windowsphone back ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:07576757d5a5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:windowsphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:back"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://martinbelam.com/2013/gmail-tabbed-inbox/">
    <title>Why the new tabbed Gmail inbox doesn’t feel “mobile first” to me &gt;&gt; Martin Belam</title>
    <dc:date>2013-07-25T21:47:37+00:00</dc:date>
    <link>http://martinbelam.com/2013/gmail-tabbed-inbox/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>My assumption is that the design changes are data-driven around how few people use filters or labels, and how many people “Mark as spam” legitimate opt-in newsletters and promotions when they realise that is easier to do than to actually unsubscribe from them.<p>

But the desktop isn’t my gripe.<p>

It is the mobile implementation on iOS that is making Gmail less efficient to use for me.<p>

Updates to the tabs that aren’t your primary inbox are signalled by something that looks like an email, but actually isn’t. Which is a bit confusing as a metaphor.</blockquote>]]></description>
<dc:subject>gmail ios ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:7d76f816ad79/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:gmail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/design-ux/60a90256efe5">
    <title>Writing notifications that don’t suck &gt;&gt; Medium</title>
    <dc:date>2013-07-23T11:56:15+00:00</dc:date>
    <link>https://medium.com/design-ux/60a90256efe5</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Dave Feldman: <blockquote>Good notifications and error messages require care. They’re not necessarily hard, but they are often overlooked – to the detriment of your overall product experience. Because notifications often occur at times of anxiety and annoyance, a bad notification can ruin your UX; while a good notification can take a moment of frustration and turn it around.</blockquote>

He doesn't deal with the notifications that roll over the top of iOS's screen, which can be a hazard - to put it mildly - if you're trying to interact with a screen element up there. A useful piece, though.]]></description>
<dc:subject>ux ui ios android</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:8fd2c0d6edd6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:android"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.androidpolice.com/2013/07/22/exclusive-moto-x-cameras-new-minimalist-user-interface-and-swipe-gestures/">
    <title>Exclusive: Moto X camera's new minimalist user interface and swipe gestures &gt;&gt; Android Police</title>
    <dc:date>2013-07-23T05:37:51+00:00</dc:date>
    <link>http://www.androidpolice.com/2013/07/22/exclusive-moto-x-cameras-new-minimalist-user-interface-and-swipe-gestures/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>The latest tidbits of information from an anonymous tipster is the new camera interface for the Moto X, which is considerably different from both previous "skinned" Motorola phones and the AOSP camera apps in both Android 4.2 and what we've seen of 4.3. It's a lot cleaner than both, with a big focus on gestures and unobtrusive controls.</blockquote>

These look intriguing, and having easily accessible alternative camera settings feels like the wave of the future (as point-and-shoot phone pictures become a commodity). How easy though is it to remember the right gestures when in a rush?]]></description>
<dc:subject>motorola motox ux gestures ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:1b2a634bd507/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:motorola"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:motox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:gestures"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/design-ux/dbc28a521a10">
    <title>Android’s advantages over iPhone &gt;&gt; Medium</title>
    <dc:date>2013-07-19T14:05:47+00:00</dc:date>
    <link>https://medium.com/design-ux/dbc28a521a10</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Dave Feldman: <blockquote>Lately I’ve seen a number of iPhone / Android comparisons suggesting that for the typical user, you can’t go wrong. These baffle me; I’ll get to why in future installments. But a loss is not a shut-out, and there are critical areas where Android nails it while iPhone misses the mark.</blockquote>

Feldman brings a cool appraisal as someone trying to design an app, and use the platform. (Thanks @HotSoup for the link.)]]></description>
<dc:subject>apple android ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:628777aba538/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://plus.google.com/u/0/+GoogleMaps/posts/4Cm8CfXz2qS">
    <title>We’ve been happy to hear so many of you enjoying the interface &gt;&gt; Google Maps on Google+</title>
    <dc:date>2013-07-11T10:03:28+00:00</dc:date>
    <link>https://plus.google.com/u/0/+GoogleMaps/posts/4Cm8CfXz2qS</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>We’ve been happy to hear so many of you enjoying the interface and features of the new Google Maps app for Android, but we know some of you are missing an easy way to access maps offline. That’s why our engineering team has been working around the clock to add a "Make this map area available offline" card below the search box for easier access. And, if you still want some #thumbercise, typing “ok maps” will work too!</blockquote>

Wouldn't it have made more sense to include the dedicated card in the first place, instead of just the easter egg, since it had been decided there was demand for the feature? Classic "<a href="http://stopdesign.com/archive/2009/03/20/goodbye-google.html">forty shades of blue</a>" process from Google.]]></description>
<dc:subject>google maps design ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:6f951f2dd1a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mobileopportunity.blogspot.co.uk/2013/06/style-vs-substance-in-mobile-software.html">
    <title>Style v substance in mobile software &gt;&gt; Mobile Opportunity</title>
    <dc:date>2013-06-24T21:47:32+00:00</dc:date>
    <link>http://mobileopportunity.blogspot.co.uk/2013/06/style-vs-substance-in-mobile-software.html</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Michael Mace has been user testing mobile apps: <blockquote>The most common problem I saw in the tests was users struggling with mobile apps and websites that prioritized beauty over usability. Too often, we as an industry equate an app that looks simple with an app that’s easy to use. Those are two entirely different things. Stripping all the text out of an app and hiding all of the buttons makes for a beautiful demo at TechCrunch, but a horrible user experience for people who are trying to get something done with an app.</blockquote>

There's a free downloadable white paper too (though it demands details like name and email).]]></description>
<dc:subject>mobile ui ux apps</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:026c5c5db717/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://getwired.com/2013/06/12/content-not-the-chrome-apps-not-the-phone/">
    <title>Content, not the chrome. Apps, not the phone. &gt;&gt; getwired.com</title>
    <dc:date>2013-06-13T05:50:58+00:00</dc:date>
    <link>http://getwired.com/2013/06/12/content-not-the-chrome-apps-not-the-phone/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Wes Miller: <blockquote>Ahead of WWDC 2013, many people were still expecting Apple to add live tiles, and possibly widgets to iOS 7. I didn’t expect either, and as a result wasn’t terribly disappointed to see them not included (that might be an understatement on my part).<p>

At first glance, live tiles may seem like a no-brainer in any operating system. Tiles that provide you information from within an app… How could this go wrong?<p>

Here’s the problems that I have with live tiles in Windows 8, and why I think they wouldn’t make sense on iOS (either):</blockquote>

]]></description>
<dc:subject>widget ux ui apple</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:4fc6f0421ba9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:widget"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apple"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stratechery.com/2013/change-for-changes-sake/">
    <title>Change for change’s sake &gt;&gt; Stratechery</title>
    <dc:date>2013-05-09T20:39:46+00:00</dc:date>
    <link>http://stratechery.com/2013/change-for-changes-sake/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Ben Thompson: <blokquote>The original iPhone included three communications channels: Phone, SMS, and Mail.<p>

My homescreen has 10: Facebook, Twitter, Phone, Skype, Google Voice, WhatsApp, Messages, LINE, Lync, and Mail (and I have other, lesser-used channels on other screens). The vast majority of these channels didn’t exist in 2007, or weren’t widely used. Since then, social interaction has both exploded in use and fragmented in type, but iOS simply wasn’t designed to support multiple channels intelligently.</blockquote>

So a redesign is needed...]]></description>
<dc:subject>ios7 ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:0318ac65d379/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios7"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.businessweek.com/articles/2013-05-02/sonys-first-mover-disadvantage-in-smart-watches">
    <title>Sony's first-mover disadvantage in smart watches &gt;&gt; Businessweek</title>
    <dc:date>2013-05-03T14:47:15+00:00</dc:date>
    <link>http://www.businessweek.com/articles/2013-05-02/sonys-first-mover-disadvantage-in-smart-watches</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>Priced at $130, Sony’s 1.3-inch touchscreen watch wirelessly connects to Android (GOOG) smartphones using Bluetooth technology. The gadget alerts users to incoming calls and allows them to reply to e-mails or texts with an array of prewritten messages. It even connects to Facebook (FB) and Twitter and controls a wearer’s phone-based music library. The SmartWatch, about the size of an iPod nano, is a slightly smaller successor to Sony’s LiveView watch.</blockquote>

Gee, it's been out since 2010. Wonder why we aren't all wearing LiveView?

<blockquote>LiveView had more limited features and was hobbled by kinks.<p>

The newer model [released in 2012] is more stylish, but users can’t enter messages and it sometimes requires daily recharging and a stable connection just to tell time reliably. “Sony was ahead of its rivals to release a watch, but it takes more than an idea to create a hit product,” says Mito Securities analyst Keita Wakabayashi. </blockquote>

As the article points out, Sony has had - and missed - plenty of other first-mover advantages.]]></description>
<dc:subject>sony smartwatch ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:7bbad8a75a53/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:sony"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:smartwatch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://9to5mac.com/2013/04/29/jony-ive-paints-a-fresh-yet-familiar-look-for-ios-7/">
    <title>Jony Ive paints a fresh, yet familiar, look for iOS 7 &gt;&gt; 9to5Mac</title>
    <dc:date>2013-04-29T21:33:15+00:00</dc:date>
    <link>http://9to5mac.com/2013/04/29/jony-ive-paints-a-fresh-yet-familiar-look-for-ios-7/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>iOS 7 is codenamed “Innsbruck,” according to three people familiar with the OS. The interface changes include an all-new icon set for Apple’s native apps in addition to newly designed tool bars, tab bars, and other fundamental interface features across the system. iOS devices running the next-generation software reportedly have polarizing filters to decrease viewing angles of on-lookers.</blockquote>

The contrast between the old and the new Podcast app - under Forstall, now gone, and under Ive, now in charge - is dramatic. If the redesign follows that, iOS 7 should look good.]]></description>
<dc:subject>apple design ios ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:9ae84116664f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techcrunch.com/2013/04/20/cognitive-overhead/">
    <title>Cognitive overhead, or why your product isn’t as simple as you think &gt;&gt; TechCrunch</title>
    <dc:date>2013-04-21T21:18:50+00:00</dc:date>
    <link>http://techcrunch.com/2013/04/20/cognitive-overhead/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[David Lieb, of the makers of app Bump: <blockquote>To illustrate the difference between generic simplicity and cognitive simplicity, let’s look at a couple products that, on the surface, might be regarded as being simple to use, but rank in my book as some of the most cognitively complex products of late.<p>

QR Codes – Designed to check the simplicity boxes of speed, ubiquity, and small number of steps, QR codes really dropped the ball on cognitive overhead. “So it’s a barcode? No? It’s a website? Ok. But I open websites with my web browser, not my camera. So I take a picture of it? No, I take a picture of it with an app? Which app?”<p>

iCloud / PhotoStream – When we heard Steve Jobs preach the utopian future where all of our photos and data would be seamlessly synchronized among all our devices, we smelled the Apple simplicity we’d all grown to love. But in practice, iCloud is rife with cognitive overhead — it only backs up your most recent photos, it works on certain select apps but not others, you have to create an icloud.com email account for it to sync your mail and notes but not everything else. Oh, and it works on new iPhone and iPads and Macs running OS X v10.7.4 or later, but not your PC or Android tablet. Try explaining that to your mother.</blockquote>

There's quite a long list you could add to that. The "how to do it right" examples are great too.]]></description>
<dc:subject>design cognitive interface ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:bdc4c6dab78c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:cognitive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.pocketables.com/2013/03/microsoft-and-the-context-sensitive-search-problem.html">
    <title>Microsoft and the context-sensitive search problem &gt;&gt; Pocketables</title>
    <dc:date>2013-04-02T20:49:10+00:00</dc:date>
    <link>http://www.pocketables.com/2013/03/microsoft-and-the-context-sensitive-search-problem.html</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[William Devereux: <blockquote>Based on these two recent Windows 8 developments, one has to wonder if Microsoft is going the Windows Phone route with the Windows 8 Charms. With more and more Microsoft apps adding search functionality to the UI, could the Charms be pushed into the background? It seems unlikely that Microsoft would remove them entirely, but why duplicate the functionality? And what will happen if the Search Charm is used for some apps while a dedicated search box is found in others?<p>

The problem, of course, lies with the users, who seem to have trouble either finding the Charms or comprehending how they work. One could argue that this is a design flaw and that the Charms aren’t discoverable enough, but what about Windows Phone’s dedicated search button? It’s always right there in front of you at the bottom of the screen, yet it still proved to be too confusing for people.</blockquote>]]></description>
<dc:subject>microsoft ux context</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:e532c419d1f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:context"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://allthingsd.com/20130321/a-universal-remote-thats-a-touch-too-much/">
    <title>Logitech Harmony Touch Review &gt;&gt; AllThingsD</title>
    <dc:date>2013-03-21T16:01:03+00:00</dc:date>
    <link>http://allthingsd.com/20130321/a-universal-remote-thats-a-touch-too-much/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Bonnie Cha: <blockquote>I’ve been using the Harmony Touch for the past week, and there’s a lot to like about the remote. Setup is easy. The touchscreen provides one-touch access to 50 of your favorite channels, and you can use gestures to perform various tasks. That said, it also poses some problems.<p>
Due to the location of the remote’s 2.4in display, some key buttons are placed out of easy reach. Those who like physical buttons might also take issue with the remote’s reliance on the touchscreen for things like entering channel numbers.<p>
But the biggest hurdle may be its expensive $250 price tag. At this point, the touchscreen is a nice-to-have feature, not a must-have, so it’s not worth the extra cost.</blockquote>

If you ever needed proof of the ocean between hardware companies - which solve problems by adding more buttons (or touch screens) - and software companies, which solve problems by repurposing features and adapting to the user, here it is.

Also: <em>$250??</em>]]></description>
<dc:subject>hardware software ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:6dff9eaba06f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</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 &gt;&gt; Boxes and Arrows</title>
    <dc:date>2013-03-18T18:03:40+00:00</dc:date>
    <link>http://boxesandarrows.com/let-them-pee-avoiding-the-sign-upsign-in-mobile-antipattern/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Greg Nudelman: <blockquote>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.<p>

This antipattern seems to be going away more and more as companies are beginning to figure out the following simple UX equation:<br />Long sign-up form before you can use the app = Delete app<p>
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.</blockquote>

The case study he then cites is priceless.]]></description>
<dc:subject>design ux ui charlesarthur</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:7a5628094b00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.techradar.com/news/phone-and-communications/mobile-phones/gimmick-watch-which-galaxy-s4-features-are-actually-useful-1137782">
    <title>Gimmick watch: which Galaxy S4 features are actually useful? &gt;&gt; TechRadar</title>
    <dc:date>2013-03-17T21:45:44+00:00</dc:date>
    <link>http://www.techradar.com/news/phone-and-communications/mobile-phones/gimmick-watch-which-galaxy-s4-features-are-actually-useful-1137782</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[By their count, not that many. (Thanks @beardyweirdy666 for the link.)]]></description>
<dc:subject>samsung galaxy ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:2a4ceae4399e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:samsung"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:galaxy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zdnet.com/will-90-percent-of-users-always-hate-windows-8-7000012348/">
    <title>Will 90% of users always hate Windows 8? &gt;&gt; ZDNet</title>
    <dc:date>2013-03-12T21:29:19+00:00</dc:date>
    <link>http://www.zdnet.com/will-90-percent-of-users-always-hate-windows-8-7000012348/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Matt Baxter-Reynolds: <blockquote>There's another category of people that fit into the 90% [of users who aren't "experts" or "willing adopters"]. They're not really "don't care" types, they're more "they shouldn't have to care." My dad is an older gentlemen (sorry, dad!), and in November he needed to replace his aging Vista laptop. I suggested he get a Windows 8 laptop, which he did. He bought a Dell. No touchscreen, but otherwise decent specs.<p>

It arrived, but I forgot about it for a couple of months until he had a problem whereupon I popped round to fix it. I asked him how he found Windows 8. His reply was: "I hate it." This in and of itself was not entirely unexpected. But what happened next left me feeling profoundly guilty. I watched him try and do simple tasks and saw him again and again just floored by Windows 8's odd usability modes.</blockquote>

It's not just parents; people who have been used to Windows XP and Windows Vista and Windows 7 - hundreds of millions of people who just want a computer they can use - are discovering whether they're in the 10%, or 90%. Don't miss the <a href="http://www.zdnet.com/the-mailbag-what-you-said-about-90-percent-of-users-hating-windows-8-7000012495/">followup article</a>, which examines his mailbag. There are plenty of 90%ers in there. (And in the comments, of which there are more than 600.)]]></description>
<dc:subject>windows8 microsoft usability ux charlesarthur</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:2129351ff321/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:windows8"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://martinbelam.com/2013/ultraviolet/">
    <title>Getting ultraviolent about UltraViolet™ &gt;&gt; Martin Belam</title>
    <dc:date>2013-03-07T14:53:25+00:00</dc:date>
    <link>http://martinbelam.com/2013/ultraviolet/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[User experience (UX) designer Martin Belam: <blockquote>A good UX can be hard to quantify, but you sure know when you are having a bad one. And over Christmas I stumbled over a really good example of a bad one.<p>

Regular readers may have noticed that I quite like Doctor Who, and so of course Santa brought me the latest DVD box set for Christmas. It includes the new UltraViolet™ feature of making digital copies available to owners of the physical product.<p>

The instructions come in a leaflet in the box, and I was eager to try it out. </blockquote>

Anyone had a <em>good</em> experience with Ultraviolet?]]></description>
<dc:subject>ultraviolet drm films ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:956b66245f7e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ultraviolet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:films"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dcurt.is/yours-vs-mine">
    <title>Yours vs. Mine &gt;&gt; Dustin Curtis</title>
    <dc:date>2013-02-12T06:32:19+00:00</dc:date>
    <link>http://dcurt.is/yours-vs-mine</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>A question that inevitably comes up very early in the process of designing a new app is this: should the interface refer to the user as “your” or “my” when talking about the user’s stuff, like in “my profile” or “your settings”? For a long time, this question ate at my soul. Which is right?</blockquote>

Well?]]></description>
<dc:subject>design interface ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:280ed4421376/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://macorios.com/files/iPhone-Settings-Mind-Map.html">
    <title>iPhone Settings Mind Map &gt;&gt; macorios.com</title>
    <dc:date>2012-12-11T07:03:26+00:00</dc:date>
    <link>http://macorios.com/files/iPhone-Settings-Mind-Map.html</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>I made an outline which contains all iPhone 5 iOS 6.0.1 settings from the iPhone itself and from the preinstalled apps. I did this with the iPhone setup with English as the OS language and German for time formats and so on. I tried to write everything down, but I couldn't write down some things, like Japanese characters and such. So the mind-map competition should be about 98 % or more.</blockquote>

Simplicity itself. Android and Windows Phone next?]]></description>
<dc:subject>ios iphone ux charlesarthur</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:2e98cc593578/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.androidpolice.com/2012/09/18/ux-things-i-hate-about-android/">
    <title>Stock Android isn't perfect: these are the things I can't stand about Jelly Bean &gt;&gt; Android Police</title>
    <dc:date>2012-12-06T12:48:42+00:00</dc:date>
    <link>http://www.androidpolice.com/2012/09/18/ux-things-i-hate-about-android/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Ron Mateo: <blockquote>Stock Android isn't perfect either, and that's what we're here to talk about today. Jelly Bean has all sorts of confusing user interfaces, weird bugs, things that don't make any sense, and things that desperately need polishing.<p>
I criticize because I care - that goes for Sense, TouchWiz, and MotoBlur too. I want the Android user experience to be good, and this is a big component in making it better - open, honest discussion of what sucks (and, hopefully, receptive developers). If you always think everything is awesome all the time, and that polish, "nit picking," and user experience don't matter, then you turn into desktop Linux. No one wants that.</blockquote>

A really thoughtful, user-experience-led piece. Matias Duarte, head of Android's design, consistency and UI team, responds (briefly) at the end.]]></description>
<dc:subject>android design google mobile ux charlesarthur</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:9e475cd3944c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.useit.com/alertbox/windows-8.html">
    <title>Windows 8 — disappointing usability for both novice &amp; power users &gt;&gt; Jakob Nielsen's Alertbox</title>
    <dc:date>2012-11-19T14:38:11+00:00</dc:date>
    <link>http://www.useit.com/alertbox/windows-8.html</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Jakob Nielsen: <blockquote>One of the most promising design ideas in Windows 8 is the enhanced use of generic commands in the form of the so-called "charms." The charms are a panel of icons that slide in from the screen's right side after a flicking gesture from its right edge (on a tablet) or after pointing the mouse to the screen's upper-right corner (on a computer).<p>
The charms panel includes features like Search, Share (including email), and Settings that apply to whatever content the user is currently viewing. In principle, it's great to have these commands universally available in a single, uniform design that's always accessed the same way.<p>

In practice, the charms work poorly — at least for new users. The old saying, out of sight, out of mind, turned out to be accurate. Because the charms are hidden, our users often forgot to summon them, even when they needed them. In applications such as Epicurious, which included a visible reminder of the search feature, users turned to search much more frequently.<p>

Hiding commands and other GUI chrome makes sense on small mobile phones. It makes less sense on bigger tablet screens. And it makes no sense at all on huge PC screens.</blockquote>]]></description>
<dc:subject>microsoft ui usability ux windows8</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:f7a375857f1b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:windows8"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://skeu.it/">
    <title>Skeu It!</title>
    <dc:date>2012-11-08T15:49:45+00:00</dc:date>
    <link>http://skeu.it/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Skeuomorphism skeuered, hliariously.]]></description>
<dc:subject>design ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:af54a2c5fb50/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://counternotions.com/2012/11/05/sirjony/">
    <title>Apple’s design problems aren’t skeuomorphic &gt;&gt; counternotions</title>
    <dc:date>2012-11-06T22:06:38+00:00</dc:date>
    <link>http://counternotions.com/2012/11/05/sirjony/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>In the end, what’s wrong with iOS isn’t the dark linen behind the app icons at the bottom of the screen, but the fact that iOS ought to have much better inter-application management and navigation than users fiddling with tiny icons. I’m fairly sure most Apple users would gladly continue to use what are supposed to be skeuomorphically challenged Calendar or Notebook apps for another thousand years if Apple could only solve the far more vexing software problems of AppleID unification when using iTunes and App Store, or the performance and reliability of the same. And yet these are the twin sides of the same systems design problem: the display layer surfacing or hiding the power within or, increasingly, lack thereof.</blockquote>

Well said.]]></description>
<dc:subject>apple design ios ux ui charlesarthur</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:1157207e7289/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://getwired.com/2012/10/28/ios-is-showing-its-age/">
    <title>iOS is showing its age &gt;&gt; getwired.com</title>
    <dc:date>2012-10-29T11:07:27+00:00</dc:date>
    <link>http://getwired.com/2012/10/28/ios-is-showing-its-age/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Wes Miller: <blockquote>iOS should have an option, on by default to update in the background. More importantly, in an ecosystem where too many app authors do the bare minimum in terms of security, apps should have that same option.<p>

The original iPhone succeeded not because of apps. No, it succeeded because it was a better, more usable phone than almost anything else on the market. It just worked. It had voicemails we could see before listening, contacts we could easily edit on the phone, and a Web browser that was better than any mobile browser we’d ever seen before.<p>

But the OS is showing its age. Little nuances like the somewhat functional search screen, Favorites in Contacts, and VIPs in Mail show that iOS is under structural pressure to deal with the volume of data it tries to display in a viable way. Notifications and the Settings app seem fragmented and are starting to become as disorganized as the Windows Control Panel (that’s bad!). Photo Stream sharing is a joke. It’s unusable. The edges are showing.</blockquote>]]></description>
<dc:subject>ios apple iphone ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:628e3a657f38/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://skydrive.live.com/?cid=d57e836204feb061&amp;id=D57E836204FEB061%213317&amp;sff=1">
    <title>Why can't you have just three columns in Windows 8? &gt;&gt; Tim Anderson</title>
    <dc:date>2012-08-23T22:18:27+00:00</dc:date>
    <link>https://skydrive.live.com/?cid=d57e836204feb061&amp;id=D57E836204FEB061%213317&amp;sff=1</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Running the RTM, and wants to have three columns, not four. Watch the video..]]></description>
<dc:subject>windows8 ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:5a01fe09d26e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:windows8"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.currybet.net/cbet_blog/2012/08/never-open-external-links-in-new-windows.php">
    <title>Why your news site should never open external links in a new window &gt;&gt; Martin Belam</title>
    <dc:date>2012-08-23T22:06:20+00:00</dc:date>
    <link>http://www.currybet.net/cbet_blog/2012/08/never-open-external-links-in-new-windows.php</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>Imagine a not-too-distant world where you are manipulating your device mostly by touch and voice, and the whole document paradigm might have vanished. Operating systems might not have “new windows” in the future, just as browsers didn’t used to have tabs.<p>

Opening up an external link in a new window basically shouts out “Darling, don’t leave me!”, with your site sobbing in the background like a jilted lover.</blockquote>

There are other pertinent accessibility reasons too.]]></description>
<dc:subject>browser ux ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:721a42724991/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesign/">
    <title>A brief rant on the future of interaction design &gt;&gt; Bret Victor</title>
    <dc:date>2012-06-21T20:29:31+00:00</dc:date>
    <link>http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesign/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[It's all about the hands, but also other things. Read.]]></description>
<dc:subject>ux ui design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:3004b40b4f37/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vimeo.com/43224490">
    <title>Sharp AQUOS Android Smartphone: Feel UX &gt;&gt; Vimeo</title>
    <dc:date>2012-06-20T06:15:00+00:00</dc:date>
    <link>http://vimeo.com/43224490</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[An interesting rethink of the Android UI by frog, the designers. Very attractive: note how it's using Microsoft typefaces in the video, and Windows Phone-like tiling. Get used to competition in how Android UIs look as smartphone penetration explodes.]]></description>
<dc:subject>sharp android ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:8ed166f8ee45/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:sharp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.totalmedia.co.uk/insights/news/145">
    <title>What do people do with tablets, and where? &gt;&gt;Total Research</title>
    <dc:date>2012-05-29T05:26:16+00:00</dc:date>
    <link>http://www.totalmedia.co.uk/insights/news/145</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[From March, but always good to have data from a large survey: <blockquote>People who own tablet computers spend more time and money on the internet than anyone else in Britain. This is according to research commissioned by Total Media into how tablet technology has, and will, affect the population in terms of media consumption and behaviour. The quantitative study of more than 1,000 nationally representative respondents identified that 79% of tablet owners mostly use the device at home, with a further 33% saying that the tablet has affected their behaviour in the home.</blockquote>]]></description>
<dc:subject>tablets data ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:b60f61e7515c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:tablets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loper-os.org/?p=861">
    <title>Engelbart’s Violin &gt;&gt; Loper OS</title>
    <dc:date>2012-05-29T05:22:49+00:00</dc:date>
    <link>http://www.loper-os.org/?p=861</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[<blockquote>Fascinating as the chorded keyboard is, its confinement to the ghetto of “crackpot technology” is but a symptom of the underlying disease: <a href="http://www.loper-os.org/?p=316">the total victory of the technological business model which caters primarily to the unskilled</a>.</blockquote>

Looking at the intriguing question of why the chorded keyboard never took off as an input mechanism.]]></description>
<dc:subject>interface technology ui ux charlesarthur</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:72b0a61de06c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.youtube.com/watch?v=XeeOkHjV7nM">
    <title>Joe Pirillo uses Mac OS X for the first time &gt;&gt; YouTube</title>
    <dc:date>2012-03-15T06:45:25+00:00</dc:date>
    <link>http://www.youtube.com/watch?v=XeeOkHjV7nM</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Yesterday we <a href="http://www.guardian.co.uk/technology/blog/2012/mar/14/windows-8-user-interface-confusion">showed you Chris Pirillo's father using Windows 8 for the first time</a>. Now here he is using Mac OSX for the first time, and trying to find "the internet". 

Fascinating piece of user interface film: watch this before you judge users. (Pirillo senior is a confirmed Windows user, though he has used iPads and iPhones.)]]></description>
<dc:subject>apple userinterface ux ui osx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:02b07037d6c6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:userinterface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:osx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://icspapercuts.tumblr.com/">
    <title>ICS Paper Cuts &gt;&gt; Tumblr</title>
    <dc:date>2011-12-22T23:02:47+00:00</dc:date>
    <link>http://icspapercuts.tumblr.com/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[A Tumblr looking at UI inconsistencies or weirdnesses in Ice Cream Sandwich (aka Android 4.0). If you're presently on Android 2.x, you'll probably find ICS like moving into a new house where all the rooms have been rearranged. So, is there a similar Tumblr for iOS?]]></description>
<dc:subject>charlesarthur ics android ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:5964577bfd2a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.elezea.com/2011/12/google-path-ui-design/">
    <title>Google Circles and Path 2.0: How good UI design cannot fix a broken solution</title>
    <dc:date>2011-12-21T22:42:31+00:00</dc:date>
    <link>http://www.elezea.com/2011/12/google-path-ui-design/</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA["There are inherent problems with binary social networks. The idea that someone is either full-on in your life (and therefore has access to everything about you) or not at all is not how it works offline. You tend to share certain information only with certain groups of people. Only some people will be interested in photos of your new puppy, whereas those same people will probably not be interested in blog posts about your work.

Google Circles aims to solve these problems by allowing you to drag and drop people into distinct buckets, and letting you only share what you want with each circle. And yes, the UI makes it really easy to do this. It’s great design."

But it's impossible for that great design to make up for the fact that you can't maintain the listing of who belongs in which circles (or overlapping circles) for any length of time.]]></description>
<dc:subject>google+ design twitter ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:guardiantech/b:8caed0e55d3c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:google+"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mrgan.tumblr.com/post/10492926111/labeling-the-back-button">
    <title>Labeling the Back button &gt;&gt; Neven Mrgan's tumbl</title>
    <dc:date>2011-11-08T23:11:07+00:00</dc:date>
    <link>http://mrgan.tumblr.com/post/10492926111/labeling-the-back-button</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA[Very good, and surprisingly subtle, usability advice]]></description>
<dc:subject>charlesarthur iOS UX</dc:subject>
<dc:identifier>https://pinboard.in/u:guardiantech/b:53a562de907a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:iOS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:UX"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://googlesystem.blogspot.com/2011/07/google-tests-interface-optimized-for.html">
    <title>Google tests an interface optimized for infinite scrolling &gt;&gt; Unofficial Google Blog</title>
    <dc:date>2011-07-20T20:32:31+00:00</dc:date>
    <link>http://googlesystem.blogspot.com/2011/07/google-tests-interface-optimized-for.html</link>
    <dc:creator>guardiantech</dc:creator><description><![CDATA["Alon Laudon spotted a new experimental interface for Google's results pages. The most important change is that most navigation elements continue to be visible even when you scroll down. The navigation bar, the search box and the search options sidebar have a fixed position, which means that you no longer have scroll to the top of the page to edit the query or switch to a specialized search engine."<br />
<br />
Is it bad that a first reaction was "I wonder when that was patented?"]]></description>
<dc:subject>google search charlesarthur ui ux</dc:subject>
<dc:identifier>https://pinboard.in/u:guardiantech/b:1e26dca5c9ba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:charlesarthur"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:guardiantech/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>