Google Ridesharing

What do you like best?

We started using Google Ridesharing to solve the problem of our technicians scheduling and routing issue. It effectively resolve our business problem and meets business requirements (will provide details in later section). What did I like? here are few:

1. Google Ridesharing provides robust and powerful API capability.

2., flexibility to develop your own custom routing/scheduling application using it's core functionality and capability.

3. nearly 99% accuracy turn-by-turn fastest/shortest route to destinations and 99% accuracy on prediction

4. Easy and seamless integration with Google map

5. now seamless integration with google assistant

What do you dislike?

1. Initial setup and integration with our own mobile application was difficult. We had several technical discussion with Google team to integrate Google Ridesharing functionality in our applications.

2. Reporting is also little strange. Instead of running last 30 days, it shows month by month. For that we needed to bring the data back to our environment and have our custom reporting on that data. Thanks to available APIs.

Recommendations to others considering the product:

It depends on your personal usage need and/or business need. As I mentioned earlier, as a technical person I found this product effective to solve our business problem. Also mentioned, it will be little difficult to develop your own custom application based on core functionalities and capabilities of Google Ridesharing will be little challenge but worth to give a try.

What problems are you solving with the product? What benefits have you realized?

We had business problem to help our technicians to arrive consumers address on time using effective up to date route with turn by turn driving guidance. We also have problem of allowing our consumer to change/cancel any appointment up to 45 mins before the schedule time needed fast replanning/rescheduling and re-routing the technician's schedule and route. Google ridesharing effectively helped to solve the problem.

NB: We didn't use Google Ridesharing native app. We just used it's capabilities and APIs