User Tools
access_types
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
access_types [2014/03/13 21:55] superdupersms |
access_types [2014/03/15 09:06] (current) superdupersms |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| The following access types each have different features. They are listed in the order in which an incoming message is processed. Ideally, you will select the **lowest** priority level suitable for your app. In some cases, your app will be automatically placed, and in cases where another app interferes with your app's performance, it will be re-prioritized. Proper user experience is critical. | The following access types each have different features. They are listed in the order in which an incoming message is processed. Ideally, you will select the **lowest** priority level suitable for your app. In some cases, your app will be automatically placed, and in cases where another app interferes with your app's performance, it will be re-prioritized. Proper user experience is critical. | ||
| - | * **ACCESS_TYPE_SYSTEM** - Please contact us for system level access as a carrier or manufacturer. | + | ====ACCESS_TYPE_SYSTEM==== |
| - | + | //Please contact us for system level access as a carrier or manufacturer. | |
| - | * **ACCESS_TYPE_SYSRESERVED** - Please contact us for reserved, premium access and features. | + | // |
| - | + | ====ACCESS_TYPE_SYSRESERVED==== | |
| - | * **ACCESS_TYPE_ANTISPAM** - Antispam apps block messages from regular messaging and other apps | + | //Please contact us for reserved, premium access and features. |
| + | // | ||
| + | ====ACCESS_TYPE_ANTISPAM==== | ||
| + | //Antispam apps block messages from regular messaging and other apps | ||
| + | // | ||
| [[Antispam Integration|Instructions for Integrating Antispam Apps]] | [[Antispam Integration|Instructions for Integrating Antispam Apps]] | ||
| - | Antispam apps should not request "SMS_DELIVERED" - if you do, you will be denied this permission level and it will default to "unregistered" and your app will not work. This will also help with backward compatibility. Also, SDSMS will send duplicate messages to your app to confirm if the broadcast should be aborted based your user settings. You will not have SMS/MMS write access to the SMS provider. | + | Antispam apps should not request "SMS_DELIVERED" - if you do, you will be denied this permission level and it will default to "unregistered" and your app will not work. This will also help with backward compatibility. Also, SDSMS will send duplicate messages to your app to confirm if the broadcast should be aborted based your user settings. You will not have SMS/MMS write access to the SMS provider. |
| - | * **ACCESS_TYPE_PLUGIN** - SMS / MMS preprocessing for special features. | + | ====ACCESS_TYPE_PLUGIN==== |
| + | //SMS / MMS preprocessing for special features. | ||
| + | // | ||
| [[Plugin Integration|Instructions for Integrating Plugins]] | [[Plugin Integration|Instructions for Integrating Plugins]] | ||
| - | Plugin apps should not request "SMS_DELIVERED" - if you do, you will be denied this permission level and it will default to "unregistered" and your app will not work. This will also help with backward compatibility. Also, SDMM will send duplicate messages to your app to confirm if the broadcast should be aborted or modified by your app. You will not have SMS/MMS write access to the SMS provider, so modifications must be made to the broadcast intent. | + | Plugin apps should not request "SMS_DELIVERED" - if you do, you will be denied this permission level and it will default to "unregistered" and your app will not work. This will also help with backward compatibility. Also, SDMM will send duplicate messages to your app to confirm if the broadcast should be aborted or modified by your app. You will not have SMS/MMS write access to the SMS provider, so modifications must be made to the broadcast intent. |
| - | * **ACCESS_TYPE_AUTORESPONDER** - SMS Autoresponders | + | ====ACCESS_TYPE_AUTORESPONDER==== |
| + | //SMS Autoresponders | ||
| + | // | ||
| [[Autoresponder Integration|Instructions for Integrating Autoresponders]] | [[Autoresponder Integration|Instructions for Integrating Autoresponders]] | ||
| - | Autoresponder apps should not request "SMS_DELIVERED" - if you do, you will be denied this permission level and it will default to "unregistered" and your app will not work. This will also help with backward compatibility. Do not write the received message to the SMS provider. | + | Autoresponder apps should not request "SMS_DELIVERED" - if you do, you will be denied this permission level and it will default to "unregistered" and your app will not work. This will also help with backward compatibility. Do not write the received message to the SMS provider. |
| - | * **ACCESS_TYPE_MSGRESERVED** - Premium access for messaging apps. | + | ====ACCESS_TYPE_MSGRESERVED==== |
| - | Provide enhanced processing and services before standard messaging apps. Please contact us for details. | + | //Premium access for messaging apps. Provide enhanced processing and services to your users before standard messaging apps. Please contact us for details. |
| + | // | ||
| - | * **ACCESS_TYPE_MESSAGING** - Standard text messaging apps. | + | ====ACCESS_TYPE_MESSAGING==== |
| + | //Full-featured messaging apps. | ||
| + | // | ||
| [[Full Featured App Integration|Instructions for Integrating Full-Featured Messaging Apps]] | [[Full Featured App Integration|Instructions for Integrating Full-Featured Messaging Apps]] | ||
| Line 37: | Line 48: | ||
| //It is important to **NOT** follow all of Android's recommendations when you are not the "Default SMS App". Proper integration requires that your app only disable them when neither your app nor SDMM is the "Default SMS App". SDMM allows your app to continue to function properly as if it were the default app.// | //It is important to **NOT** follow all of Android's recommendations when you are not the "Default SMS App". Proper integration requires that your app only disable them when neither your app nor SDMM is the "Default SMS App". SDMM allows your app to continue to function properly as if it were the default app.// | ||
| - | * **ACCESS_TYPE_BACKUP** - Backup apps will have full access to the SMS database. | + | ====ACCESS_TYPE_BACKUP==== |
| + | //Backup apps will have full access to the SMS database. | ||
| + | // | ||
| [[Backup Integration|Instructions for Integrating Messaging Backup Apps]] | [[Backup Integration|Instructions for Integrating Messaging Backup Apps]] | ||
| Line 43: | Line 56: | ||
| Since the system broadcasts "SMS_RECEIVED", SDMM will do the same (in the event that Android changes that going forward). If you integrate with SDSMS, you will be able to provide full backup/recovery without user intervention or action. | Since the system broadcasts "SMS_RECEIVED", SDMM will do the same (in the event that Android changes that going forward). If you integrate with SDSMS, you will be able to provide full backup/recovery without user intervention or action. | ||
| - | * **ACCESS_TYPE_OBSERVER** - Observers will simply receive an additional SMS_RECEIVED broadcast. | + | ====ACCESS_TYPE_OBSERVER==== |
| + | //Observers will simply receive an additional SMS_RECEIVED broadcast. | ||
| + | // | ||
| + | |||
| + | ====ACCESS_TYPE_UNREGISTERED==== | ||
| + | //Apps that integrate with SDMM but are not registered with an account. | ||
| + | // | ||
| - | * **ACCESS_TYPE_UNREGISTERED** - Reserved for apps that integrate and do not request an appropriate Access Type (either based on their requested permissions, behavior, SDMM review, attempting to modify the SMS tables with authorization, etc.) | + | Reserved for apps that integrate and do not request an appropriate Access Type (either based on their requested permissions, behavior, SDMM review, attempting to modify the SMS tables with authorization, etc.) |
access_types.txt · Last modified: 2014/03/15 09:06 by superdupersms
Page Tools
