Project Detail

Description

I want a clone of Barablu: refer: http://www.barablu.com with all of its features, compelete. The only changes will be the interface N/B: Only Barbble Talk, Barble IM, and Barbble SMS, is allowed to appear on the Interface.

All the features that barablu has is required, so you just clone the exact application of barablu with all of its features, everything. There is no need to send you any documents as all you have to do is download the barablu API and clone it. Then you work around it to support more smart phones, of Symbian types (Symbian Versions 1, 2, 3, UIQ types, MAOP types, and Windows Mobile types.

Note: I do not have any source code to provide to you, so do not ask me for source code, you can download the barablu API from http://www.barablu.com/pages/download/barablu_for_mobile.aspx

I have also attached a zipped file of the barablu API for your convenience.

You will be required to sign a non disclosure agreement.

Be able and willing to work on future evolutions of this project
You are able to build in extremely secure licensing functions

Please do not quote unless you:
have checked the barablu software we are referring to and fully understand the initial mandate,
are absolutely certain that you can deliver what we want and deliver it in time,
have an excellent command of English,
are contactable at all times via email and yahoo
work weekends,
Are excellent at communicating regularly and clearly with your clients,
Will develop live so that we can see progress,
are immediately available to start
are clear in your mind on your quote
You are able to encrypt the software once completed.


Versions and devices ( The software must be able to run on all versions of Symbian OS).

Note that if you use a language other than C++, you may gain stronger cross-phone compatibility. MIDP Java, WAP, and HTML, are all designed to allow user interfaces to be coded without detailed knowledge of the target phone, whether Symbian-OS or otherwise.

Symbian OS is a modular system, and licensees who build products with it are expected to add, remove, and in some cases, modify, components. This means that Symbian OS software written for one phone may or may not be compatible with another phone. As well as cross-device compatibility, you may also want to consider compatibility between different versions (releases) of Symbian OS

Symbian OS phones

The extensive customisation facilities provided by Symbian OS mean that not all phones support all the functionality it offers. There is, however, a large core of interfaces that will be present on all phones. Example of common interfaces are the large Kernel user library (euser.dll), and the engines for the key PIM applications Contacts and Agenda.

Pre-platform developers should therefore rely on the common interfaces. User interfaces are likely to be the area of greatest difference between the Symbian OS and the eventual phone. This variability of UIs, over a common operating system core, means that Symbian OS encourages programs to be written with a clean separation of UI code from application logic (or engine) code.

Symbian OS versions
The following table lists the key versions of the operating system, its major innovations, and the products (announced before December 2001) that use that release.

Name
Innovations
Products

Symbian OS v3.
Eikon UI, Agenda and office applications
Psion Series 5

Symbian OS v5.
Contacts application, Media Server, Messaging, Java (JDK 1.1.4), Telephony
Psion Series 5mx, Revo, Netbook/Series 7

Symbian OS v5.1
Uikon UI layer, Unicode
Ericsson R380

Symbian OS v6.0
Advanced GSM telephony, PersonalJava and JavaPhone, Quartz and Crystal UIs, WAP
Nokia 9200 Series

Symbian OS v6.1
Bluetooth, GPRS
Nokia 7650

Symbian OS v7.0
IPv6, Metrowerks CodeWarrior support, MIDP Java, Multimedia Messaging, Multimode Telephony, Opera web browser, SyncML



Symbian have attempted to maintain backward compatibility so that developers can write code that runs on multiple versions of Symbian OS.

Backward source compatibility means that code written for older versions can be made to run on newer versions by simply rebuilding it. This compatibility has been broadly maintained across these versions, with the exception of the UI architecture, which was substantially changed at Symbian OS v5.1. The best guide to backward source compatibility is the Support information for each item in the Developer Library's API Reference.

Symbian also try to maintain backward binary compatibility (allowing old code to run on newer versions without rebuilding), though this is not always possible when new functionality is introduced. The largest binary compatibility break occurred at Symbian OS v5.1, when Symbian OS began using Unicode, causing a break for all interfaces with string (descriptor) parameters



Additional information submitted:

06/13/2008 at 8:45 EDT:
More clarification

Additional files submitted:
barablu_2_50_29.zip
Barablu_Clone.doc