KitKat To Complete SMS API, Need Default Texting App Plus Limit All Others

In a post around the Android Developers Blog previously today, Google has given us yet another indicator associated with upcoming changes to the Google android platform. When KitKat commences, it will finally introduce a public API for the last remaining functions texting apps could hardly achieve without diving into private APIs. Developers will often be advised to stay away from private APIs since they can change with each new version and may even not be kept consistent throughout different OEMs.

The key component of the new strategy is a setting where customers can choose their default texting app, and it will be assured access to every SMS and MMS message received with the phone. As a part of this modify, the selected app will exclusively receive the new SMS_DELIVER_ACTION and WAP_PUSH_DELIVER_ACTION intents whenever new messages arrive. In addition , only this app will have permission to write to the TEXT MESSAGE Provider, the central database where your messages are stored.

defaultSmsApp changeSmsApp (1)

A lot of the wording makes it seem like sending and receiving of text messages may become more limited, however the post never specifically says existing public methods will be restricted. Contrary to some interpretations, there is nothing in Google’s publish that clearly indicates this will cause problems for apps that use texting for security, parental tracking, or even those useful for spying. For now, it appears programs will still have the ability to watch for incoming messages through the current SMS_RECEIVED_ACTION (notice, it’s Received instead of Deliver ) and to send messages through the SmsManager. send* methods. The only major modify is that modifications to the database are restricted to the arrears app.

There are several drawbacks to the new program for both developers and users. Text messaging replacement apps should be modified to avoid delivering messages if they are not the current default, since they won’t be capable of write the sent text messages to the database. Unfortunately, this can effectively corral users into sticking with a single app with regard to texting, which probably indicates the end of having one application for primary messaging whilst also having something like Facebook’s Chat Heads around with regard to quick replies.

Google’s post also phone calls out backup and recover apps which are popular among modders. Developers of these apps are advised to guide their users via changing the default application, restoring their database, after that switching back to the original application immediately after. Unfortunately, this stream will make it difficult for cloud messaging and cross-device syncing apps, neither of which will have got much recourse with the brand new restriction.

Ideally, these changes won’t be as well disruptive, but it seems likely some users will find their favorite favorite apps crippled with the new restrictions. Developers associated with texting apps will want to include the necessary permissions and purpose filters to their manifest to make sure they appear in the list associated with apps users can choose being a default. Support for the brand new API will come with Level nineteen, so app developers would want to keep their eyes peeled for the Android 4. 4 SDK.

Source: Google android Developers Blog

This entry was posted in Android News. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *