In a publish on the Android Developers Blog previously nowadays, Google has presented us but an additional indicator of future adjustments to the Android system. When KitKat launches, it will ultimately introduce a public API for the past remaining features texting apps could not achieve without diving into non-public APIs. Developers are often advised to keep absent from personal APIs due to the fact they can change with each new variation and may not be kept steady across various OEMs.
The key ingredient of the new program is a location the place people can select their default texting app, and it will be certain obtain to every SMS and MMS message obtained by the telephone. As a aspect of this transform, the selected application will completely get the new SMS_ Produce _ Action and WAP_ Thrust _ Produce _ Motion intents when new messages get there. Also, only this application will have authorization to create to the SMS Provider, the central repository in which your messages are saved.
androidpolice.com/wp-content/uploads/2013/10/nexusae0_defaultSmsApp.png">
Much of the wording can make it audio like sending and acquiring of messages might turn out to be far more minimal, but the publish never specifically states present general public approaches will be limited. Opposite to some interpretations, there is practically nothing in Google's post that plainly implies that this will result in issues for applications that use texting for stability, paren tal tracking, or even people utilized for spying. For now, it seems applications will nonetheless have the potential to observe for incoming messages by means of the current SMS_ Acquired _ Action ( recognize, it's Gained alternatively of Deliver ) and to deliver messages by way of the SmsManager. send out * methods. The only key adjust is that modifications to the database are limited to the default application.
There are some downsides to the new process for both developers and end users. Textual content messaging substitute apps ought to be modified to avoid sending messages if they are not the recent default, because they will not be able to publish the despatched messages to the database. Sad to say, this will successfully corral people into sticking with a solitary app for texting, which in all probability means the stop of possessing one particular application for key messaging although also possessing anything like Facebook's Chat Heads ab out for swift replies.
Google's post also phone calls out backup and restore applications which are common among the modders. Builders of these apps are recommended to tutorial their end users by way of altering the default application, restoring their database, then switching back again to the authentic application instantly after. Regrettably, this circulation will make it difficult for cloud messaging and cross- gadget syncing apps, neither of which will have much recourse with the new restriction.
With any luck,, these changes would not be way too disruptive, but it appears to be probable some end users will uncover their favorite favorite apps crippled by the new limitations. Developers of texting applications will want to increase the needed permissions and intent filters to their manifest to assure they show up in the list of apps consumers can decide on as a default. Guidance for the new API will arrive with Degree 19, so application developers will wa nt to retain their eyes peeled for the Android four. 4 SDK.
Supply : Android Builders Site
0 komentar:
Posting Komentar