Based on an Ionic3 template + the code from another developer, you'll create 25 screens of a marketplace for the mobile versionf of IOS and Android.
Client will provide Contractor the PSD files for the Application’s UI, and the URL of the Coommerce’s API, along with a minimum of information for the PRD and the Application’s User Experience.
Contractor will gather all the received information, he will ask the Client for any question, and only when everything is clear, Client will be able to start the screen’s development.
A screen can be accepted by Client only against all these conditions:
Client approved that Contractor understood all the screen’s details and is definitively ready to start to develop it.
Contractor developed the PSD file at 100% in term of UI both in IOS and Android, unless Client requires some changes.
In this case, Client can require to change the UI of up to 5 objects in the screen (for example: a slider, a form etc.).
Contractor developed the screen with a quick and intuitive User-Experience, respecting the following rules:
Visibility of system status - The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
Consistency and standards - Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
Error prevention - Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
Flexibility and efficiency of use - Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
Client can require to change the original UX about up to 5 functional/non-functional objects in the screen (an object if for example a professional slider, a loading process, an alert when the user lost the connection to Internet etc.).
The screen doesn’t contain any bug of UI, UX, client-side, and connection to server-side; both for functional and non functional objects; and for all the IOS and Android phones.
In this case, Client can require Contractor to fix all the bugs in less than 24 hours (including regressions on QA and/or on Code Review).
Client approved that the code is ready for production, after doing a code review if necessary. In this case, Client can require from Contractor to fix all the programming issues in less than 48 hours (including regressions on QA and/or on Code Review).
Client approved he detected only less than 10 bugs/code review issues per screen. To avoid such problems, Contractor must checks himself in several environments, before sending a build to Client.
The screen is available for production after QA and code review, up to 72 hours after the Client approved that Contractor understood all the screen’s details and is definitively ready to start to develop it. In case Client doesn’t provide the PSD/API at time, the 72 hours period could be extended without any compensation for the Contractor regarding “any timing issue”.
The screen is ready for deployment in the store of Apple (IOS) and Google (Android), together with push notifications, and deep links both for IOS/Android, even when the user has not installed the Coommerce’s Mobile Application yet.
Contractor will develop at least 25 screens of the Mobile Application of Coommerce, and Contractor will publish the Mobile Application with push notifications and deep-links, both to the store of Apple (IOS) and Google (Android).