News for hackers. Stuff that matters.
Re:Launch HN: Mystro (YC S17) – Automation for On-Demand Dri... by tammer on Tuesday August 22, 2017 @02:03PM (#15074906)
This isn't a great question, as the child comments illustrate; effectively its a proven tenet of startup culture that execution and growth are key steps to profitability rather than the uniqueness of an idea or service.

I have a similar but I think more valid question, however, which is how do you plan on staying compatible with the ride-sharing companies themselves, who I assume will eventually attempt to lock you out of their services as they come to see you helping their competitors?

Re:Launch HN: Mystro (YC S17) – Automation for On-Demand Dri... by mrajcok on Tuesday August 22, 2017 @02:11PM (#15074989)
We actually are solving a massive driver retention problem for them (96% churn) so we see ourselves as beneficial to the rideshare companies since we increase driver earnings and retention at no cost to them.

We have a framework built out that lets us rapidly respond to app updates and a team of testers all over the US.

We have also thought about how to best circumvent any active attempts to block us -- since we interface with the driver apps directly rather than any APIs that would be harder to do.

Re:Launch HN: Mystro (YC S17) – Automation for On-Demand Dri... by sharkmerry on Tuesday August 22, 2017 @06:29PM (#15076921)
>>We actually are solving a massive driver retention problem for them (96% churn)

Forgive me, but how? Is downtime really the issue that makes drivers leave?

Re:Launch HN: Mystro (YC S17) – Automation for On-Demand Dri... by jsloss on Tuesday August 22, 2017 @02:09PM (#15074970)
They mention this issue on their site. It seems as if they're helping to reduce driver churn (which can be as high as 90% after 1 year) and thus Lyft / Uber let them rock and roll.