You have chosen to sponsor your bid up to a maximum amount of .
If you have never seen a service technician/remote worker app before, have a look at these links to get an idea:
The above links show completed and polished apps. I only need a very basic app and it will be up to you to tell me how much you can get done and for what price.
Server back-end (Java/C#/Delphi)
- needs to run on Windows
- interfaces with RDBMs (any flavour)
- db schema (anything that works enough to demo)
- display of task list (let's say 3 fields as a minimum "name, description, due time")
- able to receive new tasks from server
- persists the tasks to storage
- able to drill from list into a single task
- able to execute "start" and "complete" actions against the task from the single-task view
- able to send actions to server, and to queue (resend timer loop) if offline
- able to work offline/disconnected
- auto switching between wi-fi and 3g
- reads configuration from a local SQLite db (server host & port, "id" of device)
The front-end for creating jobs to send to the Android
The ideal candidate is one who has ALREADY done a similar app or can customize something, so that I'm not paying for you to learn how to develop an app from scratch.
You can ignore the $250 ceiling and you may also give me as many pricing options (xyz for $a, add abc for $b etc) as you see fit. In fact, you can suggest something completely different and add/remove features to fit what you have already have as a starting point. I am only after a starting point from which to build my full solution.
Thank you for reading this far and bidding.
Note: I won't read the bid messages at all. Put your entire pitch into a private message, and if it doesn't start with "All Blacks" on a line on its own, I'm not reading it.
Additional Project Description:
01/24/2013 at 17:46 NZDT
The hanging statement "The front-end for creating jobs to send to the Android" should read:
The front-end for creating jobs to send to the Android app is out of scope. For the purposes of this project, you can use any means to exercise this function, e.g.
- insert into RDBMs and have the server end dequeue it to the device; or
- create the server end as a desktop app with a GUI, from which details can be entered and sent.
Now thatI think about it, a GUI would make things simpler, and you can show the upstream actions in the same GUI. We don't need RDBMs integration or a db schema using this approach. However, if you already have a Windows service, that's fine too. I will consider all options.