Since its inception, Seattle transit app OneBusAway has been the kind of service you’d have to pry off someone’s home screen. Given King County Metro’s chronic funding shortfalls that keep route schedules from being updated (or even available) at all stops, and the system’s tendency to bog down in rush-hour traffic congestion, OneBusAway’s real-time bus tracking is an essential part of a commuter’s toolkit.
New transit-site-on-the-block WhichBus, which emerged from beta at the beginning of 2013, promises to be “simple” and beautiful” but it doesn’t yet have the years of user-testing that’s now built into OneBusAway. So Metro riders greet any news about their favorite app’s future with distinct wariness. But news, nonetheless, is what University of Washington professor Alan Borning has, as a shared-funding contract ends:
The contract is expiring in mid-May, and sometime around then Sound Transit will be taking over running it. (Sound Transit already has an experimental version of OneBusAway running in parallel with the production system.)
Borning explains that as a year-and-a-half of King County Metro, Sound Transit, and Pierce Transit support for the app (which remains free for download) ends, Sound Transit is officially taking over running the Seattle-based instance, while the UW group continues research and development on how apps such as OneBusAway can provide:
…better and additional types of transit information (such as alerts, real-time replanning, vehicle capacity information, and others), integrating incentives for transit use with OneBusAway, crowd sourcing the detection and resolution of data problems with real-time transit data, and providing tools that seek to benefit all riders, including blind and low-vision, mobility impaired, and others.
By mid-2011, when Brian Ferris, one of OneBusAway’s creators, was leaving for grüner Google pastures, 50,000 people were using OneBusAway each week. Two years later, that number has more than doubled, to more than 100,000 people. That kind of usage has hardened the app in ways that the WhichBus team can’t match, as of yet. During their beta, they relied upon a pool of 1,200 people who were willing to put up with odd results.
The idea behind WhichBus — which you can see on the minimalist home screen — is that transit is about getting from A to B, not memorizing routes, service intervals, or connections. All the site asks is where you are (type in a location, or let it find you automatically) and where you want to go. You can be precise (street address) or not (“Green Lake”), and it churns out route options for you, with real-time info baked in.
Simplicity has its drawbacks, in a city like Seattle, which maintains an “it’s complicated” relationship with transit. Back in January, I asked WhichBus how to get from Capitol Hill to the University Village Apple Store, which was not just a joke at the expense of hipsters but a difficult problem because the Village is not well-served by transit. Then, WhichBus directed me downtown and out to Northgate. It still does, for a one-hour-and-51-minute trip. Google Maps suggests the three-mile drive should take 10 minutes.
The problem could likely be solved if you could let WhichBus know you were willing to walk up to a mile, but this kind of thing complicates a determinedly simple interface. (In this case, most people could walk the three miles in under an hour, shaving at least an hour off WhichBus’s suggested trip and saving bus fare, to boot.)
That is not a simple interface. There are, I think, 7 colors PLUS gradients. And their main color is the color of ice cream.
If anything bad happens to OneBusAway, I’m getting into running.