Mobile Development for Mileage Capture App
- Mobile App Development
- Confidential
- Dec. 2016 - May 2017
- Quality
- 4.5
- Schedule
- 4.5
- Cost
- 4.0
- Willing to Refer
- 5.0
"I have a lot of respect for what they do and the work they deliver, and they built a great product for us."
- Other industries
- Milwaukee, Wisconsin
- 201-500 Employees
- Phone Interview
- Verified
Red Foundry built and designed the SDK for existing mileage tracking and billing mobile apps on iOS and Android. They integrated it with a complex backend and preserved the high-level functionality.
The end product was complex and required a highly collaborative work environment to complete, but Red Foundry did so with composure. Their work was consistently of the highest quality and their candid approach to project management and development made for an overall enjoyable experience.
A Clutch analyst personally interviewed this client over the phone. Below is an edited transcript.
BACKGROUND
Introduce your business and what you do there.
I am the Vice President of Product at Runzheimer, overseeing all our mobile platform experience, including apps as well as all of our partner integration initiatives. We are an enterprise mobility company focused on fair and accurate mileage reimbursement for business use of personal vehicles.
OPPORTUNITY / CHALLENGE
What challenge were you trying to address with Red Foundry?
We wanted to create a platform from which we could distribute mileage capture to anyone who needed it as part of their business routine, be it consumer oriented or business-to-business. The aim of our overall system is to provide IRS compliant mileage logging and reimbursement all within mobile apps. Although we have had mobile apps themselves for about ten years, we needed the expertise of Red Foundry to build a software development kit (SDK) from our existing versions because our in-house team did not have that skillset.
SOLUTION
What was the scope of their involvement?
The apps themselves are built on Xamarin, which is a C# base code, and we brought in Red Foundry to build the SDK in C# so that it would be distributable to any mobile platform. Once we had the SDK, the plan was to sell that product to third parties who wanted to embed our mileage capture functionality within their own native app experiences. The customer would then able to capture and classify the miles they drive, including using the mobile device’s GPS to allow accurate data collection and reimbursement within the app.
Red Foundry provided us with both iOS and Android developers, and they built and designed the SDK from the ground up while modeling it after our existing platform. Our services group also had to be intimately involved because they had to build the backend with which the final system would operate. There were a variety of things that we needed to be able to track through the final SDK, including authentication, reporting, and diagnostics. Having all of those features would allow us to report and bill accurately based on the usage of the platform.
What is the team composition?
At the peak of the project’s development phase, we had about five people from Red Foundry working with our team. However, the collaboration began with three main team members. Rob Brandt (Partner, Red Foundry) filled the equivalent of my role on their side, helping us from a product and overall business standpoint. Then Ron Franczyk (Partner & CTO, Red Foundry) took charge of our iOS architecture, and we had a third person working on Android. Once the project ramped up to speed, they added one more developer for each platform.
How did you come to work with Red Foundry?
I had worked with Rob at a previous company and we had kept in touch over the years. When he took over as the CEO of Red Foundry, the opportunity presented itself to have them be in contention for this role. We took them through a hiring process, including interviewing multiple other companies, but it was clear when I talked to Rob and after we reviewed their credentials that they were the right fit for our needs.
What is the status of this engagement?
We worked with them from December of 2016 through May of 2017. Although the SDK has not been released due to extenuating circumstances unrelated to Red Foundry, the engagement has concluded.
RESULTS & FEEDBACK
What evidence can you share that demonstrates the impact of the engagement?
Unfortunately, due to other in-company factors, we have not yet installed the SDK in a production environment. We have been able to get the SDK approved in the app stores, although it is not currently being made available to third party developers. The long-term plan is still to roll it out, but there is no specific timeline on that yet. As such, we do not have any user or marketplace feedback or metrics about the impact of their work, other than that we have been very satisfied internally with what they have delivered. Building a mileage capture experience is tricky, particularly because working with GPS on either iOS and Android comes with a certain set of pitfalls, but they did a great job.
How did Red Foundry perform from a project management standpoint?
Rob is a great leader and a smart product guy, and Ron is awesome. They did a fantastic job of raising risk with us when it happened, and having them be an Agile shop just like our team was very welcome. Rob did an excellent job of leading the daily stand-up and doing the longer-term planning. There was a lot of collaboration inherent to this project, which added another layer of complexity to the work. In addition to their team, we had developers on our side working on fleshing out the SDK, as well as the services group who built the backend. Their project manager was top notch and they did a good job of coordinating across the fence.
What did you find most impressive about them?
The scope of their estimation in regards to deadlines was incredibly accurate, and as someone who has over 25 years of experience in development, I know that is no simple task. They did what they said they would in the time that they predicted, and they completed it at the cost for which they quoted us in the initial statement of work. This was greatly appreciated from a partner perspective because it created a lot of credibility and trust on both sides. They were also good at understanding the problem that we were trying to solve with the SDK, and are simply great developers.
Red Foundry is made up of smart and honest people who were upfront if and when they ran into problems, rather than hide behind smoke and mirrors. We would have a discussion, make a decision regarding a solution, and then move on. They also brought a lot of great thought leadership to the project, which was exactly what we wanted in a partner. We initially had plans to continue to use them, but because of outside factors, that did not work out. I have a lot of respect for what they do and the work they deliver, and they built a great product for us.
Are there any areas they could improve?
I needed to push them a little on providing a weekly status on how we were running against their financial spend, but eventually they got into the habit of doing so. We did need to have some tougher conversations towards the end regarding sticking to the promised deadlines, and they took responsibility right away. To make up for a bit of friction in that area, they added a couple of features for us pro bono.
RATINGS
-
Quality
4.5Service & Deliverables
"They delivered a high quality end product."
-
Schedule
4.5On time / deadlines
"They executed their plan on time and within budget."
-
Cost
4.0Value / within estimates
"They did great work, but were a little on the pricier side."
-
Willing to Refer
5.0NPS
"I have already referred them to multiple people.