When Google unveiled Hangouts during Google I/O as its first step towards a unified, cross-platform and cross-product messaging client, the tech world took its best guess as to when Hangouts would also power SMS and MMS messages, leaving Google Voice in the dust. We were given confirmation that this would all happen at some point, but here we are some five months later without Google fully going that route.
When KitKat launches, it will finally introduce a public API for the last remaining functions texting apps could not achieve without diving into private APIs. Developers are often advised to stay away from private APIs since they can change with each new version and may not be kept consistent across different OEMs.
If the latest post on the official Android Developers Blog gives us anything, it’s a confirmation that there are big changes coming to the handling of SMS, MMS, and default SMS apps in Android 4.4.
According to this post, Google is asking SMS app developers to make needed changes to their apps so that they can still function properly in Kit Kat. In Android 4.4, only one app can be setup as the “default” and receive the new SMS_DELIVER_ACTION intent and write (send) to SMS Provider. In other words, only one app can be the default for sending and receiving SMS and MMS messages. Developers have been asked to setup their apps with the option of being used as the default SMS app.
The dirty details on making this change are all laid out at the source link below.
It just looks to me that right now, Google wants there to be more power and integration with SMS apps, whether that be Hangouts or something from a 3rd party developer. Rather than 3rd party apps funneling text messages through the stock text app, this sounds as if it will give them the power to send them out by themselves. Goodbye, need for a stock Messaging app?
0 comments:
Post a Comment