The internet allows products and services to be rapidly improved based on user feedback. So rapid, that iterative design should become the primary method of designing internet-based services. Not just as an Agile-like method of working, but as a method of specifying the product itself.
Partly it isn’t because creators haven’t adjusted their methods to match the new technology – we’re still wedded to a single start-to-finish process, with one outcome at the end. Partly it isn’t because feedback can be hard to gather and digest, and even hard to act upon.
An iterative method has become one of the defining characteristics of how I like to write, organise, and present text on the internet. At least, beyond this domain. But until now, I’ve struggled to apply it to internet-based video.
This article introduces internet-based iterative design, and uses YouTube’s “Hot Spot” analysis to show how we can start to apply an iterative approach to video and movie-making. Read more of this article »
The UK‘s local public transport data is effectively a closed dataset. The situation in the US seems similar: In spite of the benefits only a handful of agencies have released raw data freely (such as BART and TriMet on the west coast of America).
That hasn’t stopped “screen-scraping” of data or simply typing in paper timetables (from Urban Mapping to many listed here). Unfortunately, the legal basis for scraping is complex, which creates significant risks for anyone building a business. For example, earlier this year, airline Ryanair requested the removal of all their data from Skyscanner, a flight price comparison site that gathers data by scraping airlines’ websites. How many airlines would need to object to their data being scraped before a “price comparison” service becomes unusable?
Micro-blogging, primarily through Twitter, has started to show the potential of individual travellers to report information about their journeys: Ron Whitman‘s Commuter Feed is a good example. Tom Morris has also experimented with London Twitter feeds.
This article outlines why the “social web”/tech-entrepreneur sector may wish to stop trying to use official sources of data, and instead apply the technology it understands best: People. Read more of this article »
The United Kingdom’s local public transport network is likely to become part of Google Transit. Technically that should be far easier in the UK than in North America, where Google Transit was first developed: The UK has a decade’s bitter experience putting all the data together. In practice it is raising wider issues over data control and availability, that the public sector is somewhat reluctant to tackle.
This article describes how the UK’s public transport data is being integrated into Google. It questions why data is being made available based solely on the business model adopted. It explores the real value of this information, and presents a case for the liberalisation of data.
Readers unfamiliar with the topic area should read my earlier Introduction to UK Local Public Transport Data, which contains non-technical background information, and defines many of the terms used (such as “local”). The original research for this was done in June/July 2007, so may now be slightly out of date.
The illustration on the right is the Google part of a visual representation of web trends, based on the Tokyo metro map, by Information Architects Japan.