In some ways, a mobile app development project is no different to any other software development project. Some common important issues are: concurring whether it is to be a fixed price or time and products task, working how and when the functional requirements will certainly be agreed and captured, picking a total task timetable and, naturally, concurring who will certainly own the intellectual property rights in exactly what is created (especially if pre-existing software and/or open source software is being leveraged).
However, with a mobile app development project there are some certain issues that have to be carefully read through, including the following:
Compliance with terms of platform providers— some platform carriers (e.g. Apple) are more prescriptive than others (e.g. Google). Plainly, the client will certainly want to try to flow down as much of the problem of compliance on to the developer as possible– especially if the customer is the one with the direct contractual relationship with the platform company. Nevertheless, even if it is the developer who has entered into the developer arrangement with the platform service provider, if it is the customer’s app, the client will wish to ensure the app complies. For instance, Apple’s terms consist of different provisions stating that app functionality should not override or disrupt Apple-implemented informs (e.g. Coding around use of location or address book data) or, if it includes certain functionality, that users have to be informed and their consent acquired. The customer will certainly desire specifics like this to be addressed either as requirements in the spec and/or by way of a warranty from the developer that the app adheres to all requirements of the platform provider. The trouble is, this is something of a moving target. The platform service providers reserve the right to change their terms at any time, and are for that reason totally free to change or present new requirements. Who handles the legal duty for compliance– the client or the developer? An added issue is that not all platform carriers’ terms are publicly available. Apple’s are not, for instance, unless you pay to subscribe, and other, more niche, platforms appear to run something of an ‘under the counter’ method to their terms. There is for that reason no assurance that what you show up by simply doing an internet search actually is the set of terms that currently uses. Both client and developer therefore have a vital task to inspect exactly what they, or the other party, have signed up to with the platform service provider, and precisely what the requirements are that need to be factored in.
Acceptance-– what will success appear like? Developers and clients are familiar with approval criteria, however the customer might want it concurred that confirming conformity to requirements only totals up to interim or conditional acceptance, which full acceptance just happens when the app in fact gets accepted by the platform service provider(s) for noting on the picked platform(s), and to make the developer particularly responsible for guaranteeing that takes place. Developers will certainly be less eager to be on the hook for something that they can not, eventually, control (considering that platform service providers are never ever required to accept any app).
Hosting-– in the app context, hosting normally only associates with dynamic material, because Web site url the platform supplier(s) will host the app itself, although it is possible that, if the app is to be offered from the customer’s own web site, it could desire the developer to host it. Given that much of the value and appeal of an app will certainly be in vibrant content, the client will desire control of this, and for that reason will need to concur whether it, or a third party, is going to supply a content management tool.
Support and maintenance— having got the app accepted by the platform company(s), the customer will certainly be eager to ensure that updates provided by the developer (presuming that is part of the developer’s continuous responsibility), whether correctional or to enhance functionality, are also accepted by the platform company(s).
