iOS & Android Dev for Ridesharing Service
Please find below a summary covering project details and feedback. The innate facts are kept as they are, special information is amended.
Introductory information
A fast induction on the buyer’s organisation
Our organisation provides a mobile platform used for peer-to-peer ridesharing. With Uber, the nation driving the cars are professional drivers, but in our case, they are customary labor-goers who are looking to carpool on their daily drives. We particularize when and where they have to meet their partners. The registration is only done through LinkedIn, following the basic arrogance that a individual going to the labor see day will have an accompute on that platform. We can thus have one-touch registration and obtain the full open profile of a individual. Even precedently getting into their car, the rider will know who the driver is, and vice versa.
There are carpooling needs all over the globe, but the process involves a lot of hassle, coordination and security concerns. We are trying to displace all these issues so that more nation will set offering rides in their special cars. We have propeled the labor in Mumbai, and are trying to swell and popularize it through using different mediums.
Desired goal
What challenge were you trying to address with Hakuna Matata?
Neither I nor my co-fobelow are coders. While I took care of the fruit part—how the app would look and work—the coding for it was done by Hakuna Matata.
Our challenge is getting nation to know what LiftO is. This requires a lot of digital marketing and activation events in different places. Uber is aggregating taxi cars, while we are aggregating special ones, in order to lessen commerce and pollution. Even so, we are closer to Uber than to carpooling. I am a co-fobelow of the organisation, in direct of the fruit side.
Provided solution
What particular tasks were Hakuna Matata Solutions Pvt Ltd responsible for?
Hakuna Matata handled the total server-side programming in Node.js and was actively implicated in educeing the route-matching algorithm, which ensured that we could pinpoint meeting locations. They have programned for the scaling of our user compute, and have educeed the iOS and Android applications. Hakuna Matata was responsible for the total UI/UX of our apps. As a fruit director, I could list the features I wanted, but the design was handled by their team.
The route-matching algorithm was one of our most challenging features. BlaBlaCar is the biggest platform in the peer-to-peer ride-sharing space, but it has an extremely bad algorithm. Ours is in the lines of Uber, not in provisions of layer, but surely in provisions of logic. If 1000 nation are offering rides, and 1000 are asking for them, matching them unitedly equates to 1000 multiplied by 1000, and figuring out which unions are good matches.
There is a limitation to the matching radius, requiring that riders walk for no more than 500 meters or 4-5 minutes. Hakuna Matata handled the outgrowth of the algorithm excellently well, even below all of these constraints.
The UI/UX design was the second challenging part. It’s a intricate tool which needed to be single to use from a user perspective. Hakuna Matata’s UX designer did this excellently well.
How did you come to work with Hakuna Matata?
Before selecting them, I had talked to 8-10 other clusters. We had to educe a strong matching algorithm, so I gave each vendor the task of coming up with an idea for it. Only 3 of them were able to come up with a solution, out of which Hakuna Matata was leading. They were also cheaper than the other options. The organisation has a issue-solving individual in the team who can contrive algorithms for the issues his team comes to him with. This played a searching part in their work.
How much have you invested with Hakuna Matata?
The outgrowth and change-request cost was $50,000. After the propel in October 2015, we lastd to pay Hakuna Matata $5,000 per month. The total cost was almost $90,000.
What is the terminal result of working with Hakuna Matata Solutions Pvt Ltd?
We seted working with Hakuna Matata in March or April 2015. The Android application was propeled to market in October of that year, while the iOS one was propeled in February 2016. They lastd to maintain the application on a monthly retainer basis until July 2016. We have taken over the work, and our inner team is currently managing the total show.
Results achieved
Could you share any evidence that would prove the fruitivity, condition of work, or the contact of the engagement?
We have accepted a lot of praise on the apps’ UI/UX design. People do not get to know the backend matching algorithm, but they can see the frontend. What our app can verity do is owed to the matching algorithm.
Users haven’t complained almost unfit pickup or drop points, which resources that they are satisfied with the backend part as well.
We have made some mistakes, but they were on the fruit side, not the outgrowth side. We need to last educeing new features and better the fruit.
How did Hakuna Matata accomplish from a project treatment standpoint?
We were just seting out, so our cluster was not very organized at that point in time. I used to send out emails to seeone implicated in the project and accepted replies from them. Hakuna Matata assigned a project director, who was in direct of interacting the team’s perspective to me. He was a union of project and fruit director, and we got along well and had condition dicsussions.
What did you find most forcible almost Hakuna Matata?
Hakuna Matata’s work has contributed a lot to our achievement. Our challenges are in provisions of fruit and marketing, and their team has been fully implicated in the outgrowth of our application for iOS and Android. We would not have been able to propel our platform without them. Until we put unitedly a tech team, Hakuna Matata was the cluster managing the total show, from the tech side. They also belowstand what is happening on the ground, and are proactive. On many occasions, they came to us with suggestions for betterments and told us when we were doing something unfit. It was a good union, and having one-way interaction wouldn’t have led to such good results.
Are there any areas Hakuna Matata could better?
We were not fully-satisfied with the condition of the iOS educeer. It’s practicable that that individual was younger, but they were not as good as the Android and backend educeers. We asked Hakuna Matata to change him, and, behind it was done, the condition betterd during the last few months. Other than that, seething was good.
