Hacker News new | past | comments | ask | show | jobs | submit login

Sound like the company has not invented here syndrome. Maps is largely solved problem. Mapbox has a great product that is customizable.

Perhaps the company could better spend their R&D to focus on products that directly imoroves it's market share and revenue.




They likely do use mapbox for rendering maps, as their SDK is really customizable, is designed to work with the OSM data format, and you don't need to pay mapbox to use it (at least for older versions). But mapbox is not necessarily a good solution for all of the routing requirements Lyft has. For example, at SFO ride hailing drivers are required to wait in a special parking lot outside of the airport, and then dispatching for rides is done based on which driver has been waiting in that lot the longest. You could probably make this work with mapbox, but it isn't necessarily a matter of just plugging it in and calling it done.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: