We want to develop a Geolocation native app for Windows Mobile 6.5. Attached is a mockup of the iOS version of this app, it should work similar for Windows Mobile 6.5 version.
The app perform a basic function: send information about the smartphone (IMEI, latitude, longitude, battery, speed, date and time, etc) to a web service at specific times. The web service is going to respond back with instrucions for their next action to be taken. They will also need to store some small amount of information on the smartphone as part of the application features. Since all the heavy work is done in our backend, the apps are fairly simple, having just 6 screens:
1. Splash screen
This is going to play a first-time video or animation showcasing the product. We will provide this, after the video completes it will automatically takes users to the authentication screen.
2. Authentication screen
In this screen is where the user have the option to either start a session as an existing user or create a new account through our web service. The elements to include in this page are:
Sign up with Facebook button
Sign up with Email button
Already in Kipo button
3. Log in screen
In this screen is where the user logs into his account (if he already has an account set up at our web service).
There are two boxes to input text here: username and password. The user enters them and we check if the account and the credentials match in our web service. If so, it takes them to Add Device screen directly.
A button on this screen says Don’t have an account? Which takes him to the Sign up screen.
4. SIgn up with Facebook screen
This is the option the user sees if he chose to create the account using Facebook. We use Facebook to retrive the user’s: profile picture, first name, last name and email address, and display the info to him (editable). We check the user’s chosen Facebook username in our user’s database. If it is available, we display it as text with a green check next to it “username available”. If not, the text box is empty for the user to input a username. All the text boxes (email, name, last name, etc are editable).??We require the user to choose a password with enforcement requirements, all this information will be sent to our web service to be validated and stored otherwise an response back with possible validation errors/issues will be issued.
5. SIgn up using the old-fashioned way screen
In this option the user has to enter manually all the information that the Facebook option would have given automatically, which includes first name, last name, email address, profile picture, username and password.
In both options they click on a “create account” button, which takes them to the Add Device screen after successful response from web service.
6. Add Device screen
The application sends to us automatically the smartphone’s IMEI number. We check in our database to see if the device is currently associated to another user with the following possible scenarios:
If so - We display an error page: You can't add this device because currently it belongs to @username. Buttons: Contact us for help.
If not - We display the Add Device screen.
In the Add Device screen, the user has to chooose a device name, an optional device description and a device profile picture.
He clicks on “Add Device” and that device is associated and added to his account.
7. Active device screen
This is the app’s only screen once the device is already added and is being currently in use.
It has the following elements inside:
Link to help
** We need full access and property rights to the source code and any other additional support files.