Write an iPhone application

The application should serve our customers on administrative and serve as a control for people trying to enter the show purchased. Eventually the app will know to tell the conductor Bead Shrine of whether the card correctly and whether the client is allowed to enter. Characterization app: Customers can download the app what the AppStore (or Google Play - below). The application consists of four screens only and is very simplistic. Screen 1 - login screen This is the first screen that appears after the conductor pulled the app. After typing login, the application will send a POST request to sign in and receive an answer in JSON with success or failure with detail if there was an error. If the client successfully connected the application will store the login information. This screen will appear only once unless the login is incorrect (for example, when the details have changed in the system). This screen will have three fields and a button "Connect": Company Name: Example: smsite User name Password Screen 2 - Screen, Scan This screen will be a single button "Scan". Clicking on the button will activate the camera device and allow the conductor to scan barcode from iphone to another or a printed page. Bar - will sort datamatrix code or code128. All Bdkod represents a single - the values ​​of the entry ticket. Upon receipt number, send the application in HTTP / POST the same number and you will get back an answer to one of the situations Hhbaim: System right - to display an appropriate message on the screen. Note that the message should be positioned in such a way not to interfere with another scan! When there are 200 people with tickets at the entrance to the Hall must not delay the application would be a entrance. System right but it is used in the past - in that case the conductor discretion allows the customer to enter or not. The application will display a message that * requires reference from the conductor. The options are: "You can enter" or "Cancel". Each selection will be sent to the server in POST. Invalid card - the app will display a message that * requires reference from the conductor. This post has one option: "OK." * See a message that requires attention from the conductor software will prevent another scan to reference conductor. Screen 3 - Change Job Status: off-line / on-line This screen allows the software to avoid sending and receiving answers to what webapp. Such a situation is possible only if the login information stored in the system. Off-line mode can not receive notification from the server if valid cards, and therefore, the role of the application feel to keep the tickets scanned and the amount of times they have been scanned (screen 2). If the application returns to "on-line" application will send all the cards scanned into the webapp in POST. After posting an answer from the server will be success or failure Depending on all the scans are saved will be deleted Mhmcisr. Screen 4 - Screen "About" This screen will appear with regular text phone numbers and contact information with the office. Notes: Every time you open the software, it will see "connect" to the webapp. Application interface always displays the opening screen 2, unless login abnormal or wrong - in that case screen 1 will be displayed. A library for reading and translation with a barcode open source license for businesses called ZBAR your use. You can see it at the following link: [login to view URL] Option of working off-line is an option. We might want to give it a start. All you need from the server we can provide you. Do not invest time to design software. I will send to you later graphic materials including application design. At the moment it is important to do something simple and works. If you have more ideas to the application or things escaped me know. How long do you think can take to build such an app?