The actual lyft line code is more simple than you would expect. It's written in Flask and uses lots of heuristics. Lack of real-time traffic data causes most of their issues. We're hosting the engineering lead for Lyft Line at our meetup in SF next month if you are interested in learning about it: <a href="http://www.meetup.com/OpenLate/events/217476372/" rel="nofollow">http://www.meetup.com/OpenLate/events/217476372/</a>
For those not in the SF area, this is almost certainly in response to this (unless Uber has a mole within Lyft...):
<a href="http://blog.uber.com/SFpoolparty" rel="nofollow">http://blog.uber.com/SFpoolparty</a>
I just tried Lyft line in SF. The first request got canceled after five minutes. The second one found matches after a few minutes and told me to be outside 6 minutes later. At some point someone else joined the ride, so the 6 minutes turned into 12. About 15 minutes went by, and (when the estimated wait time had decreased only by 4 minutes) the driver decided to cancel the ride. My guess is that it was because rush hour pricing jumped from 50% to 75%, so "James" decided getting a single, full-price ride made more sense.<p>Needless to say, not a happy customer at this point.
For its shortcomings, at least Muni has a level of accountability to the public that Lyft and Uber inherently lack. I can't see Lyft or Uber providing discounts to seniors or people with disabilities.
The company I work for recently won a contest put on by Lyft offering free Lyft Line rides to and from work for an entire week. I live in Lower Pac Heights and work in the Financial District and take a couple different Muni routes to and from work. I'll take either the 2 or the 3 heading in and the 38L heading back; the 38L is way too crowded in the morning by the time it gets to my closest stop. Morning commute usually takes around 15 minutes and afternoon takes around 10.<p>So, my commute isn't bad by any means but I decided to give Lyft Line a shot to see if I could do any better. The first day I tried hailing one in the morning, the app hung up looking for drivers; it said 1 minute to match with a driver but I waited 3 before quitting the app and deciding to take Muni. That afternoon, I tried again but ran into the same issue. The next afternoon, I was finally able to line up a ride but had to wait 10 minutes for the driver to get to me. Once he did and we were on our way, I had the joyful experience of sitting in traffic for blocks on end while watching Munis zip by in the designated lanes beside us. Not including wait time, the ride took around 20 minutes (double my normal commute time).<p>I'm sure there are some routes for which Line is a better option than public transportation, but I personally have a much better experience on Muni than I did with Line. I get why they're focused on rush hour; a service like Line requires a critical mass of people to use the app concurrently in order to make it work. But, the downside of this is that the times when it reaches this point are the times when traffic is the worst and public transportation offers a superior alternative in many cases. We'll see if this ends up taking off, but I know I won't be using it for my commute. Maybe this would be better suited for one-off events like Outside Lands, Giants games etc. but I'd imagine they'd run into the same problems.
I’ve been a regular Lyft Line user. Except for some cars that show up in pretty bad shape and smell, it’s a good experience. And I’ve had to wait much longer on an average.<p>It’s heartening to see a company just focused on the “user” and not just world domination.
This would seem to undermine companies like Chariot, who are offering more MUNI-plus like services:<p><a href="http://chariotsf.com" rel="nofollow">http://chariotsf.com</a>
<a href="http://www.reactiongifs.com/wp-content/uploads/2012/09/throwing-money-away.gif" rel="nofollow">http://www.reactiongifs.com/wp-content/uploads/2012/09/throw...</a><p>Edit: thanks for downvoting a valid point. It's weird that HN doesn't see it for what it is.