Felipe Albertao to james.morris

The initial concept of our service was not exactly ride sharing, but basically a generic mobile bulletin board (like Craigslist, but SMS based). We initially decided to focus on ride sharing because it sounded like a good way to get traction (due to the mobility aspect of ride sharing), and we planned to expand to other categories later on.

We implementing the matching software by keywords and distances. So, for example, when the driver sends us a SMS "drive san francisco to mountain view 10am" our software would first find the location words ("san francisco" and "mountain view"), then translate them into globe coordinates (Yahoo offers such API), and finally it would process the additional words "drive" and "10am". Like so, if someone else sends "ride san francisco to sunnyvale 10am", we would match them up by proximity.

In a nutshell, here is what went wrong with our service:

1) Hard to get traction due to the classic chicken-and-egg problem: Ride sharers do not sign-up due to the lack of riders, and riders do not sign-up due to the lack of sharers.

2) People do not trust anonymous riders. We hoped to solve this issue by introducing a social network where we would prioritize the matches by degrees of separation. But that didn't work due to #1

3) The large majority of the population enjoy their privacy in their own car and do not have a motivation to share the ride (perhaps now it's a different story, since gas prices are high)

4) For those who are motivated enough to share a ride, there are already plenty of options available out there: Craigslist, employer's bulletin board, in additional to local authorities (ex: 511.org and casual car pooling in Bay Area)

5) The obvious issue of dealing with SMS, which is not user friendly. I did not list this reason as #1 because through the interviews we found that people are willing to deal with a low-tech UI if the service really worked. So we figured that poor UI (SMS) was not such a huge issue, but it definitely turned off potential users.

I think the biggest issue is really the #1 above (traction). It seems to me that focusing on a single route (say, 85 as you mentioned) is an excellent idea, and we have not tried it. Although there are plenty of rideshare systems available today, there is a real gap in casual carpooling (most of the current solutions are around fixed-time carpooling). We also have not tried the taxi dispatching idea, which could be an attractive solution, but I think it would require a huge amount of active users (i. e.: You need at least 2 people heading to the same direction at around the same time).

Also, with the gas prices going higher, you might have a better shot than we had. Our intention was to build a voucher system where the rider would prepay for the ride and then we would pay the driver according to the mileage. This idea could be a real incentive for people trying to minimize their gas expenses, especially now.

From a technology standpoint, here are the practical issues we found:

Here are a few things we tried to do to build traffic and solve the traction problem:

I hope this helps! Please let me know if I can help you any further, and I would be happy to share more of this experience over a meeting or coffee. I'm really passionate about the use of technology for environmental and social issues, and I hope your efforts in this area are successful!