In brief, the software is to work on Symbian OS 8.1 and upwards, utilising J2ME MIDP technologies, though will always consider other similar technologies (C++, .NET, Python etc).
The software shall have two components, one based on the mobile device and one based on a desktop platform, typically Windows environment.
The two components shall have the following functionality:
This should be a standalone program, typically C++ or .NET, though other languages will be considered as cross-platform functionality may be desirable, but initially will be based on MS Windows platforms. It will also require API access from other software to access functions, typically as a library component.
Data sending to Mobile Device component via standard connection interfaces, e.g. Bluetooth, IRDA, Data cable, WiFi - to be user configurable. Data will consist primarily of string types, typically an HTTP URL.
Data can be stored on the desktop component for bulk data syncing or can be instantaneous synchronisation.
Data capture will be web browser based contextual menu item, e.g 'Add link to Sync Database'. Web browser contextual menu support will be MSIE6 and Mozilla Firefox.
Mobile Device Component:-
There are two main parts to this component.
One will be the administrative interface for user configuration, which will only load as and when required. This component will sync, store and show the data that has been synchronised from the desktop component with additional information updated via mobile-internet access to specific URLs. No web browser functionality will be required, only http URL resolution and simple string parsing of the html that is returned.
Data shall be in list format, in categories accessed by tabs or similar.
The other component will be an ‘always on’ monitoring component with two main functions, both of which require monitoring of date time on the device. Date/time conditions will be applied from the data captured through internet access. When certain date/time conditions are met, one of two things will occur: (1) an alarm or alert of some type will activate to inform user, either as audio alert or an onscreen image alert or both, to be user configurable; (2) and/or component will access the internet to update data stored.
Alarms/alerts must be directly linked to the end user's mobile device ringing profile, e.g. General, Silent etc.
Provided reference components:
The PC version of string parsing routines will be provided to the Service Provider as reference code, written in Visual Basic and utilising Windows API.
Interface documentation, requirements and samples will be provided, but architectural changes and modifications can be freely suggested where it would improve and optimise.
All architecture will be vetted by Service Buyer before commencement.
Non-disclosure Agreement of product functionality.
This project will be offered as a White Label product development and all Copyright and Intellectual Property remains entirely that of the Service Buyer.
A high standard of work may guarantee continued repeat business, as there is scope for a future project to proceed based on an existing software product with current user base.
Must have good spoken & written English to provide daily updates regards progress and can provide similar work samples.
ISO accredited companies or individuals will be regarded favourably, though not a requisite for acceptance.
By bidding, you are agreeing to commit to the agreed specifications, to deliver on budget and to deadline.
We are a software enterprise and are well aware of time frames for this project but do not have J2ME or cell phone programming experience.
We know this project is no more than a small project in terms of scale, but are willing to pay for quality, professionalism and reliability.
Process workflow will be provided, and the project manager is also an experienced software engineer, so a high standard is expected from the start.
This is neither an exhaustive nor detailed list of the functionality required, but gives an idea of the type of work involved.
A small change in the remit, so please be aware:
The scope of the project end use is now to cover all Java enabled mobile phones or devices, and no longer exclusively limited to Symbian OS.
This should not be a problem as the functionality of the mobile component is not solely reliant on any features of a particular platform, but please bear in mind that the code use should be either portable or generic.
Functional Requirements have been modified and uploaded in the attached document.
Please provide feedback regarding the modified functional specification. As mentioned previously, this will be an application which will be available for MIDP 2.0 and Symbian based markets, other platforms to follow and subsequent further work will be through the chosen Service Provider.