User Tools
access_types
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
access_types [2014/03/13 21:54] superdupersms |
access_types [2014/03/13 21:55] superdupersms |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| [[Full Featured App Integration|Instructions for Integrating Full-Featured Messaging Apps]] | [[Full Featured App Integration|Instructions for Integrating Full-Featured Messaging Apps]] | ||
| - | By requesting this type of access your app will be responsible for writing to the SMS database. Therefore, all features should work in your app. As with pre-KitKat messaging, your app should abort the broadcast if there is reason to (for example, you have an anti-spam feature). The first "messaging" app to either abort or write the message will be the last in this group to receive it. | + | By requesting this type of access your app will be responsible for writing to the SMS database. Therefore, all features should work in your app. As with pre-KitKat messaging, your app should abort the broadcast if there is reason to (for example, you have an anti-spam feature). The first "messaging" app to either abort or write the message will be the last in this group to receive it. |
| //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_types.txt ยท Last modified: 2014/03/15 09:06 by superdupersms
Page Tools
