Mobile Android application developemnt in Arabic

Addendum (1): Mobile Application Simple Description. (Arabic Interface) I. Web service backend A web service should be developed to provide access for mobile applications used by Field Observers. The web service works as the link between the mobile application and a new database (referred to as the web service database) that will be created to save Humna Rights (HR) cases uploaded by Field Observers. The main functionalities the web service will provide: 1. Authentication. User accounts will be created for every Field observer on the web service. Field observers must authenticate (Log in) to the web service before being able to upload any images, input forms, or documents. The web service must provide an API endpoint for authentication (Log in). 2. Uploading Cases Data. The web service will provide an API endpoint that the mobile application will call to upload (report) a new HR case. This endpoint should accept HTTP form data input as requested in the HR violation form. This API endpoint is only accessible by authenticated users. Preferably all data uploaded should be encrypted using the encryption keys described in notes 4 and 5 below. 3. Admin User Access. The web service should provide an admin user interface (or database access to the web service database). The Admin user should be able to create users (Field Staff) and export uploaded HR cases and all their attachments to a format that can be easily imported into the current CMS database (MS SQL) Note: when exporting data it is important that there be a feature that enables only exporting data that has not previously been exported. It is important that not every time the admin user exports data from the web service backend no duplicates are imported into the Case Management Database (CMS )database. The following comments are best practices that are extremely good to have. 4. Decryption 5. Public Encryption Key Exchange The web service should provide an API endpoint that the mobile application will call in order to retrieve the public key to be used to encrypt uploaded data. This API endpoint should only be accessible by authenticated users. II. Mobile Application  A “write-only” mobile app for Android that uploads photos and data forms to a remote database system. (Data forms should be in a standardized format, exactly similar to the forms accepted by the web service and the ones imported into the CMS)  The mobile application allows Field Observers to take a photo with their phone or tablet (or other mobile device) and quickly back it up securely to be retrieved at a later point. This feature is especially useful if the Field Observer is presented with situational threats and requires quick action.  The mobile applications will allow users to submit data collected through forms, as well as images and other attachments, to the web service backend.  The mobile application encrypts all photos and input data collected. None of the collected data is readable on the mobile device.  Data encryption is done using Field observer designated encryption keys.  The mobile application uses the web service backend to authenticate its users (Field Observers). Uploading photos and data will require users to be authenticated.  The mobile application retrieves the user's (Field Observer’s) public encryption key from the web service backend. User keys should be retrieved once the user authenticates and are used for the remainder of his/her session.  Data can be sent to the web service backend, but it cannot be read on the device it was created on.  Data must be removed from the mobile device as soon as it has been successfully uploaded to the remote database.  Clean, user friendly interface with minimizing the end user input by depending on look-up tables that will be provided to the developer