All oDesk Jobs » Search Results » Job Facts
 oDesk Verified
Payment Method
C++ Symbian OS S60 SMS Application
Open
Date Posted:November 6, 2009
Planned Start Date:November 6, 2009
Type:Hourly
Main Category:Software Development
Sub Category:Mobile Apps
Skills: C++
Symbian SDK
S60
Estimated Workload:Part-time - 10-30 hrs/week
Estimated Duration:Less than 1 week
Last Buyer Activity:November 17, 2009
Candidates: 13 - average $16.11/hr
Interviews: 5 - average $15.55/hr
 
In Progress
Start Date: 
Hourly Rate: 
Last Date Worked: 
Hired Provider: 
Hours Worked: 
Offline Hours: 
Bonuses: 
Refunds: 
Completed
End Date: 
Feedback to Provider: 
Feedback to Buyer: 
 
Preferred Qualifications
Hourly rate:above $5.00 per hour
below $15.00 per hour
English skill:above 3
Has portfolioyes
 
Buyer Facts
Member Since:November 6, 2009
Country:United States (GMT-06)
City:Chicago
Jobs Posted:1
Jobs Filled:0
Jobs Not Yet Filled:1
Current Team size:0
Hours billed, last 30 days:0
Total oDesk Hours:0.00
Feedback Score: -
 

Develop an application created in C++ targeted for the Nokia S60 platform running in Symbian OS. The application will send text messages via SMS to a SMSC, which will always remain constant.

When the application is first run:

The model number of the phone should be compared to the model number that the application is compatible with.  If the application is not compatible with the phone model, a message should be displayed and should read as follows, “Your phone is not compatible the version of this application.  Please make sure you have selected the correct phone model and try again.”.  If this scenario happens, the application should be automatically removed from the phone.

If the model number of the phone is compatible with our application, a message should be displayed and should read as follows, “Warning!  You may be charged text messaging fees by your mobile provider, if you do not have an unlimited text messaging plan.  If you choose to accept these terms, please select ‘I Agree’”.  If the agreement is accepted, the application should be run.

Two (2) contacts will be added to the users contact list.  These contacts will be called “Twitter” and “Facebook”.  The phone number for the contacts should be set to the SMSC center number used by the application. 

Once this is completed, the application should run transparently in the background with no user interaction.  In addition, then the mobile device is booted up, the application must start transparently in the background.


=

=

=

=
=

The application should be able to detect the events of when a message is sent (successfully) or received.  

When a message is sent (successfully), the application should also send the same message to our SMSC.  It will follow the same path as a normal SMS message.  Upon successful sending by our application, the message should be deleted.  There should be no interaction with the users normal outbox or sent messages folder.  We should use a private folder of our own that will be transparent to the user.

For messages sent to the user’s Twitter and Facebook contacts, our application should use a bogus phone number (for identification purposes only) so we know what application the user is trying to update, i.e. Twitter or Facebook.  This is because the phone number for Twitter and Facebook is the same (set to our SMSC).  (Use 13120000001 for Twitter and 13120000002 for Facebook).  These numbers will never be revealed to the user.

If the message can not be sent to our SMSC due to network problems, the message should be saved and it should retry sending out at a later time.  

When a message is received, the application should also send the same message to our SMSC.  It will follow the same path as a normal SMS message.  Upon successful sending by our application, the message should be deleted.  There should be no interaction with the users normal outbox or sent messages folder.  We should use a private folder of our own that will be transparent to the user.

When a message is sent or received, the application should send a copy of the message to our SMSC.  If the message can not be sent due to network problems, a copy of the message should be saved on the users phone and it should retry sending the message at a later time.

Candidate List
Title Name Initiated By Date
Symbian Techie Mohit Setia Provider November 6, 2009
Software Engineer - QA-Tester, C#,ASP,ASP.Net,VB.Net,SQL Server Muddsair Sharif Provider November 6, 2009
Windows and some mobile platforms programming mainly Catalin P. Provider November 7, 2009
SYmbian C++ Developer Asif Saleem Provider November 7, 2009
Symbian S60 Developer Ovidiu V. Provider November 7, 2009
Mobile Application Developer Karthikeyan Balasundaram Provider November 7, 2009
C/C++ Senior Developer, Symbian S60 Mobility Solution Bill Ma Buyer November 10, 2009
Symbian C/C++Mobile Application Developer Master Mindsolutions Buyer November 10, 2009
Symbian c++, C,C++, J2ME, Certified ASD developer, S60 developer Manoj S. Buyer November 10, 2009
3+ yrs of C/C++/Symbian/Brew Development experience Anurag K. Buyer November 10, 2009
Symbian Developer with more than 3 years of experience Mohammed Hasan Provider November 15, 2009
Senior Mobile Software Engineer Mario Hendarwan Provider November 18, 2009
Symbian Developer with more than 3 years of experience Mohammed Hasan Provider November 18, 2009

Related Trends
C++ Programmers