5 ms·
* "APIs are not well-documented, and Google has changed them over time" * "Carriers modify the OS to support their particular [...] idiosyncrasies." * "Poor,
by bookwormAT 13y ago
* "APIs are not well-documented, and Google has changed them over time"
* "Carriers modify the OS to support their particular [...] idiosyncrasies."
* "Poor, inconsistent and conflicting documentation"
Not true. Google usually documents APIs well, and older versions of Android are forwards compatible to newer versions.
The SMS Api that the author used was a so-called "hidden API". These APIs are not documented on purpose, as they are not supposed to be used by developers. These are experimental APIs that can and mostly will change over time.
Hidden APIs are not part of the Android specification and they are not part of the Android compability test suite. Of course they do not work reliable on different versions of the operating system.
See: http://android-developers.blogspot.co.at/2013/10/getting-your-sms-apps-ready-for-kitkat.html http://android-developers.blogspot.co.at/2013/10/getting-you...
- madeofpalk 13y agoInteresting. So the SMS API was a private API all along? On iOS you get rejected for using private APIs for that very reason.
- Retric 13y agoiOS 4 has an API for sending text messages, doing the same prior to Android 4.4 required using hidden API's. That's the real issue.
- schvenk 13y agoiOS does not have an API for sending text messages. iOS has an API that presents the user with an Apple-controlled screen, from which she can then send a text message...but there's no way to send a message without presenting that extra UI step.
- Retric 13y agoAnd on android 4.4 you can have 1 and only 1 app can send text messages. There both compromises around the idea that sending SMS messages costs people money. If it's really important to you you can always set up your own SMS server and use that, however for security reasons Apps don't get full control of the SMS system though an API.