Android/J2ME and XMPP

Cerrado Publicado Dec 14, 2010 Pagado a la entrega
Cerrado Pagado a la entrega

SSA is looking for a fast and reliable Android/J2ME developer to work on an integrated client app for Android. Inexperienced developers should refrain from this offer, as full satisfaction guarantee is a MUST. The client app unifies Facebook, Twitter, Gmail, Yahoo Messenger and RSS feeds into a single app. All above mentioned message types would arrive from our propriety XMPP backend server. The communication between the client app and the backend server would be performed via XMPP protocol (message types [XMLs] will be provided to the programmer).

## Deliverables

App Design and Specifications SSA (Securenet Sistemas Avanzados SL, Spain) is looking for a fast and reliable Android/J2ME developer to work on an integrated client app for Android. Inexperienced developers should refrain from this offer, as full satisfaction guarantee is a MUST. The client app unifies Facebook, Twitter, Gmail, Yahoo Messenger and RSS feeds into a single app. All above mentioned message types would arrive from our propriety XMPP backend server. The communication between the client app and XMPP backend server would be performed via XMPP protocol (message types [XML] will be provided to the programmer). 1. The name of the app is “Social Gear??. The icon for the app is provided below. 2. A good starting point would be to customize one of the many light XMPP android clients (e.g. Jabbim, Jabiru, Jabbroid) to the look and feel specified below. (Please see attached full source code of [url removed, login to view]) 3. The app’s main screen should be similar to the following screenshot. The top gallery is a folder list. The vertical item list is the messages entry. The vertical gallery buttons would filter messages by “All??, “Facebook??, ??Twitter??, ??RSS??, “Gmail??, “Yahoo Messenger?? and “Advertisements??. An additional entry in the gallery would be “Settings??. 4. Upon first time use of the App, the user will be prompted with a Terms and Condition page. (Text to be supplied to the developer) 5. Upon agreeing to the terms and condition page, the user would be directed to the “Settings?? page where he would specify his user/password to our XMPP backend server at http://www.azcalabs.com. (See look and feel). 6. Our XMPP server will push user Facebook, Twitter, Gmail, Yahoo Messenger and RSS activity to the IP address assigned to the android device. The correspondence between the client App and the server will consist of several Message Types (XMLs). 7. When a ‘new incoming message’ icon appears in the notification status bar, a click on the notification should open the App’s main screen. The App should receive and parse the XMPP messages quickly and efficiently so that messages are displayed immediately upon opening the App with the following information: message type, date and time, sender info (photo and name), subject and short header. All messages should be sorted into the different folders according to their type. 8. The incoming messages should be sorted into the following folders: All, Facebook, Twitter, Gmail, Yahoo Messenger, RSS and Advertisement folders. 9. Only upon opening a message should its full content be displayed. Messages from Facebook, Twitter, Gmail, Yahoo Messenger, RSS clients should be loaded into their respective clients. Any reliable and quick open source clients (Facebook, Twitter, Messenger) would be acceptable. E.g. Facebook: Babler, Blooo. Twitter: twittli, etc. 10. Only the look and feel of the abovementioned Facebook, Twitter, Gmail, Yahoo Messenger and RSS clients is required. Any activity within these clients will create and send an XMPP request message to our backend XMPP server, rather than execute the code locally on the device. The XMPP backend server will respond with an XMPP response message that will contain the requested data to be displayed on the device. 11. While using these clients, the user can click the “Back?? button, to go back the of Social Gear main screen. 12. By default, every folder should display the most recent 15 messages. An option to load the next 15 messages should be programmed. Upon arrival of a new message, it should be placed at the top of the corresponding folder, pushing the oldest message out. 13. The option button functionality should consist of the following: select/deselect all messages (or specific ones), mark as read/unread all messages (or specific ones) and delete selected messages (move to trash bin). By default, unread messages should be seen in bold. (Similar to the K9 mail client) 14. The client app should be capable of handling XMPP media file transfers. If file type is not registered in the system, give the option to open that file, with one or more of the installed programs on the device. 15. App has to be compatible with Android 1.5, 1.6, 2.1 and 2.2 and adaptable to all screen layouts and sizes. 16. App should use minimum memory usage, maximum performance, and be immediately responsive to any operation by the user. Terms and Conditions 1. The project delivery must include: all source codes and other related files to the project, clear and accurate documentation, design and analysis documents, flowcharts, UML and any other associated documentation. 2. Project delivery should include the following steps: analysis, design, implementation, testing of the product and publication in Android Market place. 3. All source codes, related files and documentation will be the sole property of SSA and shall be governed by Spanish law of intellectual property. 4. Daily communication channels (email and Skype) with the developer is necessary during his working hours. 5. Communication language is English. 6. Project deliveries and corresponding payments will consist of a series of short work packages of 4-5 working days each. 7. Signed acceptance of the above terms and conditions is a prior condition to the execution and delivery of the project.

## Platform

Android App - J2ME - XMPP

Android Seguridad informática Desarrollo de apps móviles Gestión de proyectos Seguridad web XML

Nº del proyecto: #2984409

Sobre el proyecto

Proyecto remoto Activo Dec 30, 2010