IPAD CRM Project

Project Description:
I have a completely functional cloud based CRM software system that is very functional. However, I need to start adding mobile solutions. I have a mobile web app, but that leaves a lot to be desired. I want to create several apps (over time) that will duplicate my cloud based CRM app. I need to develope a relationship with a developer that can work on this project a few days a month. This developer needs to have experience with developing pure IPAD apps and have existing apps in the apple store. I am planning on doing this in stages:

Stage 1) IPAD app to handle the basic menu system of the app.

This section of the project will consume a web service from a web server that will return all available menu options. The IPAD user will have a setup screen that defines the user login, password, and a few other details that the system needs to login to the correct server. I have an existing windows desktop program that performs this process. However, it would be great if we could use the facebook or linkedin generic login routines that validate the user based on the linkedin or facebook login.

The web service will return the menu options to the user based on the user's role within the CRM system. My DBA will handle the MS SQL backend and my web programmer will handle the web services needed.

For this section of the code, I need a good IOS programmer that understands the base Apple Store requirements that must be performed to have an app get registered in the store. The completed app will be registered, however, since this first phase is only a menuing system, we do not need to worry about getting the app registered with apple.

The existing CRM system will be available for the approved candidate to work with and review in order to understand the end result desired.

Stage 2) IPAD app to handle the Customer section of the App.

This stage will handle the basic customer setup and update. At the end of this stage I will need to get the app registered with the Apple Store for download. I also want my end users to be able to download the app free of charge. However, at the completion of the overall system, the complete app will be available for download via the app store for a given price. The idea here is to allow private sales reps use the system on their own with a minimal per month cost.

My browser based windows system allows the desk top to look at incoming phone calls and pop up a screen that has all the customer information on it. Ideally I would like this functionality on the IPad. I am not certain this can be done, but it is a goal.

Stage 3) IPAD app to handle the Product/Inventory system of the app.
Stage 4) IPAD app to handle the Order Entry system of the app.
Stage 5) IPAD app to handle the Contact Entry system of the app.
Stage 6) IPAD app to handle the Calandersystem of the app.
Stage 7) IPAD app to handle the Campaign/Bulk Email system of the app.
Stage 8) IPAD app to handle the Setup system of the app.

As you can see, there is a lot of work to be done. That is why I am handling it in phases. I may choose to bring this project in house at some time. However, my plans are to complete the first two phases through Freelancer. I need the code to be well documented (because my team currently works in VB.NET/ASP.NET).

This first phase should be considered a way for us to get to know each other's working knowledge. Not everyone can work together and my way of managing projects is not easy to work with. Being a programmer myself, I know when someone is trying to "blow smoke" and really does not know what they are talking about OR when they are trying to "pad" their hours.

If the selected person does a great job on the first phase, the second phase will be done without bidding.

So let's get started!!!

Additional Project Description:
01/25/2013 at 4:41 IST
==========================================

I added two power point presentations to this project. These presentations should define exactly what I want. If you wish to adjust your bid afterr viewing these presentations, please do so.

The first power point is a representation of the different screens I will need for this first phase.

The second power point defines the flow of the system when a user first downloads and opens the app. After the first time, we need to insure we open the app on the screen that allows the user to login. If the app is just inactive (not rolled out of memory) we need to open at the last place the user was at.

All of the information in the login screen must be stored locally on the device.

All menu options must also be stored locally. However, when the user logs into the system, these menu options will be reset.