<?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 (rahuldave)</title>
    <link>https://pinboard.in/u:rahuldave/public/</link>
    <description>recent bookmarks from rahuldave</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.zeldman.com/2012/02/28/a-list-apart-no-345-responsive-content-thinking-beyond-pages-from-research-to-content-strategy-to-meaningful-project-deliverables/"/>
	<rdf:li rdf:resource="http://feeds.arstechnica.com/~r/arstechnica/index/~3/OnPurZT2VuY/design-student-scores-apple-internship-to-spiff-up-ios-notifications.ars"/>
	<rdf:li rdf:resource="http://www.zeldman.com/2010/12/10/anatomy-of-the-goodreads-com-friend-spam-dark-pattern/"/>
	<rdf:li rdf:resource="http://www.zeldman.com/2010/04/14/designing-for-ipad/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.zeldman.com/2012/02/28/a-list-apart-no-345-responsive-content-thinking-beyond-pages-from-research-to-content-strategy-to-meaningful-project-deliverables/">
    <title>A List Apart No. 345: Responsive content: thinking beyond pages; from research to content strategy to meaningful project deliverables.</title>
    <dc:date>2012-02-28T14:39:07+00:00</dc:date>
    <link>http://www.zeldman.com/2012/02/28/a-list-apart-no-345-responsive-content-thinking-beyond-pages-from-research-to-content-strategy-to-meaningful-project-deliverables/</link>
    <dc:creator>rahuldave</dc:creator><description><![CDATA[

IN ISSUE NO. 345 of A List Apart, for people who make websites:

Future-Ready Content
by SARA WACHTER-BOETTCHER

The future is flexible, and we’re bending with it. From responsive web design to futurefriend.ly thinking, we’re moving quickly toward a web that’s more fluid, less fixed, and more easily accessed on a multitude of devices. As we embrace this shift, we need to relinquish control of our content as well, setting it free from the boundaries of a traditional web page to flow as needed through varied displays and contexts. Most conversations about structured content dive headfirst into the technical bits: XML, DITA, microdata, RDF. But structure isn’t just about metadata and markup; it’s what that metadata and markup mean. Sara Wachter-Boettcher shares a framework for making smart decisions about our content’s structure.

Audiences, Outcomes, and Determining User Needs
by COREY VILHAUER

Every website needs an audience. And every audience needs a goal. Advocating for end-user needs is the very foundation of the user experience disciplines. We make websites for real people. Those real people are able to do real things. But how do we get to really know our audience and find out what these mystery users really want from our sites and applications? Learn to ensure that every piece of content on your site relates back to a specific, desired outcome — one that achieves business goals by serving the end user. Corey Vilhauer explains the threads that bind UX research to content strategy and project deliverables that deliver.


Illustration by Kevin Cornell for A List Apart






]]></description>
<dc:subject>A_List_Apart content_strategy Responsive_Web_Design Usability User_Experience UX</dc:subject>
<dc:identifier>https://pinboard.in/u:rahuldave/b:597ff8eccf6a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:A_List_Apart"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:content_strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Responsive_Web_Design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:User_Experience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:UX"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://feeds.arstechnica.com/~r/arstechnica/index/~3/OnPurZT2VuY/design-student-scores-apple-internship-to-spiff-up-ios-notifications.ars">
    <title>Apple aiming to improve iOS notifications further with fresh talent</title>
    <dc:date>2011-12-13T18:45:00+00:00</dc:date>
    <link>http://feeds.arstechnica.com/~r/arstechnica/index/~3/OnPurZT2VuY/design-student-scores-apple-internship-to-spiff-up-ios-notifications.ars</link>
    <dc:creator>rahuldave</dc:creator><description><![CDATA[  
  
  
  

        
    If being a successful jailbreak developer can get you hired at Apple, apparently so can redesigning the oft-criticized Notification Center. Apple has hired Jan-Michael Cart, perhaps best known for creating demos of proposed Notification Center tweaks, to intern with the company for the next seven months. Cart's internship follows two other recent hires known for notification work, suggesting the company is aware that iOS notifications still need some work.


Cart, currently a junior majoring in Mass Media Arts at the Univeristy of Georgia (go Bulldogs!), specializes in video and graphic design. He has recently begun experimenting with Xcode and learning about iOS development, according to his website. With the release of iOS 5, Cart began creating videos to demonstrate his ideas for improving its Notification Center feature.
    
          
      
        
    


      Read the comments on this post


   
]]></description>
<dc:subject>News Apple design internship ios iphone notifications ui ux</dc:subject>
<dc:identifier>https://pinboard.in/u:rahuldave/b:979a8ebf29d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:News"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:internship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:ios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:notifications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zeldman.com/2010/12/10/anatomy-of-the-goodreads-com-friend-spam-dark-pattern/">
    <title>Anatomy of the Goodreads.com Friend Spam Dark Pattern</title>
    <dc:date>2010-12-10T13:18:11+00:00</dc:date>
    <link>http://www.zeldman.com/2010/12/10/anatomy-of-the-goodreads-com-friend-spam-dark-pattern/</link>
    <dc:creator>rahuldave</dc:creator><description><![CDATA[“Goodreads.com is social cataloging service for books. In this post you will see how they’ve used the friend spam dark pattern, but how they’ve also failed to make it go viral. This makes it interesting to carry out a post mortem and work out what they should have done.”

—Anatomy of the Goodreads.com Friend Spam Dark Pattern

(Hat tip: Andrew Travers.)





]]></description>
<dc:subject>Community Design UX Urbanism Usability User_Experience tweets twitter</dc:subject>
<dc:identifier>https://pinboard.in/u:rahuldave/b:e11718a09f8c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:UX"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Urbanism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:User_Experience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:tweets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:twitter"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zeldman.com/2010/04/14/designing-for-ipad/">
    <title>Design Lessons from iPad</title>
    <dc:date>2010-04-14T11:04:04+00:00</dc:date>
    <link>http://www.zeldman.com/2010/04/14/designing-for-ipad/</link>
    <dc:creator>rahuldave</dc:creator><description><![CDATA[






It’s only Wednesday but we already have our link of the week. Although they call it merely a “quick write-up” (and it is a fast read), iA’s mini-compendium of design insights before and after the appearance of the iPad at their office should be required reading for all web, app, and/or interaction designers.

In the equivalent of a breathlessly quick seminar presentation, iA discusses typographic resolution and feel; the effect of the device’s brilliant contrast on readability; the kitsch produced by rigorously adhering to Apple’s “make it 3D” guidelines; whether metaphors work; and more—all of it well worth far more than the little time it will take you to absorb.

In particular, I call your attention to the section entitled, “Interaction Design: So What Works?” Although intended as a guideline to producing well-tuned iPad apps, it also works splendidly as a mini-guide to creating better websites, much like Luke Wroblewski’s brilliant “Mobile First” presentation at last week’s An Event Apart, which carried a similar message:



The limited screen estate and the limited credit on the number of physical actions needed to complete one task (don’t make me swipe and touch too often), pushes the designer to create a dead simple information architecture and an elaborate an interaction design pattern with a minimal number of actions. This goes hand in hand with the economic rule of user interaction design: Minimize input, maximize output.
Since the smallest touch point for each operation is a circle of the size of a male index finger tip, we cannot cram thousands of features (or ads!) in the tight frame; we have to focus on the essential elements. Don’t waste screen estate and user attention on processing secondary functions.
We found that the iPad applications we designed, made it relatively easy to be translated back into websites. The iPad could prove to be a wonderful blue print to design web sites and applications. If it works on the iPad, with a few tweaks, it will work on a laptop.


Via iA  » Designing for iPad: Reality Check.
















]]></description>
<dc:subject>Apple Applications Design Information_architecture Platforms UX Usability User_Experience Web_Design apps architecture industry ipad estate reality interaction check resolution actions splendidly</dc:subject>
<dc:identifier>https://pinboard.in/u:rahuldave/b:f463506c9387/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Applications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Information_architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:UX"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:User_Experience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:Web_Design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:apps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:industry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:ipad"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:estate"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:reality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:interaction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:check"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:resolution"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:actions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rahuldave/t:splendidly"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>