Archive for the ‘Development’ Category

I have seen a slew of sites that attempt to achieve a one-screen effect where there is a dashboard view of all the content. Rather than having users scroll, these sites encourage users to click to explore new content.  This is bad, very bad especially for a site rich with information.  My advice: if you have a lot of content, let people scroll.

1. Scrolling is fast
The best equivalent of scanning a newspaper on a computer is being able to scrub or scroll up/down a page. 

2. Scrolling does not punish, it is a forgiving behavior
When you click something, it takes you to a new destination. For some that experience can be scary and for others the time to load a new page is just not worth it.  Don’t punish the user and make him use the back button.

3. Trying to change the habits of someone will make them run away
No one wants to learn something new. When a site doesn’t need a scroll bar or have a recognizable interface to navigate, a user begins to slow down and think about their experience. 

4. We scroll all the time, so leave it that way
Every kind of site requires you to scroll: news on MSNBC, stocks on Yahoo Finance, Gmail, Twitter, Facebook, and Yelp. Your applications even require you to scroll: Excel, Word, TextMate, Quicken. People are very used to scanning a large space for the information they need. If it is organized visually their experience can be pleasant.

Find a way to make scrolling work for your experience. Do everything you can to ensure that elements on your page are easily recognizable. Using good typography and vibrant images can help attract the eye where it needs to go. Using common elements across pages will help too!

This tip is for anyone creating a site with extensive content.  If you are creating a site for a ad campaign, portfolio, or some creative experiment, this does not apply!

[singlepic=8]

The New York Times took a leap forward today and released an API powered by the United States Federal Election Filings.  They have done the hard work and aggregated all the necessary information to retrieve data on candidates by zip code and information on individual donors.  From the Open Code blog:

The initial version of the Campaign Finance API offers overall figures for presidential candidates, as well as state-by-state and ZIP code totals for specific candidates. In addition, the API supports a contributor name search using any of the following parameters: first name, last name and ZIP code.

This is an important release by the New York Times because it reiterates their commitment to the developer community.  In their own words, “You already know that NYTimes.com is an unparalleled source of news and information. But now it’s a premier source of data, too — why just read the news when you can hack it?“ 

This appeal to developers should result in a mini-ecosystem of rich apps powered by New York Times APIs. The value of releasing data to developers will be:

  • Allowing creative developers around the globe to hack at their data
  • Extending the NYTimes brand throughout the web community
  • Identifying talented developers who could be potential employment candidates
  • Gaining insight on how people use the APIs and tools released

I might just dabble with the API this weekend…