|
| MobileCore™ Overview |
MobileCore™ services from Zaah consist of the most advanced elements of consumer mobile applications. Wireless technology is an essential component of today's most progressive industries. Recognizing the full marketing and sales potential provided by wireless applications, we make it easy for any business to develop their mobile presence.
Major advantages of MobileCore™ are its flexibility to assimilate with new technology and expand with additional features after the initial version. Zaah's MobileCore™ designs are white-boxed and/or client branded to match exact 'look and feel' required by our clients. |
| |
| Features: |
| Software Activation |
The first time the user launches the application after installation, the application is automatically activated and is invisible to the user except that he has to wait until the activation is completed.
The activation process consists of the following: |
|
The GUID is always included in every SOAP request sent from the client to the server or Windows client (ceHome). This makes it possible to securely identify the user's phone.
Two GUIDs could be used. One is secure and is never sent over HTTP but only sent securely using SMS or SSL (typically used for payment). The other is used in every SOAP request over HTTP or Bluetooth. |
 |
| Image Capture |
|
 |
| The user should be able to capture multiple images in sequence without interruption (see fig 1). When finished, he can click “Continue” and choose what to do with the images just captured (see fig 2). |
| |
| Navigation buttons are used to select thumbnails and the "Menu" button is used to select what to do with the selected image. Some menu options will bring up one or more new dialog boxes. For example, if the user choose to send a picture as postcard, the user is prompted to enter the recipient(s) name and address or select from the address book. The menu items on the "Options" button can be different if the file is video or audio. |
|
|
| |
| Image Options |
|
|
| The options for images can include, but are not limited to: |
 |
Rotate |
|
Send as e-mail |
|
Delete |
|
Send Postcard |
|
Share |
|
Tag / Rename |
|
| The “Continue” button in Fig. 2 is similar to checkout from a shopping cart. If the user chooses any premium options, he must register or select a credit card and fill in the CVV2 code. The instruction and images will now be saved to the server. |
|
|
| |
| Upload Images |
| The user can upload existing images, video and audio files to a server. The user adds one or more files is a screen similar to Fig. 2 with the same or similar options. |
|
| |
| Download |
| The user can download pages, images, video and audio from the server or Windows client. |
| |
| Cache |
| Any type of files downloaded from the server or Windows client (ceHome) can be cached locally on the phone. A property describes if the asset should be retrieved from the server every time (not cached), if it should be deleted at the end of the session or if it should be cached until a new version is sent from the server. |
|
| Navigation |
The following is an example of page navigation that can be supported.
The center icon (bitmap and text) is always selected. The user can use navigation buttons to move other icons horizontally and vertically. The selected icon can be clicked and an event is raised. This event should support opening new pages, send information about what was clicked to the server or Windows client (ceHome), change scene, play/pause/stop video or audio. |
| |
| Send & Share |
| The application also helps the user to share his images with others by using the share feature. The way in which the sharing can work is as follows: |
|
| Phone (Capture or Upload) >> |
Server >> |
Phone |
| |
|
Email |
| |
|
Server |
|
|
| The files are always sent from the client to the server. The server can then share the files online, send as e-mail, send as postcard or send to other servers or ceHome. |
|
|
| |
| Order and Payment |
|
|
The user can register a new credit card or re-bill an existing card. The secure GUID generated during software activation can be included when the client sends payment details using SMS. This GUID will securely identify the user and will also make it possible for the server to detect a new SIM card. |
|
| |
| Offline Mode |
| The client application should also work when no data connection can be established. Only cached assets can be browsed in this mode. Navigation elements pointing to items that are not cached are disabled. |
| |
| Push Support |
| The server can send an SMS to the client. This will trigger the client to check for updates from the server by making a SOAP request. The SMS message will be invisible to the user. |
|
| Change Scene |
The user can change a scene from the phone or the server or Windows client can instruct the client to change the scene. A scene can consist of a client theme (graphical design profile for the client application) and/or device theme (wallpaper, ring tone and screensaver).
The user can also buy and download new themes and scenes. |
| |
| Software Architecture: |
|
|
