earth2marsh + design 450
Coding Horror: Visualizing Code to Fail Faster
3 days ago by earth2marsh
"Yes, it's artsy, yes these are mostly toy projects, but this isn't entirely abstract art house visualization nonsense. Designing tools that let you make rapid changes, and see the effects of those changes as soon as possible can be transformative."
coding
programming
ide
ides
design
fail
failure
3 days ago by earth2marsh
You Are Solving The Wrong Problem | UX Magazine
3 days ago by earth2marsh
"What's the take-away? When you are solving a difficult problem re-ask the problem so that your solution helps you learn faster. Find a faster way to fail, recover, and try again. If the problem you are trying to solve involves creating a magnum opus, you are solving the wrong problem."
ux
flight
problems
solving
design
3 days ago by earth2marsh
Research Blog: Is beautiful usable? What is the influence of beauty and usability on reactions to a product?
6 days ago by earth2marsh
Product usability and aesthetics are coexistent, but they are not identical. To understand how usability and aesthetics influence reactions to a product, we conducted an experimental lab study with 80 participants. We created four versions of an online clothing shop varying in beauty (high vs. low) and usability (high vs. low). Participants had to find a number of items in one of those shops and buy them. To understand how the factors of beauty and usability influence final users happiness, we measured how they much they liked the shop before and after interaction.
The results showed that the beauty of the interface did not affect how users perceived the usability of the shops: Participants (or Users) were capable of distinguishing if a product was usable or not, no matter how nice it looked. However, the experiment showed that the usability of the shops influenced how users rated the products' beauty. Participants using shops with bad usability rated the shops as less beautiful after using the shops. We showed that poor usability lead to frustration, which put the users in a bad mood and made them rate the product as less beautiful than before interacting with the shop
design
beauty
usability
via:jen
The results showed that the beauty of the interface did not affect how users perceived the usability of the shops: Participants (or Users) were capable of distinguishing if a product was usable or not, no matter how nice it looked. However, the experiment showed that the usability of the shops influenced how users rated the products' beauty. Participants using shops with bad usability rated the shops as less beautiful after using the shops. We showed that poor usability lead to frustration, which put the users in a bad mood and made them rate the product as less beautiful than before interacting with the shop
6 days ago by earth2marsh
All Presentation Software is Broken - igvita.com
13 days ago by earth2marsh
"I've instrumented my RailsConf presentation (Making the Web Faster) with Google Analytics, where I'm tracking slide transitions and clicks via custom events and time on slide via the user timings API:"
analytics
design
powerpoint
presentation
software
web
google:analytics
13 days ago by earth2marsh
Usage Patterns For Client-Side URI parameters
21 days ago by earth2marsh
"Designers of URIs have traditionally used ? to encode server-side parameters. At its inception, the Web also introduced fragment identifiers (preceded by # ) as a means of addressing specific locations in a document. As highly interactive applications get built using Web parts (HTML, CSS and JavaScript component resources that are themselves Web addressible — see [tvr-cacm2009], there is an increasing need for encoding interaction state as part of the URI. The Web is beginning to discover and codify design patterns based on fragment identifiers for many of these use cases."
uri
url
w3c
design
hash
hashes
hashbang
21 days ago by earth2marsh
Coding Horror: This Is All Your App Is: a Collection of Tiny Details
22 days ago by earth2marsh
"Your software, your product, is nothing more than a collection of tiny details. If you don't obsess over all those details, if you think it's OK to concentrate on the "important" parts and continue to ignore the other umpteen dozen tiny little ways your product annoys the people who use it on a daily basis – you're not creating great software. Someone else is. I hope for your sake they aren't your competitor.
The details are hard. Everyone screws up the details at first, just like Petmate did with the first version of this automatic feeder. And it's OK to screw up the details initially, provided …
you're getting the primary function more or less right.
you're listening to feedback from the people who use your product, and actively refining the details of your product based on their feedback every day."
design
development
quality
software
details
jeff_atwood
The details are hard. Everyone screws up the details at first, just like Petmate did with the first version of this automatic feeder. And it's OK to screw up the details initially, provided …
you're getting the primary function more or less right.
you're listening to feedback from the people who use your product, and actively refining the details of your product based on their feedback every day."
22 days ago by earth2marsh
On Linking – Part 1
4 weeks ago by earth2marsh
"Linking is the most under-utilized aspects in modern RESTful apps. Without linking, what we are building today are essentially POXy REST apps. I categorize a well-designed POXy REST app as one that is built as follows:
Models resources at the right granularity such that it can constrain the set of operations to a uniform interface.
Lets clients use the uniform interface in the manner defined by HTTP 1.1, i.e., uses GET for safe and idempotent read-only operations, PUT to update resources, DELETE to delete resources, and POST to create new sub-ordinate resources.
Uses media types such as application/xml or
application/json (should I call this POJO REST instead?) to represent data.
Uses representations, content negotiation, and conditional requests – i.e. it takes full advantage of HTTP as an application protocol."
hypermedia
rest
restful
apis
design
subbu
links
linking
urls
Models resources at the right granularity such that it can constrain the set of operations to a uniform interface.
Lets clients use the uniform interface in the manner defined by HTTP 1.1, i.e., uses GET for safe and idempotent read-only operations, PUT to update resources, DELETE to delete resources, and POST to create new sub-ordinate resources.
Uses media types such as application/xml or
application/json (should I call this POJO REST instead?) to represent data.
Uses representations, content negotiation, and conditional requests – i.e. it takes full advantage of HTTP as an application protocol."
4 weeks ago by earth2marsh
The Dimensions of API Fidelity | Cloud Computing Software from Eucalyptus
5 weeks ago by earth2marsh
"With the agreement between Eucalyptus and Amazon to cooperate on ensuring API fidelity between the two technologies comes the question of defining what it means for two independent implementations to support the same API. The API itself consists of a large number of different "commands" or "service requests," each of which triggers many different operations within the system that are visible to the user. Moreover, the API makes specific assumptions about "things" (VMs, storage volumes, network addresses, etc.) it is defining and manipulating. Launching two different VMs with different network and storage characteristics through the identical API call doesn't capture fidelity.
Thus, API fidelity measures three dimensions of compatibility in the interface "calls" it implements:
the calls and parameterizations of each call
the actionable responses generated by each call
the similarity between the objects manipulated by each call"
api
apis
compatibility
design
amazon
eucalyptus
Thus, API fidelity measures three dimensions of compatibility in the interface "calls" it implements:
the calls and parameterizations of each call
the actionable responses generated by each call
the similarity between the objects manipulated by each call"
5 weeks ago by earth2marsh
legal - Is copying an API a breach of copyright? - Stack Overflow
5 weeks ago by earth2marsh
"Section 1201(f) of the DMCA states that "a person who has lawfully obtained the right to use a copy of a computer program may circumvent a technological measure that effectively controls access to a particular portion of that program for the sole purpose of identifying and analyzing those elements of the program that are necessary to achieve interoperability of an independently created computer program with other programs." Doesn't this solve the reverse-engineering problem?
This exemption is inadequate for several reasons. First, reverse-engineering has many legitimate uses beyond strict interoperability that are not allowed by the DMCA. Significantly, one might reverse-engineer in order to build a competitive product, but such reverse-engineering is not permitted. Other legitimate uses that are not exempted include: verifying proper operation of a program; discovering undocumented features; or correcting bugs in the external specifications of an application.
Second, "interoperability" is narrowly defined by the DMCA as meaning "the ability of computers to exchange information, and of such programs mutually to use the information which has been exchanged." By restricting interoperability to information exchange, the DMCA excludes other legitimate types of interoperability such as API-level replacements for computer libraries..."
api
apis
copying
design
pattern
This exemption is inadequate for several reasons. First, reverse-engineering has many legitimate uses beyond strict interoperability that are not allowed by the DMCA. Significantly, one might reverse-engineer in order to build a competitive product, but such reverse-engineering is not permitted. Other legitimate uses that are not exempted include: verifying proper operation of a program; discovering undocumented features; or correcting bugs in the external specifications of an application.
Second, "interoperability" is narrowly defined by the DMCA as meaning "the ability of computers to exchange information, and of such programs mutually to use the information which has been exchanged." By restricting interoperability to information exchange, the DMCA excludes other legitimate types of interoperability such as API-level replacements for computer libraries..."
5 weeks ago by earth2marsh
mnot’s blog: User Personas for HTTP APIs
6 weeks ago by earth2marsh
"When you’re designing HTTP APIs, you need to keep a lot of concerns in mind. Stealing a page from XP, let’s look at some possible personas and their user stories for HTTP-based APIs:
JOE AT HUGECORP
Let’s start with the people who consume the APIs. Joe uses Java (or some similar statically typed language). He’s used to having good tool support,"
api
design
http
rest
personas
apis
JOE AT HUGECORP
Let’s start with the people who consume the APIs. Joe uses Java (or some similar statically typed language). He’s used to having good tool support,"
6 weeks ago by earth2marsh
Design Staff – Story-centered design: Hacking your brain to think like a user
9 weeks ago by earth2marsh
"Hack 3: Review stories on paper
When it’s time to review designs with the team, I almost never show individual screens. Instead, I’ll print out all the screens in a story, and lay them out on a long conference table or tape them to a wall.
This works so well because the team can get up close and see a single screen in full detail. They can take one step back, see the adjacent screens, and think about the transitions between screens. And they can step back even more to see the entire story, which helps keep everyone in agreement about the user goals and tasks that the screens need to support.
When I show work to other designers, I’ll skip the paper and just flip through screens on a computer — they’ll get it. But I find that the printing approach is incredibly helpful for working with engineers and PMs who don’t spend all day nerding out about interaction design like I do. Oh, and with paper you can draw notes directly on the designs and take them back to your desk to work on the next iteration
design
story
ux
When it’s time to review designs with the team, I almost never show individual screens. Instead, I’ll print out all the screens in a story, and lay them out on a long conference table or tape them to a wall.
This works so well because the team can get up close and see a single screen in full detail. They can take one step back, see the adjacent screens, and think about the transitions between screens. And they can step back even more to see the entire story, which helps keep everyone in agreement about the user goals and tasks that the screens need to support.
When I show work to other designers, I’ll skip the paper and just flip through screens on a computer — they’ll get it. But I find that the printing approach is incredibly helpful for working with engineers and PMs who don’t spend all day nerding out about interaction design like I do. Oh, and with paper you can draw notes directly on the designs and take them back to your desk to work on the next iteration
9 weeks ago by earth2marsh
John Sheehan : Don't build the best REST API, build the best HTTP API.
9 weeks ago by earth2marsh
"I’ve named the root element for the data ‘items’ again for strongly-typed langauges. Particularly in C# this in combination with generics makes deserialization cleaner."
John comments later:
"Imagine you're deserializing to C# objects. For each different resource you'll have to create a class definition to match the response. It's much easier to generalize if you can do `Items<T>` instead."
api
http
rest
design
collections
deserialization
arrays
John comments later:
"Imagine you're deserializing to C# objects. For each different resource you'll have to create a class definition to match the response. It's much easier to generalize if you can do `Items<T>` instead."
9 weeks ago by earth2marsh
Designing a better subway map: idsgn (a design blog)
10 weeks ago by earth2marsh
Massimo Vignelli
design
maps
subway
10 weeks ago by earth2marsh
Hypertext Style: Cool URIs don't change.
12 weeks ago by earth2marsh
One man's rant on URL design. Some good points about common mistakes.
"It the the duty of a Webmaster to allocate URIs which you will be able to stand by in 2 years, in 20 years, in 200 years. This needs thought, and organization, and commitment.
URIs change when there is some information in them which changes. It is critical how you design them. (What, design a URI? I have to design URIs? Yes, you have to think about it.). Designing mostly means leaving information out."
uri
url
design
w3c
"It the the duty of a Webmaster to allocate URIs which you will be able to stand by in 2 years, in 20 years, in 200 years. This needs thought, and organization, and commitment.
URIs change when there is some information in them which changes. It is critical how you design them. (What, design a URI? I have to design URIs? Yes, you have to think about it.). Designing mostly means leaving information out."
12 weeks ago by earth2marsh
App Store - JSON Designer
february 2012 by earth2marsh
A visual design tool for your JSON
iphone
ipad
ios
json
design
tool
apps
february 2012 by earth2marsh
Hidden gem: General principles for good URI design for RESTful and HTTP applications. : programming
february 2012 by earth2marsh
> Here's my perspective... I view URLs and HTTP as a serialization layer for communication between software processes (RPC).
Right. REST views it differently. That's what you're missing. REST is a means for computers to communicate, but not through procedure calls. They communicate through transferring stateful representations. Hence the name.
apis
design
api
rpc
comparison
uri
Right. REST views it differently. That's what you're missing. REST is a means for computers to communicate, but not through procedure calls. They communicate through transferring stateful representations. Hence the name.
february 2012 by earth2marsh
Domain-driven design: tackling complexity in the heart of software - Eric Evans - Google Books
february 2012 by earth2marsh
Amazon review: "If you have even been involved in a software project (a) as a developer and did not know what the end product is going to be used for or how it will be used or (b) as an architect who spent countless hours with your stakeholders and domain experts trying to figure out how to go about architecting your application, then you should read this book. Read it again after you have read it for the first time. This book is packed with pointers, information, tips, how-tos, "down to earth" practical samples, and even conversational examples that one could have while gathering requirements. Evans in his book fills a wide gap that we all tend to come across while designing software applications."
uri
design
software
objectoriented
book
cs
february 2012 by earth2marsh
Analysis patterns: reusable object models - Martin Fowler - Google Books
february 2012 by earth2marsh
"In Analysis Patterns: Reusable Object Models, Martin Fowler focuses on the end result of object-oriented analysis and design - the models themselves. He shares with you his wealth of object modeling experience and his keen eye for identifying repeating problems and transforming them into reusable models. Analysis Patterns provides a catalogue of patterns that have emerged in a wide range of domains including trading, measurement, accounting and organizational relationships. Recognizing that conceptual patterns cannot exist in isolation, the author also presents a series of "support patterns" that discuss how to turn conceptual models into software that in turn fits into an architecture for a large information system. Included in each pattern is the reasoning behind their design, rules for when they should and should not be used, and tips for implementation."
software
design
book
february 2012 by earth2marsh
on the importance of naming
february 2012 by earth2marsh
"Another way to get at this - when you discuss your application with end users (those who presumably know little about programming) what are the words they themselves use repeatedly?
Those are the words you should be designing your application around.
If you haven't yet had this conversion with prospective users - stop everything right now and don't write another line of code until you do! Only then will your team have an idea of what needs to be built.
I know nothing about financial software, but if I had to guess, I'd say some of the resources might go by names such as "Report", "Payment", "Transfer", and "Currency".
There are a number of good books on this part of the software design process. Two I can recommend are Domain Driven Design and Analysis Patterns."
uri
url
design
apis
Those are the words you should be designing your application around.
If you haven't yet had this conversion with prospective users - stop everything right now and don't write another line of code until you do! Only then will your team have an idea of what needs to be built.
I know nothing about financial software, but if I had to guess, I'd say some of the resources might go by names such as "Report", "Payment", "Transfer", and "Currency".
There are a number of good books on this part of the software design process. Two I can recommend are Domain Driven Design and Analysis Patterns."
february 2012 by earth2marsh
restful url - How to create REST URLs without verbs? - Stack Overflow
february 2012 by earth2marsh
Awesome post from Bob Aman on good URI design
uri
url
design
apis
bestpractices
february 2012 by earth2marsh
Stop Designing Pages And Start Designing Flows - Smashing UX Design | Smashing UX Design
january 2012 by earth2marsh
"Design flows that are tied to clear objectives allow us to create a positive user experience and a valuable one for the business we’re working for. In this article, we’ll show you how spending more time up front designing user flows leads to better results for both the user and business. Then we’ll look in depth at a common flow for e-commerce websites (the customer acquisition funnel), as well as provide tips on optimizing it to create a complete customer experience."
design
ux
web
webdesign
flows
conversions
conversion
january 2012 by earth2marsh
Kawamura Ganjavian - OSTRICH
january 2012 by earth2marsh
"Working patterns are constantly evolving. We gradually spend more time in our working environments, and this in turn means that we often need to make work and rest fully compatible within the same space. Some cultures have assimilated this concept more naturally than others, but in general the workplace has rarely adapted to this new working-resting paradigm."
design
pillow
sleep
ostrich
january 2012 by earth2marsh
Interactive Smooth CoffeeScript
january 2012 by earth2marsh
good interactive examples, though not obvious that they're interactive!
interactive
javascript
design
tutorial
tryme
examples
january 2012 by earth2marsh
Android Developers
january 2012 by earth2marsh
comprehensive dev portal
api
docs
apis
design
examples
android
development
january 2012 by earth2marsh
Design for developers
january 2012 by earth2marsh
I liked the bit in the beginning especially, in talking about what makes good tools.
design
developers
presentation
slides
interface
january 2012 by earth2marsh
The Documentation Dilemma - (37signals)
january 2012 by earth2marsh
At 37signals we’re firmly in the #1 camp. Designs go from concept to HTML (often in-app) without any deliverables in-between, and then from HTML mock to fully implemented feature in Ruby or JavaScript again without intermediate artifacts.
37signals
design
development
documentation
process
january 2012 by earth2marsh
dvdp
january 2012 by earth2marsh
oh wow. love.
animated
gifs
motion
art
design
inspiration
3d
gif
animation
from delicious
january 2012 by earth2marsh
Second-system effect - Wikipedia, the free encyclopedia
january 2012 by earth2marsh
"The second-system effect refers to the tendency of small, elegant, and successful systems to have elephantine, feature-laden monstrosities as their successors."
second
versions
systems
architecture
development
programming
design
software
from delicious
january 2012 by earth2marsh
TEDxSiliconAlley: Foursquare's Product Manager on The 5 Laws of Engagement - The Next Web
november 2011 by earth2marsh
"We seek comfort in relationships; We all have something to say; We need to feel important; We are hypnotized by beauty; We are captivated by the unknown"
foursquare
engagement
design
product
engament
TEDx
from delicious
november 2011 by earth2marsh
Asynchronous UIs - the future of web user interfaces
november 2011 by earth2marsh
Asynchronous UIs - the future of web user interfaces
javascript
Asynchronous
spine
design
apps
webdev
Client
Server
Applications
from delicious
november 2011 by earth2marsh
APIs are a Pain
november 2011 by earth2marsh
APIs are a Pain . I have seen the sneak preview and it is some amazing innovation by @sallamar & team @ #eBay
api
apis
client
rest
pain
design
Ebay
hateoas
from delicious
november 2011 by earth2marsh
Twilio Conference 2011: Steve Klabnik, Everything You Know About REST Is Wrong on Vimeo
november 2011 by earth2marsh
"Pretty much every web service that uses HTTP verbs is calling itself RESTful these days, but what does that even mean? What makes a service RESTful? Why would you write a service using the REST style? Why are most services that call themselves RESTful actually just RPC in REST clothing? Steve will answer all these questions and more, as well as discussing where following strict REST does not make sense."
REST
video
Videos
twilio
conference
apis
api
design
from delicious
november 2011 by earth2marsh
13 Cool Examples of Google+ Brand Pages | DreamGrow Social Media
november 2011 by earth2marsh
Also recommend Burberry's page.
google+
brand
pages
examples
design
from delicious
november 2011 by earth2marsh
API Versioning - O'Reilly Broadcast
november 2011 by earth2marsh
Well written, but I still prefer /v1/ in my URIs.
api
apis
versioning
design
versions
patterns
from delicious
november 2011 by earth2marsh
Dudes, this is so not REST | Thought Palace
november 2011 by earth2marsh
"It’s simple to make requests to Rdio’s REST API. It’s built on widely used standards and conventions so there are libraries for most common web development platforms. All method calls are made as POST requests to http://api.rdio.com/1/. Arguments are sent as application/x-www-form-urlencoded, just like when a browser submits a form. The name of the method is passed as the ‘method’ argument. [Emphasis mine.]
What’s wrong with this? Well, the first bolded point is immediately contradicted by the ones that follow. Specifically, this cannot be a REST API, because it uses only one URL and one HTTP method. Two of the key features of HTTP-based REST are that
It’s object-oriented, where objects are identified by URLs. Each request’s URL identifies what object it operates on.
The methods to invoke on the objects are primarily indicated by the request’s method (GET, PUT, POST, DELETE). In fact this is why Tim Berners-Lee used the word “method” in the HTTP protocol in the first place."
api
rest
design
programming
reference
examples
example
restful
webdev
winningatinternets
from delicious
What’s wrong with this? Well, the first bolded point is immediately contradicted by the ones that follow. Specifically, this cannot be a REST API, because it uses only one URL and one HTTP method. Two of the key features of HTTP-based REST are that
It’s object-oriented, where objects are identified by URLs. Each request’s URL identifies what object it operates on.
The methods to invoke on the objects are primarily indicated by the request’s method (GET, PUT, POST, DELETE). In fact this is why Tim Berners-Lee used the word “method” in the HTTP protocol in the first place."
november 2011 by earth2marsh
LukeW | UI16: Experience Leadership
november 2011 by earth2marsh
"Kurt Lewin’s model of change: Unfreeze -shake people loose from existing norms. Transition, then refreeze. The new culture needs time to take root.
John Kotter’s model: develop a guiding coalition, and get short-term wins. Don’t decide to boil the ocean upfront. A coalition lets you have multiple change leaders not just one person.
Continuous change model: there are four types of change agents. It starts with influencers or evangelists. They sell ideas to the people who can make change. Then autocrats (people with power) can dictate and move things into practice. Then architects are required to establish the systems needed to put things into place. Finally educators tell the stories and help train people."
change
culture
design
from delicious
John Kotter’s model: develop a guiding coalition, and get short-term wins. Don’t decide to boil the ocean upfront. A coalition lets you have multiple change leaders not just one person.
Continuous change model: there are four types of change agents. It starts with influencers or evangelists. They sell ideas to the people who can make change. Then autocrats (people with power) can dictate and move things into practice. Then architects are required to establish the systems needed to put things into place. Finally educators tell the stories and help train people."
november 2011 by earth2marsh
Steve Jobs’s Real Genius : The New Yorker
november 2011 by earth2marsh
jobs: a genius and a bastard.
tweaker
innovation
apple
design
steve_jobs
malcolm_gladwell
from delicious
november 2011 by earth2marsh
Design blogs
september 2011 by earth2marsh
From dewitt clinton
Design
Blogs
Feeds
google:reader
from delicious
september 2011 by earth2marsh
Nikon | Feel Nikon | Universcale
september 2011 by earth2marsh
a descendant of the "Power of 10"
reference
design
education
power
from delicious
september 2011 by earth2marsh
What’s wrong with the Twitter API – Orian Marx
september 2011 by earth2marsh
"I want to make something clear from the start: I love Twitter, though sometimes I wonder if I’m suffering from Stockholm syndrome. I have devoted much of the last three years of my life to working with the Twitter API and continue to pursue building the world’s best Twitter client for professionals in the form of Siftee. Recently Twitter staff has been reaching out to developers with a renewed vigor in the hopes of recapturing some of the goodwill and enthusiasm that has been squandered in the past two years. I applaud them for that. The new developer discussion site and documentation portal are significant improvements. Jack Dorsey has reached out for feedback. I recently spent time on the phone with Jason Costa, Twitter’s developer relations manager, at his request. I think these are all good signs for the ecosystem.<br />
<br />
With that said, there is a lot of feedback to give. This post is a technical one focused on the API itself, not on Twitter’s relationship with developers"
design
api
twitter
platform
from delicious
<br />
With that said, there is a lot of feedback to give. This post is a technical one focused on the API itself, not on Twitter’s relationship with developers"
september 2011 by earth2marsh
Clarifying REST
september 2011 by earth2marsh
best explanation I've seen of hateoas
design
programming
apis
rest
Hateoas
from delicious
september 2011 by earth2marsh
RESTful Error Handling - O'Reilly ONLamp Blog
september 2011 by earth2marsh
"Nonetheless, here are my votes for most important criteria: Human Readable Error Messages; Application Specific Errors; Machine Readable Error Codes"
design
api
apis
reference
errors
from delicious
september 2011 by earth2marsh
API Design Principles | Qt Wiki | Qt Developer Network
september 2011 by earth2marsh
"Be minimal; Be complete; Have clear and simple semantics; Be intuitive; Be easy to memorize; Lead to readable code"
api
design
reference
apis
from delicious
september 2011 by earth2marsh
Thoughts on RESTful API Design
september 2011 by earth2marsh
"Thoughts on RESTful API Design<br />
<br />
Lessons learnt from designing the Red Hat Enterprise Virtualization API"
design
api
rest
reference
from delicious
<br />
Lessons learnt from designing the Red Hat Enterprise Virtualization API"
september 2011 by earth2marsh
So, you want to provide an API for the world to use? « Canonical Design
september 2011 by earth2marsh
"I conducted 5 qualitative interviews with developers and here are some findings.<br />
<br />
You have two problems. The first problem is to design the API. The second is to help people learn to use it.<br />
<br />
Great API design<br />
<br />
Is consistent, predictable, learnable. You are creating an API that developers will interact with. In the same way that a graphical user interface (GUI) might use visual design to provide users with a language to predict and learn behaviours, an API can use naming and format." … and lots more
design
apis
api
interviews
reference
research
from delicious
<br />
You have two problems. The first problem is to design the API. The second is to help people learn to use it.<br />
<br />
Great API design<br />
<br />
Is consistent, predictable, learnable. You are creating an API that developers will interact with. In the same way that a graphical user interface (GUI) might use visual design to provide users with a language to predict and learn behaviours, an API can use naming and format." … and lots more
september 2011 by earth2marsh
Harnessing the Power of Feedback Loops | Magazine
august 2011 by earth2marsh
"giving individuals a clear goal and a means to evaluate their progress toward that goal greatly increased the likelihood that they would achieve it"
design
feedback
loops
behavior
wired
sensors
from delicious
august 2011 by earth2marsh
Hipster Ipsum | Artisanal filler text for your site or project.
august 2011 by earth2marsh
"Odio accusamus messenger bag food truck marfa. Eu mollit viral, lo-fi aesthetic vice id you probably haven't heard of them officia high life laborum delectus 8-bit odio. Twee fanny pack qui nihil mollit, fixie vice do seitan voluptate williamsburg photo booth mixtape sed cliche. Brunch sed VHS, irony fixie messenger bag blog tattooed culpa butcher. Consequat brunch readymade tumblr sunt. Excepteur eiusmod brunch, Austin est skateboard helvetica tempor adipisicing pitchfork sapiente enim. Aesthetic elit deserunt ex locavore echo park odio."
design
tools
webdev
webdesign
ipsum
lorem
from delicious
august 2011 by earth2marsh
Disruption
august 2011 by earth2marsh
Right on. Empathy is the secret sauce.
Disruption
Design
innovation
from delicious
august 2011 by earth2marsh
related tags
!to_check ⊕ !to_describe ⊕ !to_listen ⊕ !to_read ⊕ !to_see ⊕ !to_watch ⊕ 2D ⊕ 3d ⊕ 37signals ⊕ abandoned ⊕ academic ⊕ access ⊕ accessibility ⊕ accessories ⊕ Adobe ⊕ ads ⊕ advertising ⊕ advice ⊕ aesthetics ⊕ affordances ⊕ africa ⊕ agency ⊕ agile ⊕ ajax ⊕ ala ⊕ alternating ⊕ alternative ⊕ amazon ⊕ america ⊕ analysis ⊕ analytics ⊕ android ⊕ animals ⊕ animated ⊕ animation ⊕ api ⊕ apidesign ⊕ apis ⊕ app ⊕ apple ⊕ application ⊕ Applications ⊕ apps ⊕ architecture ⊕ archive ⊕ arrays ⊕ arrogance ⊕ art ⊕ article ⊕ articles ⊕ artificialintelligence ⊕ artist ⊕ Asynchronous ⊕ attention ⊕ audio ⊕ awesome ⊕ aws ⊕ aza_raskin ⊕ b&w ⊕ background ⊕ badge ⊕ bamboo ⊕ baseball ⊕ beauty ⊕ behavior ⊕ best ⊕ bestpractices ⊕ best_practices ⊕ bicycle ⊕ bidding ⊕ biology ⊕ bloat ⊕ blockquote ⊕ blog ⊕ Blogs ⊕ board ⊕ book ⊕ bookmarklet ⊕ books ⊕ border ⊕ box ⊕ brand ⊕ branding ⊕ browsers ⊕ brushes ⊕ bubble ⊕ building ⊕ business ⊕ businesscards ⊕ button ⊕ buttons ⊕ cad ⊕ calendar ⊕ campaign ⊕ cappuccino ⊕ captology ⊕ car ⊕ card ⊕ cards ⊕ change ⊕ chart ⊕ charts ⊕ chemistry ⊕ choice ⊕ circuit ⊕ city ⊕ clever ⊕ Cli ⊕ client ⊕ clients ⊕ clipart ⊕ clock ⊕ clothing ⊕ cloudkick ⊕ cloudstock ⊕ cms ⊕ code ⊕ coding ⊕ cognition ⊕ collaborate ⊕ collaboration ⊕ collaborative ⊕ collection ⊕ collections ⊕ color ⊕ colors ⊕ colour ⊕ communication ⊕ community ⊕ commuting ⊕ compare ⊕ comparison ⊕ compatibility ⊕ competition ⊕ computers ⊕ concept ⊕ concert ⊕ conference ⊕ conservation ⊕ content ⊕ contest ⊕ context ⊕ control ⊕ conversion ⊕ conversions ⊕ convert ⊕ cool ⊕ copy ⊕ copying ⊕ copyright ⊕ copywriting ⊕ corners ⊕ corporate ⊕ cover ⊕ crafts ⊕ creative ⊕ creativecommons ⊕ creativity ⊕ creator ⊕ criticism ⊕ critique ⊕ crowdsource ⊕ crowdsourcing ⊕ cs ⊕ css ⊕ cultofdone ⊕ culture ⊕ cursor ⊕ custom ⊕ customer ⊕ cut ⊕ data ⊕ database ⊕ Dates ⊕ death ⊕ debt ⊕ decorating ⊕ decoration ⊕ deserialization ⊕ desig ⊕ design ⊖ designer ⊕ desks ⊕ desktop ⊕ Detail ⊕ details ⊕ developers ⊕ development ⊕ device ⊕ diagram ⊕ diagrams ⊕ digital ⊕ Disney ⊕ Disruption ⊕ distributed ⊕ diy ⊕ docs ⊕ documentation ⊕ dodecahedron ⊕ download ⊕ downloads ⊕ drawing ⊕ drupal ⊕ dynamic ⊕ Ebay ⊕ ebook ⊕ ebooks ⊕ EC2 ⊕ eco ⊕ economics ⊕ editing ⊕ editor ⊕ education ⊕ effects ⊕ efficiency ⊕ elasticity ⊕ elearning ⊕ election ⊕ elections ⊕ electricity ⊕ electronics ⊕ elevator ⊕ email ⊕ emergence ⊕ energy ⊕ engagement ⊕ engament ⊕ engine ⊕ engineering ⊕ entrepreneurship ⊕ envelopes ⊕ environment ⊕ errors ⊕ ethics ⊕ etiquette ⊕ eucalyptus ⊕ eulogy ⊕ events ⊕ evil ⊕ evolution ⊕ example ⊕ examples ⊕ Excel ⊕ exhibit ⊕ experience ⊕ export ⊕ eye ⊕ eyetracking ⊕ fabrication ⊕ facebook ⊕ faces ⊕ fail ⊕ failure ⊕ fashion ⊕ favicon ⊕ favorite ⊕ feature ⊕ features ⊕ feed ⊕ feedback ⊕ Feeds ⊕ filesystem ⊕ firefly ⊕ fitness ⊕ flags ⊕ flash ⊕ flickr ⊕ flight ⊕ floorplan ⊕ flow ⊕ flows ⊕ fluid ⊕ font ⊕ fontography ⊕ fonts ⊕ form ⊕ formats ⊕ formatting ⊕ forms ⊕ Foundry ⊕ foursquare ⊕ framework ⊕ free ⊕ freelance ⊕ freeware ⊕ fun ⊕ funny ⊕ furniture ⊕ future ⊕ gallery ⊕ game ⊕ gamedesign ⊕ games ⊕ gaming ⊕ gamma ⊕ garbage ⊕ gate ⊕ generative ⊕ generator ⊕ generators ⊕ gif ⊕ gifs ⊕ gimp ⊕ github ⊕ google ⊕ google+ ⊕ google:analytics ⊕ google:reader ⊕ googleearth ⊕ gpl ⊕ gps ⊕ graph ⊕ graphic ⊕ graphicdesign ⊕ graphics ⊕ graphs ⊕ green ⊕ grid ⊕ groups ⊕ gui ⊕ guide ⊕ hack ⊕ hacks ⊕ handmade ⊕ handwriting ⊕ happiness ⊕ happy ⊕ hardware ⊕ hash ⊕ hashbang ⊕ hashes ⊕ hateoas ⊕ hateos ⊕ health ⊕ highway ⊕ history ⊕ hobby ⊕ holography ⊕ home ⊕ house ⊕ housing ⊕ howto ⊕ html ⊕ html5 ⊕ http ⊕ humor ⊕ hypermedia ⊕ ia ⊕ icon ⊕ icons ⊕ ide ⊕ ideas ⊕ identity ⊕ ides ⊕ ie ⊕ ikea ⊕ illusion ⊕ illustration ⊕ illustrator ⊕ image ⊕ images ⊕ incentives ⊕ industrial ⊕ infographics ⊕ information ⊕ inheritance ⊕ inkscape ⊕ innovation ⊕ inspiration ⊕ installation ⊕ intel ⊕ interaction ⊕ interactiondesign ⊕ interactive ⊕ interesting ⊕ interface ⊕ internet ⊕ interview ⊕ interviews ⊕ intro ⊕ ios ⊕ ipad ⊕ iphone ⊕ ipod ⊕ ipsum ⊕ IxD ⊕ java ⊕ javascript ⊕ jeff_atwood ⊕ Jeff_Bezos ⊕ jesse_schell ⊕ jobs ⊕ jquery ⊕ json ⊕ kindle ⊕ landscape ⊕ language ⊕ laptops ⊕ laser ⊕ lasers ⊕ latency ⊕ layers ⊕ layout ⊕ learning ⊕ led ⊕ lego ⊕ lessons ⊕ lessonslearned ⊕ library ⊕ light ⊕ lighting ⊕ lights ⊕ linking ⊕ links ⊕ linux ⊕ list ⊕ lists ⊕ location ⊕ Login ⊕ logo ⊕ logos ⊕ london ⊕ loops ⊕ lorem ⊕ lsi ⊕ mac ⊕ magazine ⊕ mail ⊕ mailto ⊕ malcolm_gladwell ⊕ management ⊕ manifesto ⊕ manufacturing ⊕ map ⊕ mapping ⊕ maps ⊕ marketing ⊕ mattwebb ⊕ Matt_Jones ⊕ meaning ⊕ media ⊕ memory ⊕ menu ⊕ menus ⊕ methodology ⊕ methods ⊕ microsoft ⊕ mind ⊕ mindmap ⊕ mindmapping ⊕ mint ⊕ mistake ⊕ mobile ⊕ mocks ⊕ mockup ⊕ mockups ⊕ model ⊕ moderation ⊕ moma ⊕ monitoring ⊕ moodboards ⊕ motion ⊕ motivation ⊕ movies ⊕ mozilla ⊕ mp3 ⊕ murals ⊕ music ⊕ names ⊕ naming ⊕ Nature ⊕ navigation ⊕ networks ⊕ newsletter ⊕ newsletters ⊕ node.js ⊕ nori ⊕ notification ⊕ notifications ⊕ nyt ⊕ nytimes ⊕ obey ⊕ objectoriented ⊕ ocean ⊕ office ⊕ online ⊕ openoffice ⊕ opensource ⊕ optimization ⊕ organic ⊕ organization ⊕ origami ⊕ OS ⊕ ostrich ⊕ osx ⊕ outsourcing ⊕ owner ⊕ ownership ⊕ package ⊕ packaging ⊕ packing ⊕ pages ⊕ pain ⊕ paint ⊕ palette ⊕ panorama ⊕ paper ⊕ papercraft ⊕ parallax ⊕ parking ⊕ Passwords ⊕ pattern ⊕ patterns ⊕ pdf ⊕ pechakucha ⊕ people ⊕ perception ⊕ performance ⊕ Periodictable ⊕ personalization ⊕ personas ⊕ persuasion ⊕ persuasive ⊕ philosophy ⊕ phone ⊕ phones ⊕ photo ⊕ photographer ⊕ photography ⊕ photos ⊕ photoshop ⊕ Phpbb ⊕ physics ⊕ piano ⊕ picker ⊕ pictures ⊕ pillow ⊕ pixels ⊕ place ⊕ places ⊕ plagiarism ⊕ planes ⊕ planning ⊕ platform ⊕ plugins ⊕ png ⊕ podcast ⊕ policy ⊕ polish ⊕ politics ⊕ pollock ⊕ portfolio ⊕ portrait ⊕ poster ⊕ posters ⊕ postmortem ⊕ power ⊕ powerpoint ⊕ prd ⊕ presentation ⊕ presentations ⊕ president ⊕ pricing ⊕ principles ⊕ print ⊕ printing ⊕ Privacy ⊕ problems ⊕ procedural ⊕ process ⊕ procrastination ⊕ product ⊕ productivity ⊕ productowner ⊕ product_management ⊕ programming ⊕ project ⊕ projectmanagement ⊕ propaganda ⊕ prototype ⊕ prototyping ⊕ psychology ⊕ public ⊕ pulpfiction ⊕ puzzle ⊕ python ⊕ qr ⊕ qrcode ⊕ quality ⊕ quote ⊕ radiohead ⊕ rails ⊕ rant ⊕ raspberry ⊕ rate ⊕ rating ⊕ readability ⊕ realestate ⊕ realism ⊕ recycle ⊕ reference ⊕ registration ⊕ renovate ⊕ renovation ⊕ representation ⊕ reputation ⊕ requirements ⊕ research ⊕ resource ⊕ resources ⊕ responsive ⊕ rest ⊕ restful ⊕ review ⊕ reviews ⊕ road ⊕ robots ⊕ rotary ⊕ rotate ⊕ rounded ⊕ roundedcorners ⊕ rows ⊕ royksopp ⊕ rpc ⊕ rss ⊕ ruby ⊕ RUSSIA ⊕ sales ⊕ sample ⊕ sanfrancisco ⊕ satisfaction ⊕ saving ⊕ scale ⊕ schemes ⊕ science ⊕ screencast ⊕ scrum ⊕ sculpture ⊕ seal ⊕ seattle ⊕ second ⊕ Security ⊕ segway ⊕ self ⊕ sensors ⊕ seo ⊕ sequencer ⊕ server ⊕ service ⊕ services ⊕ set ⊕ shadow ⊕ sharecropping ⊕ sharing ⊕ shell ⊕ shipping ⊕ shoes ⊕ shopping ⊕ shortcut:timezone ⊕ shortcut:tz ⊕ showcase ⊕ Signin ⊕ signs ⊕ signup ⊕ simplicity ⊕ simulation ⊕ site ⊕ sketch ⊕ sketchup ⊕ Skills ⊕ skins ⊕ sleep ⊕ slider ⊕ slides ⊕ slideshow ⊕ slow ⊕ smile ⊕ smiley ⊕ snippets ⊕ social ⊕ socialengineering ⊕ socialmedia ⊕ socialnetworking ⊕ socialsoftware ⊕ society ⊕ sociology ⊕ software ⊕ solving ⊕ sony ⊕ sound ⊕ source ⊕ space ⊕ spam ⊕ speech ⊕ spine ⊕ sports ⊕ spreadsheet ⊕ sprites ⊕ stackexchange ⊕ stairs ⊕ standards ⊕ stanford ⊕ startup ⊕ startups ⊕ statistics ⊕ Stencil ⊕ steve_jobs ⊕ stock ⊕ storage ⊕ stories ⊕ story ⊕ storyteller ⊕ storytelling ⊕ study ⊕ style ⊕ stylesheet ⊕ subbu ⊕ subpixel ⊕ subway ⊕ support ⊕ sushi ⊕ sustainability ⊕ sustainable ⊕ svg ⊕ sync ⊕ synchronization ⊕ synthesis ⊕ system:filetype:pdf ⊕ system:media:document ⊕ systems ⊕ t-shirts ⊕ table ⊕ tabs ⊕ tagging ⊕ taste ⊕ taxi ⊕ Teaching ⊕ technique ⊕ technology ⊕ ted ⊕ TEDx ⊕ template ⊕ templates ⊕ test ⊕ testing ⊕ text ⊕ texture ⊕ textures ⊕ theme ⊕ themes ⊕ theory ⊕ thingfrastructure ⊕ thinking ⊕ threes ⊕ tiles ⊕ time ⊕ timeline ⊕ tim_bray ⊕ tips ⊕ todo ⊕ tool ⊕ tools ⊕ tour ⊕ Toyota ⊕ toys ⊕ tracking ⊕ training ⊕ transport ⊕ travel ⊕ trends ⊕ tricks ⊕ tryme ⊕ tshirts ⊕ tumblr ⊕ turbine ⊕ turnstyle ⊕ tutorial ⊕ tutorials ⊕ tv ⊕ tweaker ⊕ twilio ⊕ twitter ⊕ type ⊕ typeface ⊕ typography ⊕ ubiquity ⊕ ui ⊕ uml ⊕ urban ⊕ uri ⊕ url ⊕ urls ⊕ usability ⊕ useful ⊕ user ⊕ userbar ⊕ userexperience ⊕ users ⊕ user_experience ⊕ user_research ⊕ utilities ⊕ utility ⊕ ux ⊕ uxd ⊕ vector ⊕ venn ⊕ venndiagram ⊕ versioning ⊕ versions ⊕ via:ajpik ⊕ via:awhite ⊕ via:jen ⊕ via:jess ⊕ via:preoccupations ⊕ via:zite ⊕ video ⊕ videogame ⊕ videogames ⊕ Videos ⊕ virtualization ⊕ vision ⊕ vista ⊕ visual ⊕ visualisation ⊕ visualization ⊕ vocabulary ⊕ voting ⊕ w3c ⊕ Wallpaper ⊕ walmart ⊕ web ⊕ web-services ⊕ web2.0 ⊕ webdesign ⊕ webdev ⊕ webinar ⊕ webservice ⊕ Werner_Vogels ⊕ wind ⊕ windows ⊕ winningatinternets ⊕ wired ⊕ wireframe ⊕ wireframes ⊕ wireframing ⊕ wishlist ⊕ wood ⊕ wordpress ⊕ work ⊕ workflow ⊕ world ⊕ writing ⊕ wysiwyg ⊕ xml ⊕ XP ⊕ yahoo ⊕ yam ⊕ youtube ⊕Copy this bookmark: