FAQ-1090 Advice on instigating a billable event from your application


FAQ-1090 Advice on instigating a billable event from your application

» Symbian OS » Developer Knowledgebase » FAQ-1090

Classification:	General	Category:	Symbian Signed
Created:	07/16/2004	Modified:	04/24/2005
Number:	FAQ-1090
Platform:	Not Applicable

Question:
My application generates a billable event. How should I handle this?

Answer:
If your application takes advantage of the communications features in a Symbian OS phone and produces a billable event, you must be sure to notify, and seek approval from, the end user. A billable event is anything which will result in a charge to the user's network account - for example, sending an SMS, setting up a HTTP connection, initiating a voice or data call, etc. Not only is gaining approval for such activities good practice, it is a requirement for passing the Symbian Signed process. However, if your application makes heavy use of these features, constant warnings and confirmation requests can become a hindrance rather than help for users. Symbian is therefore issuing the following 'best practice' advice for dealing with billable events:

1. The first time any application makes a billable event after installation, the user must be presented with a dialog box to approve the activity. For example:

MyApplication will now connect to the Internet.
This will result in a charge to your phone bill.
Do you wish to continue?

and allowing them the option of cancelling the event.

2. Every such application should also provide a Preference/Setting which the user can change to remove future warnings. For example:

Prompt for billable events [Yes,No]

The default value for any such setting must be that the user is asked. This setting should be persisted in the program's INI file. If the user changes this preference to ensure they are not asked, you can forego using warning/confirmation dialogs in future.