Mobile App Development for Social Restaurant Platform
- Mobile App Development
- $10,000 to $49,999
- Jan. 2017 - Ongoing
- Quality
- 4.0
- Schedule
- 3.0
- Cost
- 5.0
- Willing to Refer
- 5.0
"I don’t think we could find better quality for what we’re paying."
- Other industries
- Los Angeles, California
- 1-10 Employees
- Phone Interview
- Verified
AppInventiv assists with the creation of a startup iOS app by providing frontend development through map integration, social networking and calendar booking features, and API build-ins.
The in-progress product has already incorporated high-touch social features and engaging functionalities, thanks to AppInventiv’s time investments and detailed feature proposals. The team’s broad technical expertise and quick scaling ability continue to promote success.
A Clutch analyst personally interviewed this client over the phone. Below is an edited transcript.
BACKGROUND
Introduce your business and what you do there.
The company is a social network food app for iOS. I am one of the co-founders.
OPPORTUNITY / CHALLENGE
What challenge were you trying to address with AppInventiv?
We needed to engage an agency with the ability to scale quickly. Like most startups, we have to play the cash-flow game. We’ve been basically bootstrapping this business as more of a side project. We’ve been self-funding, and my co-founder was able to build the backend very quickly—the database and APIs. We were slower in getting the frontend developed. It wasn’t our area of expertise, and we also both have full-time jobs, so it’s been difficult to juggle the two. We started reaching out to offshore dev shops to find one that could help us take the project to completion.
SOLUTION
What was the scope of their involvement?
We’ve done all the UI/UX on our side, and we also built all the APIs, which are custom to our app. AppInventiv has been building the frontend. We’re building a pretty integrated, high-touch social network for food and restaurants, and I know they’ve integrated with several maps. We have a calendar booking request in it as well. Users will be able to share the app via text message and log in only via Facebook, which is one of the APIs they had to build in.
How did you come to work with AppInventiv?
We went on a site called AppFutura and posted our project. We received 50–60 inquiries from companies, and then we reviewed their past clientele and the verticals on which they focused. We wanted to see whether they had a SaaS [software as a service] focus, or e-commerce, or lifestyle. AppInventiv seemed to have a lot of experience in the space we’re playing in.
We interviewed seven dev shops in half-hour increments. In the interview, we were looking at their ability to understand our vision and what we were trying to do. Since they’re so far away, that was a very big point for us. A second aspect we reviewed was the extent to which they’re detail-oriented. Given the communication barrier and the time zone difference, communication would be key. So, we looked at how well we could communicate and understand each other. The last point was the price. We weren’t looking for the cheapest, but we wanted a competitive shop.
We ended up sending an RFP to two firms, including AppInventiv. We chose AppInventiv due to the attention to detail in their proposal. They took the time to dissect all the information we gave them and created a feature list within the proposal. It had every single feature that we thought we wanted to be included in our app—every page, design, and function. That really showed that they understood what we were doing.
They also pushed back on a few of our ideas, saying something wasn’t feasible, which I think is a big deal when choosing an offshore dev shop. Most of them say they can do everything, but they’re not able to do it, and you have a bad product or something that takes forever to make. We chose them due to the combination of those features that we saw through the RFP process.
How much have you invested with AppInventiv?
We’ve invested around $10,000.
What is the status of this engagement?
We started working together in late January of 2017, and the relationship is ongoing.
RESULTS & FEEDBACK
Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
There was a learning curve in the beginning as they adapted to how we work, as we learned to understand their schedule. We have the usual communication and time zone challenges. A lot of our Skype calls would drop because they didn’t have a good internet connection, or their power went out during a storm, or they were in five hours of traffic. That was definitely a learning curve. I’m very detail-oriented, so I like having a lot of detail in communication. That’s one thing I had to work with them on to ensure we were getting the information we needed while not impeding on their ability to do the job.
Overall, I don’t think we could find better quality for what we’re paying. The time they’ve invested and the work they’ve done is well worth the money we’ve paid. I wish we could have had more releases so we could QA on our side more frequently. We’ve found some bugs and also some errors due to poor communication in terms of what we wanted. I guess that’s inevitable in a working relationship like this. I think having more releases could have caught some of these errors earlier and saved time. It might have been my fault for not breaking down the project into more milestones in the beginning.
We are behind schedule. Part of that is just not understanding the scope of work on their side, and part is that we’ve been too busy on our side to put in the time we should have to get everything done quickly. They spend the most time in the beginning understanding your scope of work, the features, and what needs to be done. Then, they spend proportionately a lot less time on the actual development and coding.
We thought we were extremely behind schedule because it took us so long to get to the part where we started product development, but that’s just their process. They’re obviously very good and efficient programmers. Once they understand the project, they hit the ground running. Getting that knowledge transfer in the beginning takes significantly longer than it would with a US dev shop.
How did AppInventiv perform from a project management standpoint?
We share the project management duties. Their team includes one QA person, one senior developer, one junior developer, a graphic designer, a UI/UX designer as needed, a delivery lead, a project cop, and two project managers. We communicate with the project managers twice a week when their Skype permits. Their delivery lead is someone we can go to for issues with the coding or the technical side. The project cop is someone we can email if we have any problems with the team or if they aren’t meeting expectations. I really like having that extra layer of support and being able to activate things as needed.
What did you find most impressive about AppInventiv?
I think the RFP process was amazing. Having gone through it with another agency and after interviewing a number of companies, I think that process was unique to them. They put in significant time to understand our scope of work and our project. They’re not afraid to push back and give you suggestions on design or say you should reconsider your design. I think that’s very good. I like that they have a project cop; I don’t think most places have that.
Are there any areas AppInventiv could improve?
I would improve the ongoing communication with project status, having more check-ins and releases.
RATINGS
-
Quality
4.0Service & Deliverables
"They’re great for what we’re paying."
-
Schedule
3.0On time / deadlines
-
Cost
5.0Value / within estimates
-
Willing to Refer
5.0NPS
"Depending on their needs, I’d definitely recommend AppInventiv.