 |
|
    |
 |
|
 |
The NextBus approach combines Global Positioning System (GPS) data with patented predictive software to give passengers accurate arrival times. NextBus uses satellite technology and advanced computer modeling to track vehicles (fitted with a satellite tracking system). NextBus estimates vehicle arrivals with a high degree of accuracy. This estimate is updated constantly and posted to the web, wireless devices including signs at bus stops and businesses, Internet-enabled cell phones and PDAs. We had an opportunity to talk with Bryce Nesbitt, responsible for new business at NextBus, to learn more about their development process.
How did you come up with the idea for NextBus? Anyone who has ever ridden a bus has asked the question "when will the next bus arrive?" We simply set out to answer that question. We now have good answers in two-dozen cities and will soon finish what we have started in San Francisco. How did Openwave help you accomplish your goal? We started with HDML working with a predecessor of Openwave. Openwave has helped us navigate the shark-infested waters of cellular technology, which sees a constant stream of new (and slightly different) telephone models each day. Specifically, what technologies are you using? We outfit each bus with a GPS receiver and a cellular radio. Our base computer models current traffic conditions, and creates estimated arrival times. We deliver data directly to passengers via our website, fixed location signs, SMS and of course WAP and even HDML. Try it from your mobile phone! What role do partners play in the deployment? We know a lot about each of our users. We know where they are, where they are going, and how much time they have on their hands. Our challenge is to find additional services passengers will accept, that also help offset the costs of providing the system. We are seeking partners to help leverage this potential. Do you plan to add new location features (used in mobile devices) in an upcoming version of your application? Even without Location Based Services (LBS), we already know where our users are, so direct LBS is not of great benefit. But we are looking forward to the day when small and local businesses routinely purchase highly geo-targeted advertisements. We have information people want to look at -- where the bus is -- that makes us an excellent place to advertise. We also see interesting potential in the "push a button to ride" application space. Running empty buses around is inefficient; we can help optimize both the rider and transit agency experience. Do you have any advice for anyone developing applications? What else did you learn from this process? If there is a problem with your application, don't expect that you'll hear about it from your users. If the application does not work the first time, many people will simply never try it again. If you're not testing on at least a dozen different telephone models, you're not testing enough (even simple things like the "back" button, can trip you up). Openwave has two tools we use: an accurate and robust simulator for testing your application and details about hundreds of device models shipping with their browser that helps navigate the challenges of delivering information to a multitude of devices. That, and the work they are doing with the OpenSource Community on projects such as WURFL can help developers get the information they need to build usable apps. Want your application to be featured in an upcoming issue of the Developer Newsletter? Contact the Openwave Developer Network to find out how! |