For any given app, there is usually two parts that needs to be done. The actual App code inside C or Java. And the connection to a web-based data storage through a web service or an API. There can be apps which do not rely on any database to maintain state or load fresh data. But this usually holds true for most mobile apps. Recently, we have had to share our Mobile app work with a client who already had a database (and a working website) and wanted us to take care of the mobile apps. All in the same time, the client had retained the original developers to work on API in parallel. Though it looks innocuous on paper, in reality there were a lot of logistical issues that sprung upon us in subsequent months.
Here I am going to discuss issues generic to this scenario. They may not all apply to you but its better to be aware.
If there are more than one companies involved in a work process, there is always a chance that there is miscommunication or lack of understanding of each other's point of views. One company maybe using Jira while the other maybe using the Trello. Both companies will be probably be maintaining their own task lists and will have their own priorities. Clients communicate similar information to both parties but the task scheduling can vary.
With different priorities, companies will look after their own tasks more than that of the other vendor hence creating unseen delays and frustration for client. The developers on both sides will have their tasks of sets of finish and will test scenarios pertaining to their deadlines.
Its a human nature that we always prefer the 'known devil'. Similarly in hiring companies for app development, the team relatively unknown will take a bit of getting used to by the client. Its only natural to shift all the blame to the new guy and something that may cause the friction during project.
With two teams involved, there is a chance that client may judge one against the other and mental images will create in the her mind about one team being better than the other. This may not necessarily be the case as teams maybe used to a certain way of development and could provide reasons behind their choices.
During such situation, it may become difficult to pinpoint the party at fault and client may become ping pong between the two vendors. It can happen in case of mismatching data types or API documentation or database versioning.
Posted on March 15, 2017
Need a project quote or more information about our services? Use the form below for the fastest 8-12 hour response. Or you can pick a phone and call us or follow us on social media.