Palm Os Sms
The application will send text messages via SMS to a SMSC, which will always remain constant.
This is for palm os. I’m willing to pay $100. It can be in java, c, c++ or whatever.
When you do the work. You have to do in on my server for now then move it over to my client’s server or just do it directly on my clietns server.
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.
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.
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.
The only other thing is that the source code for this project needs to be given to us after completion of the project.
Additional information submitted:
03/03/2010 at 3:13 EST:
How the application will work:
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.
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.
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.
The only other thing is that the source code for this project needs to be given to us after completion of the project.
Deliverables
The application will do the following tasks.
1. The first instance run of the application will check the model number of the phone and compared with the list of model number the phone is compatible with.
a. If not compatable an alert is displayed as phrased below
i. Your phone is not compatible the version of this application. Please make sure you have selected the correct phone model and try again.
2. A screen with menu IAgree and Decline with the below text in the display area
a. 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’
3. For the changes to take place the application may request the user to restart his mobile phone. He can also do it manually later on.
4. Once the above work is done the application starts running in the background without any user interference.
5. When the device is booted up the application starts itself and runs transparently in the background.
6. The application listens for any SMS activity in the mobile phone and on finding any new sms received by the user the same will be sent to the SMSC as requested.
7. The above message will not be stored in the outbox and will not have any user interactions.
8. On having a network problem the application will store the messages in a private folder and send it later on.