CD Library Catalog

This is an application to manage a DVD library. It is fairly simple and straight forward. A data record is created for each DVD. Each DVD can be assigned a category and a sub category. Records can be added/modified and deleted. The data file is saved to XML. There is a communications component that sends the XML file to a server (the server is not part of this project). The Android app just has to be able to send a file to the server and receive a file back. ## Deliverables This is an application to manage a DVD library. It is fairly simple and straight forward. A data record is created for each DVD. The record would look as follows. DVD name (short string) Description (unlimited text) Comments (unlimited text) Release Date (a string mm/dd/yyyy) Category (selected from a fixed list) Subcategory (user created) Rating (1 - 10) Action (a number) Plus supporting data such as a unique record identifier; a time stamp; and other “over head??. Data is stored as Java Strings while the app is running. Data is stored in an XML file Functionality The user can view records by Category; Category + Sub category; or all together. The user can edit data as well. The Application must be able to communicate with a server in two ways. 1. The XML data file will be sent to a sever and be reconciled with a master database (on the server). The Android application is only responsible for sending the file. The reconciliation part is a separate project. The server will look at the time stamps on the records and may send an updated record back to the Android app. The Android app would then look up the record id and replace the current record with the updated record from the server. Synchronization will be by record (not by field). 2. The user of the Android application will have the ability to set a flag which will indicate that an action must be performed by the server. The Android app will send a message to the server indicating an action and some text data. As far as the Android app is concerned, it is sending an integer and some text. The action is performed at the server. Much of the Application has been prototyped in Java so I have a pretty good idea of the required data classes. The basic application is pretty simple from a data standpoint. The actual datafile will be XML. Any open-source XML library that runs on Android would be fine. It is currently implemented with XStream. The UI will be standard Android. Neat and orderly. Since this is a simple text-based app, there are no fancy UI requirements. The most difficult part will be in presenting the data on the small screen. Next to each entry will be a small icon (which I will provide) that will indicate what category the record is in. The developer may request input at any time. Contact regarding user interface options would be greatly appreciated and would lesson the chance of dissatisfaction at the end of the process. Scope will not be changed. Deliverables The deliverable will be a zipped Eclipse Project folder that will build the Application, load it into an emulator, and be run-able from the emulator. The deliverable will also be a separate program file that will be installed and tested on an Android phone. Code will be commented enough so that another programmer can understand what is going on. Time Frame This is part of a larger project and once a time-frame is agreed upon, it is important that the developer completes the tasks as promised. The developer should be conservative when providing time estimates. Major Requirement We are looking for an experienced Android Developer. This should not be the bidder’s attempt to learn Android while getting paid for it. I am a developer myself and don’t have the time to learn the Android platform and commit to a deadline. Please, unless you have created a fully functional Android application (that someone is actually using) don’t bid on this. 1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement). 2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment. b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project. ## Platform Android. The version of Android used will be an ongoing discussion. Since the app doesn't do anything fancy, I would guess 1.6 would be fine. I will rely on the recommendation of the developer for assistance on this decision.