Android mobile job control app

JobControl App: A small number of Android phone users, about 20, need to receive their daily JobLists from a shared web address. As the day progresses, the users will record their results on the Android phone. As each job is completed, (or as soon as good enough communications are available thereafter), a JobResults file should be created or updated on a second shared web address. The JobLists are in csv format, and these files will be created by an existing sytem, with ftp over to the shared web address. The production of these JobList csv files is not part of the quote. The data in the JobList csv files is intended as the input to the Android app, and an example file is attached. The JobList filename format is [login to view URL], and an example filename would be [login to view URL] As the day progresses, and jobs are completed, the completion date, time, duration, mileage, and comments are to be recorded in the JobResults file. The JobResults filename format is [login to view URL], an example filename would be 31-05-2011-R-AndySmith.csv. All users will use the same two shared web addresses, one for JobLists, and one for JobResults. The JobList App must enable the users to browse their JobLists for the last week, and for the next couple of days, and record their results as required. JobLists may change on the shared web address at any time, in which case the Android app must get the updates without user input. The date and time on the shared web addresse will change if it is updated. User input should generally not be expected to deal with data transfers to and from the web, though there should be an indication of good or bad communications. User input should be aided wherever possible, so the JobCompletedTime field should be preset to the current time, JobMileage should be preset to the previous mileage entered, and JobComments should be able to come from a picklist of common comments the user can save and re-use over time. ## Deliverables 04/06/2011 The original description has not changed. The following provides further clarification of how the app will be used, and answers questions that have been asked. Many thanks for such questions, and feel free to ask more if needed. The individual users will have HTC mobile phones on Android 2.2 and can run the app on it whenever they choose. There should be no need for the user to login, (or at least not after initial setup so the app is aware of the user's name). The shared web addresses will also need to be entered during app setup. In normal use, the user will choose a date and look at whatever jobs are present. Jobs may then be done in any sequence. The dates available should be for up to one week in the future, and one week in the past. The HTC mobile phone has to retain this data, and only communicate with the host site when it's necessary to obtain new data, or to upload new results. The user will enter information related to the job as completed, and that information will be uploaded to the web server without pressing any button as soon as good communications are available. The user will also click an EndOfDay button or similar when the day is completed, and that information will be uploaded to the web server as well. The data transfer between web and mobile app can be of your choosing, but the final JobResults csv output file is to be as per the original description. FTP is being used to interface with existing systems, but there is no requirement to use FTP for data transfers to and from the Android phone. No graphics are required, and standard widgets and textual buttons will be acceptable. If needed, button background colours should be green for normal naviation, e.g. "Next", and orange for less common navigation, e.g. "Back". Some sort of basic authentication / registration will be needed, and it is expected that a user's phone will be registered at the time of app setup, and subsequent use of the app should not require the user to login / register again. The user keeps the same phone, and their details do not alter. You would need to provide anything that's needed to run at the web end. Web services can be php or java, as long as well structured and well documented source code is provided, and we can get your script/web service running on our linux host. We would expect that the client will not need to keep polling, or communicating with the server. On an earlier windows mobile app we had the server end send a text message to a windows mobile phone, which notified the app to download the new data or updates. It is hoped that the Android platform has some better way for the server to notify the app of new data or updates, and either supply them, or get the app to request them without user interaction. * * *This broadcast message was sent to all bidders on Saturday Jun 4, 2011 8:29:08 AM: 04/06/2011 Hi, The original description has not changed. The Detailed Requirements section has been used to provide further clarification of how the app will be used, and answers questions that have been asked. Many thanks for such questions, and feel free to ask more if needed. Regards, qkim